Generates an artifact jar of checked out objects for deployment(MDSObjects.jar) from exported code. You should must 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 have folder structure as per exported code, checkout folder & project properties configuration, see project properties section for more details. When artifact is deployed, it will 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 This operation also supports partial build. When . Partial build creates a build artifact containing file(s) and folder(s) selected on the Project Files tab of a project. 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

...

Property Name

...

Required

...

Description

Project Properties

Inputs

...

Input Name

...

Required

...

Description

...

Output Name

...

Required

...

Description

Project File Attributes

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 delegates endpoint selection to the workflow developer. The workflow editor will default the selection to "All", which selects all available endpoints associated to the environment/instance.  Target.

Selecting a specific resource will result in selection of endpoints associated to the Target which have that resource defined.

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:

...

Git Example

• Subversion

  Git Folder structure

  • /

    trunk

    MDS/

    namespace

    apps/order/order.xsd

  • /

    trunk

    MDS/

    namespace

    apps/customer/customer.xsd

• If you want both of the objects

  • Check out /trunk into empty checkout folder.
  • Set namespace for

    Use "MDS/apps" for sparse checkout folder script. You can use anything for checkout folder script.

  • Use apps for MDS Name Space.

  • Leave MDS Base Object Path

     and

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

  • At deploy time both files will deploy to apps folder.

  • This option should work for partial deployment project as well.

• 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 

    Use "MDS/apps/customer" for sparse checkout folder script. You can use anything for checkout folder script.

  • Leave MDS Base Object Path as empty.

  • 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

    .

  • Use apps/customer for MDS Name Space.

• Configurations for

  what should be checked out

  sparse folder and checkout folder is done on Source Configurations for project and SCM plugins will automatically utilize that information.

Subversion Example

...

Git Example

...

• Subversion Folder structure

  • /

    MDS

    trunk/

    namespace

    apps/order/order.xsd

  • /

    MDS

    trunk/

    namespace

    apps/customer/customer.xsd

• If you want both

  of the

  objects

  • Use /MDS for sparse checkout folders and empty checkout folder.
  • Set /MDS/namespace  as 

    Configure /trunk/apps on Project Source.

  • Option 1

    • Set Checkout folder and MDS Base Object Path set to Project Name.

  • Option 2

    • Do not set anything for Checkout folder and MDS Base Object Path

    , and all

    • .

  • For both options, both objects will be included in artifact jar file, and it will have proper structure i.e. order/order.xsd and customer/customer.xsd.

  • Configure namespace on Project Properties as apps.

• If you want only customer objects
  

  • Use /MDS/namespace/customer for sparse checkout folders and empty checkout folder.
  • Set /MDS/namespace 

    Make sure you only checkout /trunk/apps/customer folder only as we are only interested in customer objects here.

  • Use apps/customer as checkout folder as we still want to maintain structure of objects.

  • Set apps 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.

  • Configure namespace on Project Properties as apps.

• Configurations for

  sparse folder

  what should be checked out and checkout folder is done on Source Configurations for project and SCM plugins will automatically utilize that information.