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 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. See Application Modules and Shared Modules in the Concepts guide for details. Applications can also contain OSGi bundles that do not contain TIBCO® Cloud Integration artifacts.

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.

Note: If any further changes to the design or configurations are made, the deployment artifact (archive file) must be regenerated.

When creating an archive file for an application, the application packager also generates the processes in SVG format.

There are multiple ways to create a deployment artifact:

  • From the Project Explorer view in TIBCO Business Studio, open <Project>app > Overview and click Export Application for Deployment link as shown below.

    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.
Note: Artifacts intended to be exported from a shared module must be contained in their respective special folders. For example, schemas must be contained in the Schemas folder, WSDL files in the Service Descriptors folder, and processes must be contained in a package under the Processes folder.