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.
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.
- Cluster Deployment Descriptor (CDD)
All methods of deployment require a cluster deployment descriptor (CDD). - Site Topology File
Before you can use MM for deployment, you define the site topology using the site topology editor in TIBCO BusinessEvents Studio. - Deployment with TIBCO BusinessEvents Monitoring and Management (MM)
After you have configured MM to communicate with the cluster to be monitored, and you have defined the site topology file, you can log in and use the MM Console to deploy, stop and start, pause, and resume processing units. - Monitoring and Management with MM
The MM component maintains a history of statistics, continuously queries the deployed engines for their status, and invokes methods on engines, as specified by the administrator. - TIBCO Hawk Application Management Interface
TIBCO BusinessEvents includes a set of TIBCO Hawk microagent methods that allow you to manage your TIBCO BusinessEvents deployment using TIBCO Hawk. - Hot Deployment
Depending on the changes made to your TIBCO BusinessEvents project, you may be able to replace an EAR file for a TIBCO BusinessEvents project with an updated one, without stopping the TIBCO BusinessEvents engine.