Generating Deployment Artifacts
A deployment artifact is an archive file that contains all the information required to deploy the application to runtime. It is the only artifact that is handed from the design phase to the runtime as it contains all the bundles and metadata that is required to deploy and run the application.
Applications are developed using the features available in TIBCO Business Studio™ for BusinessWorks™ and can range from simple to very complex. An application consists of an application module, which consists of one or more processes that define the business logic, and zero or more shared modules. For more information, see "Application Modules" and "Shared Modules" in the TIBCO ActiveMatrix BusinessWorks™ Concepts guide. Applications can also contain OSGi bundles that do not contain ActiveMatrix BusinessWorks™ artifacts.
Applications are developed using the features available in TIBCO Business Studio™ for BusinessWorks™ and can range from simple to very complex.
An application archive contains one or more OSGi bundles, one each for all the modules referenced directly or indirectly by the application. It also contains application metadata which is used during deployment.
When creating an archive file for an application, the application packager also generates the ActiveMatrix BusinessWorks processes in SVG format, which can be rendered in the Admin UI.
By default, the diagram information is present when exporting a process. To remove diagram information when exporting a process, navigate to the Exclude diagram information during packaging check box.
and select theThere are multiple ways to create a deployment artifact:
- From the
Project Explorer view in
TIBCO Business Studio for BusinessWorks, open
and click
Export Application for Deployment link as shown below.
Note: When importing projects created in a version of the software that is lower than ActiveMatrix BusinessWorks™ 6.4.x, if the application module or shared module version does not contain a .qualifier version, a design time validation error is thrown by default. Preference options can be set to ignore this validation error. Navigate to Window > Preferences > BusinessWorks >Validation >Missing .qualifier literal for module version. Preferences can be set to one of the following options:In the EAR Export window, specify the location for the archive file and provide a custom name to the archive file, if needed, by clearing the Use Default EAR file name check box. Click Finish to create the deployment artifact (archive file).
- By selecting the project application in the
Project Explorer and dropping it in the File Explorer an archive file for the application is created. If needed, change the default location in the File Explorer by using the
Open Directory to Browse option in the File Explorer and select a custom folder. For example
c:/tmp.
When you deploy an application, each application in an AppSpace is identified by its unique name and a major.minor version number. The version number is important as it provides traceability and helps troubleshoot in case of an error at run time. If any further modifications are made to the application, the archive file must be regenerated with an updated version number and then deployed to the AppSpace.
When you deploy and start an application, if the archive file contains the SVG format of business processes, you can view the process diagrams for the processes from the Admin UI. For more information, see the TIBCO ActiveMatrix BusinessWorks™ Administration guide.