mdsDeploy

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.


As of plugin version 4.6.20, this operation also supports partial build and deploy. When using partial deploy, the plugin will consume a zip file created by the mdsBuild 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. 

  

Environment/Instance Properties

Property Name

Property Code

Required

Description

MDS UserID

FDMDS_USERID

Yes

User name for MDS access.

MDS Password

FDMDS_PASSWORD

Yes

Password for MDS UserID.

MDS JDBC URL

FDMDS_JDBCURL

Yes

Database URL for MDS access.

Oracle SOA Home

FD_ORACLE_SOA_HOME

Yes

Oracle SOA Home, indicates where SOA Suite is installed.

  

Project Properties

Property Name

Property Code

Required

Description

MDS Name Space

FDMDS_NAME_SPACE

Yes

Name space within MDS where the objects will be stored.

MDS Property Replacement

FDMDS_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

The following properties are Project File Attributes. They are only available on Partial Deploy projects.

Target PathTARGET

Yes

The path in MDS where the file should be placed. Default value is the SCM file path.

Property ReplacementPROPERTY_REPLACEMENTYesWeather or not to perform property replacement on individual files. Defaults to the value of FDMDS_PROPERTY_REPLACEMENT.

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 environment/instance.


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

The following macros are not currently supported in the footer:
  • style