Deployment Using TIBCO Administrator or at the Command Line : Deployment Overview

Deployment Overview
The output of a design-time project is one or more Enterprise Archive (EAR) files and one or more Cluster Deployment Descriptor (CDD) files.
An EAR file deploys as one TIBCO BusinessEvents processing unit (engine). A processing unit can either contain one cache agent, or it can contain one or more agents of other types. Processing units and agents are defined in the CDD file.
When you deploy an EAR, you specify the CDD file to use, and you specify which processing unit class to deploy.
You can deploy in these ways:
For details about deploying TIBCO BusinessEvents Decision Manager classes (implemented virtual rule functions) see TIBCO BusinessEvents Decision Manager User’s Guide.
Hot Deployment
You can configure your TIBCO BusinessEvents engine to allow you to replace the EAR file without shutting down the engine. This is known as a hot deployment. See Chapter 11, Hot Deployment.
Manually Copy Custom Function and Third-Party Jars at Deploy-time
If your project has JAR files for custom functions or third-party software, you must manually copy them to the runtime location. Copy them to a location on the classpath of the deployed application. The recommended location is the BE_HOME/lib/ext/tpcl directory. If you choose a location that is not in the classpath, then update the classpath in the TRA file to include the location.