Deployment from TIBCO Business Studio Direct Or DAA Export
To deploy an application from TIBCO Business Studio to your BPM runtime, you have three options: Direct deployment, Export to a Distributed Application Archive (DAA) and deploy to a remote server, and create and execute a deployment script that can be used to deploy a project, or to deploy multiple projects simultaneously, using the command-line.
- Deploy directly to the BPM runtime using a deployment server. To do this:
- Create and connect to a deployment server. See Creating a New Deployment Server.
- Deploy to the server using either a deployment wizard or a drag-and-drop method. See Deploying an Application Using the Deployment Wizard and Deploying an Application by Dragging and Dropping for details.
- Export to a Distributed Application Archive (DAA) and deploy to a remote server. See Exporting to DAA.
- Create and execute a deployment script that can be used to deploy a project, or to deploy multiple projects simultaneously, using the command-line. See Deploying BPM Applications for information on this process.
Direct Deployment
Direct deployment from TIBCO Business Studio has the following goals and characteristics:
Exporting a DAA
Exporting a DAA file to ActiveMatrix Administrator for deployment is intended for production use, where finer-grained control over whether deployment is forceful or not, is required. The DAA is typically available in the Exports folder of the project.
Note: Note that DAAs generated using the scripted deployment facilities (see Deploying BPM Applications
) are not found in the Exports folder of the originating project, but are generated as part of the deployment project.
Copyright © Cloud Software Group, Inc. All rights reserved.