Deploy-time and Runtime Overview

A TIBCO BusinessEvents design-time project is deployed as a TIBCO BusinessEvents application.

When Cache object management (known as Cache OM) is used, the deployment can span multiple host servers.

Note: The TIBCO BusinessEvents Express edition supports only In Memory object management.

You can use any of these deployment methods. It is recommended that you use only one method for each cluster you are deploying:

  • At the command-line. You specify the CDD file to use and the processing unit within that CDD file.
  • Using TIBCO Administrator. If you have been using this utility in your environment, you can continue to do so. (See in Hot Deployment in TIBCO BusinessEvents Administration.)
  • Using TIBCO BusinessEvents Monitoring and Management. This is the preferred method.

All of the deployment methods use two resources: an EAR file and a cluster deployment descriptor, which is an XML file. To deploy using TIBCO BusinessEvents Monitoring and Management, you also need a site topology file.

The Enterprise Archive Resource (EAR) is the deployable version of a TIBCO BusinessEvents application. The EAR file contains runtime version of the project ontology, the channel definitions, the state machines (if TIBCO BusinessEvents Data Modeling add-on software is used), and so on. When you are finished designing the project in TIBCO BusinessEvents Studio, you simply choose a menu option to build the EAR.