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.
...
Project Properties
| 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. |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Outputs
Output Name | Required | Description |
|---|---|---|
Project File Attributes
| Attribute Name | Attribute Code | Required | Description | ||
|---|---|---|---|---|---|
| |||||
| Target Path | TARGET | Yes | The path in MDS where the file should be placed. Default value is the SCM file path. | ||
| Property Replacement | PROPERTY_REPLACEMENT | Yes | Weather or not to perform property replacement on individual files. Defaults to the value of FDMDS_PROPERTY_REPLACEMENT. | ||
...
| Info |
|---|
The target path should not contain the namespace folder, however, if the target path starts with the namespace, the plugin will ignore the namespace on the beginning of the target path. For example, if |
Artifacts
This operation consumes a jar or zip file that contains a variety of objects that will be stored in the MDS, such as an xsd, xslt or wsdl.
...