> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flexagon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# mdsDeploy

> Deploy artifacts generated by the operation to the MDS server. Note that MDSObjects.jar (artifact file) does not have namespace in its structure, but

Deploy artifacts generated by the [mdsBuild](https://docs.flexagon.com/flexdeploy-11-0-documentation/flexdeploy-plugin-guides/flexdeploy-oracle-mds-plugin-guide/mdsbuild.md) operation to the MDS server. Note that `MDSObjects.jar` (artifact file) does not have namespace in its 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.

This operation also supports package-based build and deploy. When using package-based deploy, the plugin will consume a zip file created by the [mdsBuild](https://docs.flexagon.com/flexdeploy-11-0-documentation/flexdeploy-plugin-guides/flexdeploy-oracle-mds-plugin-guide/mdsbuild.md) operation, named `\{\{FD_PROJECT_NAME\}\}.zip` . Note that the structure of this file will match the folder structure from SCM, even if the TARGET attribute is set to a different path. This is so the user can easily change the target and redeploy to MDS to update the file path inside of MDS.  When the operation executes, each file in the zip is extracted to its respective target path inside of a temporary namespace folder created with the value from `FDMDS_NAME_SPACE.` 

# Target Properties

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Property Name**</th><th>**Property Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>MDS UserID</td><td>`FDMDS_USERID`</td><td>Yes</td><td>Username for MDS access.</td></tr><tr><td>MDS Password</td><td>`FDMDS_PASSWORD`</td><td>Yes</td><td>Password for `MDS UserID`.</td></tr><tr><td>MDS JDBC URL</td><td>`FDMDS_JDBCURL`</td><td>Yes</td><td>Database URL for MDS access.</td></tr><tr><td>Oracle SOA Home</td><td>`FD_ORACLE_SOA_HOME`</td><td>Yes</td><td>Oracle SOA Home indicates where SOA Suite is installed.</td></tr></tbody></table>

# Project Properties

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Property Name**</th><th>**Property Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>MDS Name Space</td><td>`FDMDS_NAME_SPACE`</td><td>Yes</td><td>Name space within MDS where the objects will be stored.</td></tr><tr><td>MDS Property Replacement</td><td>`FDMDS_PROPERTY_REPLACEMENT`</td><td>No</td><td>Indicates whether property replacement will be performed on the MDS objects.</td></tr></tbody></table>

# Project File Attributes

> [!NOTE]
>
> The following properties are Project File Attributes. They are only available on Package-Based projects.

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Attribute Name**</th><th>**Attribute Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>Target Path</td><td>`TARGET`</td><td>Yes</td><td>The path in MDS where the file should be placed. Default value is the SCM file path.</td></tr><tr><td>Property Replacement</td><td>`PROPERTY_REPLACEMENT`</td><td>Yes</td><td>Whether or not to perform property replacement on individual files. Defaults to the value of FDMDS\_PROPERTY\_REPLACEMENT.</td></tr><tr><td>Rollback Source Type</td><td>`ROLLBACK_SOURCE_TYPE`</td><td>No</td><td>Where to retrieve file when initiating a [rollback deployment](https://docs.flexagon.com/flexdeploy-11-0-documentation/flexdeploy-users-guide/workflow-request-execution/build-deploy-projects.md#Rolling-Back-a-Deployment). Defaults to Project VersionOptions are Project Version, SCM Revision, Backup Repository, and Rollback FileSCM Revision and Rollback File options are only available when the project has SCM details configured, and Backup Repository should only be used if the FlexDeploy server and project are configured to take [backups](https://docs.flexagon.com/flexdeploy-11-0-documentation/flexdeploy-installation-guide/advanced/flexdeploy-backups-repository.md).</td></tr><tr><td>Rollback File</td><td>`ROLLBACK_FILE`</td><td>No</td><td>The associated file to deploy which will roll back this file. Only applicable when Rollback Source Type is Rollback File</td></tr></tbody></table>

> [!NOTE]
>
> For Package-Based projects only:\
> 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 `FDMDS_NAME_SPACE` is "apps", and the target path is `/Schemas/customer.xsd,` the path inside of MDS will be /`apps/Schemas/customer.xsd.`

# 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`.

# Endpoint Selection

This operation will select all available endpoints associated to the Target.

# Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.

# Replacement Properties 

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](https://docs.flexagon.com/flexdeploy-11-0-documentation/flexdeploy-variables-guide/property-replacement-support.md).\
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.