Checks out the asset sources. The build script can use a VCS to obtain the asset sources to build into composites. If you use a VCS to store your assets, you must set the enable.checkout property in build.properties to true and set the properties in build-source-checkout.xml to access the VCS. For more information, see Setting Build Properties and Setting VCS Checkout Properties.Creates and indexes the repository. The build script creates the repository in the specified structure. This is the source from which Deployer selects the assets for deployment. For more information about defining a repository in Deployer, see Connecting to a Repository for
Repository-Based Deployment.Versions the assets. The build script uses the build-number.xml file to automatically version the assets included in the build in the format version_number.build_number.Builds the composites and descriptors in the repository. The build script generates the following files for each runtime type in the build:ACDL descriptor file in the format project_name.acdlA compressed composite file that contains the definitions of the assets and their dependencies for deployment. The composite file is in the format project_name.composite_file_type where:For this runtime type... | project_name is the... | composite_file_type is... |
ActiveTransfer | Name of the file you exported using wm.mft.admin:exportData built-in service. For more information about wm.mft.admin:exportData, see webMethods ActiveTransfer Built-In Services Reference. | .bin |
API Gateway | APIGatewayAssets.acdl | .zip |
Application Platform | When the project is a standard web application, its name is used as project_name.war. | .war |
When the project is an OSGi bundle, its name is used as project_name.jar. | .jar | |
When the project is an OSGi web bundle, its name is set to project_name.jar. | .jar | |
Note: The difference between bundle and Web bundle is in the jar content. Web bundles are valid OSGi bundles and are structured internally as .war files, that is, they are a fusion of the first two project types. The difference is also reflected in the "acdl" file of the web bundles. They contain both an asset of type "Bundle" and an asset of type "WebApp". | ||
The fourth type of composite is configuration files. They have the file extension as ".properties". They do not have their own projects. Instead they are co-hosted in the /src/main/config/ directory of either a war or a bundle or a web bundle project. The name of the host project is not used to build the name of the configuration composite. These files are "built" simply by copying them to the asset repository. Therefore they are named "property_file_name.properties". An additional file "property_file_name.acdl" is created to make them into individually deployable assets. It is possible to create a project that constitutes only a collection of configurations in /src/main/config. These configurations can customize either other composites or the OSGi Common Platform itself. | ||
BPM process model | Process ID with “/” replaced by “_”. For more information about process models, see webMethods BPM Process Development Help. | .process |
Digital Event Services | Name of the folder that contains the DES "TypeRepository" folder. | .zip |
Broker | Name of the file you exported using My webMethods Server prefixed with “Broker_” or “Provider_” depending on whether you exported Broker assets or JNDI assets, respectively. When you export Broker assets (document, client, or client group), Broker creates an ADL file for the Broker assets. To export assets from webMethods Broker 8.2 SP2 or earlier, you must migrate the assets from XML format to ADL format for use in Deployer. For more information about migrating Broker assets from XML to ADL format, see Upgrading Software AG Products. When you export JMS destinations (JMS queues and JMS topics) created by a webMethods JNDI provider, Broker creates a separate XML file for a JNDI context. For more information about exporting Broker assets, see Administering webMethods Broker. | .adl (Broker assets) .xml (JNDI assets) |
Business Rules | Name of the rules project. | .jar |
EDA | Name of the Event Types project. | .zip (Event Type assets) |
Integration Server | For package, adapter runtime, and .Net assets, this is the name of the Integration Server package. For more information about adding package assets to the source directory for inclusion in the build, see Adding Package Assets to the Source
Directory. For more information about adding adapter runtime or .Net assets to the source directory for inclusion in the build, see Adding Adapter Runtime and .NET Service
Assets to the Source Directory.For administrative assets, this is isconfiguration. For more information about adding administrative assets to the source directory for inclusion in the build, see Adding Administrative Assets to the Source
Directory. | .zip |
My webMethods Server | Name of the project you exported. For more information about exporting My webMethods Server assets, see Administering My webMethods Server. | .skin, .war, .cdp |
AgileApps Cloud | Name of the application you exported using AgileApps Cloud server. For more information about exporting AgileApps Cloud assets, see the AgileApps Cloud documentation. | .zip |
Optimize | Name of the file you exported using My webMethods Server. For more information about exporting Optimize assets, see Administering webMethods Optimize. | .zip |
Trading Networks | Name of the file you exported using My webMethods Server. For more information about exporting Trading Networks assets, see webMethods Trading Networks Administrator’s Guide. | .bin |
Task Engine | Name of the task application project. | .war |
Universal Messaging | Name of the file you exported using Universal Messaging Enterprise Manager. | .xml |
The composite for a Broker project containing Broker assets would be named Broker_file_name.adl, where file_name is the name of the file you exported from Broker using My webMethods Server.The composite for a Broker project containing JNDI assets would be named Provider_file_name.xml, where file_name is the name of the file you exported from Broker using My webMethods Server.The composite for a project containing Integration Server administrative assets would be named isconfiguration.zip.