Deploying a Project

After you have developed an application, and resolved all issues highlighted in the Problems view, its constituent elements must be deployed to the BPM runtime so that the application can be run.

The projects for your business application must be deployed to the BPM runtime in the correct order of dependency, that is, if "Process Project A" uses data defined in "Data Project X", then "Data Project X" must be deployed first to ensure that "Process Project A" is successfully deployed.

In general, a project is deployed in the following order:

  • Organization projects
  • The Work list facade project
  • Business data projects (in their own interdependency order)
  • Global Signal projects
  • Business Process projects (in their own interdependency order)
Note: REST Service projects do not require deployment to the BPM runtime.

You can access a visual representation of your projects using the "View Dependencies" option from the project explorer context menu (see Using the Dependency Viewer).

Deploying Projects for Development Testing

  • For process projects that use email or REST service tasks, you must create the shared resources named in each of the email and REST participants before deployment. This is done in the Shared Resources Manager in Administrator. See the "Shared Resources" topic in the TIBCO® BPM Enterprise Administration.
  • Click Launch Admin in the deployment artifact generation wizard to open the New Deployment administration tools in a web browser. Alternatively, log in to the Work Manager and select Administrator > Deployment Manager > New Deployment.
  • You can select, or drag-and-drop the .rasc file you generated, and deploy the artifacts (.rasc files) to a development server.
    Note: The projects need to be deployed in order of dependency. For example, you must deploy a business data project before the process projects that reference it and you must deploy projects with sub-processes before projects with the main process that invoke these and so on. If you do not deploy in the correct order, the deployment fails and you must redeploy the referenced projects in the correct order.

Deploying Projects for Production

  • When your development and test cycle is complete, you can lock your projects and deploy them into production BPM Enterprise environments.

    Note: Draft deployment artifacts cannot be deployed to a production server.

  • To lock your projects for production in TIBCO Business Studio - BPM Edition, right-click the project, then select Deployment > Lock for Production. This ensures that production deployment artifacts required for deployment to a production server can be created.
  • Generate the deployment artifacts for a production server. Right-click the project, then go to Deployment > Generate Production Artifacts.
  • You can also generate and deploy your projects to the production environment using the automated CI/CD commands. For more information, see Deploying a Project from the Command Line.