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 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.
...
Environment/Instance Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
Project Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
MDS Base Object Path |
| No | The relative directory path from where MDS objects will be included in generated artifact. |
Inputs
Input Name | Input Code | Required | Description |
---|---|---|---|
Outputs
Output Name | Required | Description |
---|---|---|
Artifacts
This operation produces a jar 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 and Checkout Folder
to 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
in to into empty checkout folder. - Set
namespace
for forMDS Base Object Path
and and all objects will be included in artifact jar file and it will have proper structure i.e.order/order.xsd
and andcustomer/customer.xsd
.
- Check out
- If you want only customer objects
- Make sure you only checkout
/trunk/namespace/customer
folder folder only as we are only interested in customer objects here. - Use
namespace/customer
as as checkout folder as we still want to maintain structure of objects. - Set
namespace
asMDS Base Object Path
as namespace. - 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
.
- Make sure you only checkout
- 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 for sparse checkout folders and empty checkout folder. - Set
/MDS/namespace
asMDS Base Object Path
as /MDS/namespace , and all objects will be included in artifact jar file and it will have proper structure i.e.order/order.xsd
and andcustomer/customer.xsd
.
- Use
- If you want only customer objects
- Use
/MDS/namespace/
customer forcustomer
for sparse checkout folders and empty checkout folder. - Set
/MDS/namespace
asMDS Base Object Path
as /MDS/namespace. - 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
- Configurations for sparse folder and checkout folder is done on Source Configurations for project and SCM plugins will automatically utilize that information.
...