Deploy artifacts generated by the mdsBuild operation to the MDS server. Note that MDSObjects.jar (artifact file) does not have namespace in it's structure, but objects will be deployed to the specific namespace configured on Project properties.
Property replacement logic will be executed on Objects prior to deployment if MDS Property Replacement was checked on project properties.
This operation must execute on one of the SOA managed server endpoints in SOA domain.
Property Name | Property Code | Required | Description |
---|---|---|---|
MDS UserID |
| Yes | User name for MDS access. |
MDS Password |
| Yes | Password for MDS UserID. |
MDS JDBC URL |
| Yes | Database URL for MDS access. |
Oracle SOA Home |
| Yes | Oracle SOA Home, indicates where SOA Suite is installed. |
Property Name | Property Code | Required | Description |
---|---|---|---|
MDS Name Space |
| Yes | Name space within MDS where the objects will be stored. |
MDS Property Replacement |
| No | Indicates whether property replacement will be performed on the MDS objects. |
Input Name | Input Code | Required | Description |
---|---|---|---|
Output Name | Required | Description |
---|---|---|
This operation consumes a jar file that contains a variety of objects that will be stored in the MDS, such as an xsd, xslt or wsdl.
This operation will select all available endpoints associated to the environment/instance.
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
If the project property MDS Property Replacement is checked, then all files within the MDS object structure are pre-processed by the plugin to transform any defined replacement properties.
This is needed when there are URLs that are defined in file and need to be changed by environment, such as a URL in a fault policy file.