Generates an artifact jar of checked out objects for deployment. You should checkout or export code from SCM prior to running this operation. Checkout or Export can be easily done if you configure project with Source details.

Generated MDSObjects.jar artifact file will not have namespace folder at root, but when it is deployed it will still be deployed under specific namespace configured on Project properties.

There are no special requirements for the Endpoint where this operation will execute.

As of plugin version 4.6.20, this operation also supports partial build. When using partial build, the plugin will generate a zip file 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 without having to rebuild the entire project. 

Environment/Instance Properties

Project Properties

Inputs

Outputs

Project File Attributes

Artifacts

This operation produces a jar or zip file that contains a variety of objects that will be stored in the artifacts repository, 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.

Special Considerations

If your MDS objects are in separate SCM folders, then everything will be easy to build and deploy, but if you have one single SCM folder, but would like to create more than one FlexDeploy projects, you need to utilize MDS Base Object Path and Checkout Folder to control what gets included in artifacts jar file. For example:

Subversion Example

• Subversion Folder structure
  
  • /trunk/namespace/order/order.xsd
  • /trunk/namespace/customer/customer.xsd
• If you want both of the objects
  • Check out /trunk into empty checkout folder.
  • Set namespace for MDS Base Object Path and all objects will be included in artifact jar file and it will have proper structure i.e. order/order.xsd and customer/customer.xsd.
• If you want only customer objects
  
  • Make sure you only checkout /trunk/namespace/customer folder only as we are only interested in customer objects here.
  • Use namespace/customer as checkout folder as we still want to maintain structure of objects.
  • Set namespace as MDS Base Object Path.
  • So we have only checked out objects necessary for our project, so only customer folder related objects will be included in artifact jar file, but it will still have proper structure, i.e. customer/customer.xsd.
• Configurations for what should be checked out and checkout folder is done on Source Configurations for project and SCM plugins will automatically utilize that information.

Git Example

• Git Folder structure
  
  • /MDS/namespace/order/order.xsd
  • /MDS/namespace/customer/customer.xsd
• If you want both of the objects
  • Use /MDS for sparse checkout folders and empty checkout folder.
  • Set /MDS/namespace  as MDS Base Object Path, and all objects will be included in artifact jar file and it will have proper structure i.e. order/order.xsd and customer/customer.xsd.
• If you want only customer objects
  
  • Use /MDS/namespace/customer for sparse checkout folders and empty checkout folder.
  • Set /MDS/namespace  as MDS Base Object Path.
  • So we have only checked out objects necessary for our project, so only customer folder related objects will be included in artifact jar file, but it will still have proper structure, i.e. customer/customer.xsd.
• Configurations for sparse folder and checkout folder is done on Source Configurations for project and SCM plugins will automatically utilize that information.