The BusinessEvents design-time project is deployed as a BusinessEvents application, which can have multiple engines spanning multiple hosts.
Each engine equates to one processing unit, which runs in one JVM (Java Virtual Machine). One processing unit can host multiple agents, except in the case of a cache agent. There can be only one cache agent per processing unit. Each BusinessEvents agent is a runtime component of the overall application.
The Enterprise Archive Resource (EAR) is a standard component, used when deploying a BusinessEvents application. The EAR file the project ontology. When you are finished designing the project in BusinessEvents Studio, you simply choose a menu option to build the EAR.
See Administration Components for an overview of the cluster deployment descriptor, the site topology editor and file, and the BusinessEvents Monitoring and Management component.
All methods of deployment require a cluster deployment descriptor. After you define the project ontology and other resources, you configure the agents and processing units that will use those resources at runtime. Different kinds of agents play different roles in a large application: inference agents perform rule evaluation, query agents perform queries, and cache agents are deployed as cache agent nodes when the Cache object management option is used. You can include multiple agents in an engine instance by including multiple BusinessEvents agents within one processing unit.
All the properties that in prior releases were listed in the engine TRA files are now consolidated into the CDD file, and the same file is used by every engine at deploy-time: you simply specify which processing unit you want to deploy.
Depending on the changes made to your BusinessEvents project, you may be able to replace an EAR file for a BusinessEvents project with an updated one, without stopping the BusinessEvents engine. This feature is referred to as hot deployment. For more information about the BusinessEvents hot deployment feature, including the project changes that are supported, see
Chapter 9, Hot Deployment in
TIBCO BusinessEvents Administration.
The BusinessEvents Monitoring and Management (MM) component provides a dashboard for deployment and for monitoring the status of deployed BusinessEvents engines. Before you use this component you must configure it to suit your needs. Most configuration is done in the CDD file for the emonitor project, the BusinessEvents application that acts as the MM server at runtime. See
TIBCO BusinessEvents Administration for details.