Deployer 10.5 | Deploying Assets from a Source Asset Repository | Building Composites | Build Script Processing Steps and Output Files
 
Build Script Processing Steps and Output Files
The build script goes through the following processing steps:
*Checks out the asset sources.
*Creates and indexes the repository.
*Versions the assets.
*Builds the composites and descriptors in the repository.
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.
The build script generates the following files for each runtime in the build:
*ACDL descriptor file in the format project_name.acdl
This is the descriptor file that contains the metadata that lists the assets and dependencies contained in the composite.
*A 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 as described in the following table:
For this runtime type
project_name is
composite_file_type is
ActiveTransfer
The name of the file you exported using the 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
The name of the standard web application project.
.war
The name of the OSGi bundle project.
.jar
The name of the OSGi web bundle project.
.jar
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".
Configuration composites that contain configuration files, with the ".properties" file extension. They do not have their own projects, but are co-hosted in the /src/main/config/ directory of either a war, bundle, or web bundle project. The name of the host project is not used as the name of the configuration composite. The files are just copied into the asset repository with the name property_file_name.properties.
An additional property_file_name.acdl file is created for the configuration composite. You can create a project that has only a collection of configurations in /src/main/config. The configurations can customize either other composites, or the OSGi Common Platform.
BPM process model
The process ID with “/” replaced by “_”. For more information about process models, see webMethods BPM Process Development Help.
.process
Digital Event Services
The name of the folder that contains the DES "TypeRepository" folder.
.zip
Broker
The 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
The name of the rules project.
.jar
EDA
The 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
The 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
The name of the application you exported using the AgileApps Cloud server. For more information about exporting AgileApps Cloud assets, see the AgileApps Cloud documentation.
.zip
Optimize
The name of the file you exported using My webMethods Server. For more information about exporting Optimize assets, see Administering webMethods Optimize.
.zip
Trading Networks
The 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
The name of the task application project.
.war
Universal Messaging
The name of the file you exported using Universal Messaging Enterprise Manager.
.xml