Chapter 1 Overview : Deployment Concepts

Deployment Concepts
The BusinessEvents design-time project is deployed as a BusinessEvents application. This section discusses two methods of deployment, and describes the archives that contain the deployable files.
See Chapter 26, Deploytime Configuration and Chapter 28, Deploying a TIBCO BusinessEvents Project for more details on this topic.
Deployment Files
Each BusinessEvents engine runs one BusinessEvents application at a time, in one JVM (Java Virtual Machine). However, each application may contain multiple BusinessEvents archive files (BAR files), each of which deploys as a rule session within the overall rule server.
Enterprise Archive Resource (EAR)
The Enterprise Archive Resource (EAR) is a standard TIBCO Designer component that is used when deploying a BusinessEvents application. The EAR file contains one shared archive resource (SAR) file and one or more BusinessEvents archive resource (BAR) files. If the application integrates ActiveMatrix BusinessWorks functionality, it could also contain the process archive (PAR) file for the ActiveMatrix BusinessWorks processes.
Shared Archive Resource  A shared archive is automatically included in the enterprise archive. Certain resources are added automatically to the shared archive, and others are manually added. See Adding a JDBC Connection Resource for an example use in BusinessEvents.
For more information about Enterprise Archive Resources and project deployment in general, see TIBCO Designer User’s Guide.
BusinessEvents Archive Resource (BAR)
A BusinessEvents archive is the design-time equivalent of a BusinessEvents agent at runtime. Different kinds of agents play different roles in a large deployment: inference agents perform rule evaluation, query agents perform queries, and cache server agents are deployed as cache server nodes when the Cache object management option is used. You can include multiple rule sessions by including multiple BusinessEvents Archives within one Enterprise Archive resource.
A BusinessEvents Archive resource provides information that is used during the deployment stage. Use a BusinessEvents Archive resource to perform various tasks (depending on the type of agent you are configuring:
Configure the object manager for various object management options, which affect the availability, performance and memory usage of the deployed application (see Chapter 17, Understanding Cache OM and Multi-Engine Features and chapters following)
For more information about configuring the BusinessEvents Archive resource see BusinessEvents Archive Resource Reference.
Deploytime Configuration and Deployment Methods
How you configure for deployment depends in part on whether you are deploying to a TIBCO Administrator domain or not.
You can run applications at the command-line without deploying to a TIBCO Administrator domain. In this case, you set configuration parameters in the engine property file (be-engine.tra) This approach is useful for testing purposes, but is not recommended for production purposes.
For production purposes, it is recommended that you deploy projects to a TIBCO Administrator domain. TIBCO Administrator provides a user interface for setting deploytime parameters, as well as management and monitoring features. It also provides a command-line utility called AppManage (documented in TIBCO Administrator documentation). You can also set configuration parameters in the engine property file.
See Configuring to Run Outside of a TIBCO Administrator Domain and Configuring to Run in a TIBCO Administrator Domain for more details.
Hot Deployment
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 29, Configuring and Using Hot Deployment.