![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The TIBCO BusinessEvents Developer’s Guide explains how to build a project and configure the agent classes and processing units. The TIBCO BusinessEvents Administration guide explains how to prepare for deployment. It also explains how to deploy, monitor, and manage the runtime application.
TIBCO BusinessEvents Express Content relating to Cache OM and backing store is not relevant to TIBCO BusinessEvents Express edition.Before you begin to use TIBCO BusinessEvents Administration, gain a basic familiarity with the product by completing the tutorials in TIBCO BusinessEvents Getting Started, and read TIBCO BusinessEvents Architect’s Guide.Deployment requires project EAR files. Project EAR files are considered an input for administrative tasks and building them is explained mainly in TIBCO BusinessEvents Developer’s Guide.
• Using TIBCO BusinessEvents Studio. See Building an Enterprise Archive (EAR File) in TIBCO BusinessEvents Developer’s Guide for details.
• At the command line. See TIBCO BusinessEvents Developer’s Guide or see Building an EAR File with Studio Tools Utility.
• With all methods of deployment, you must ensure that certain files are available at runtime. 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. See Updating Classpath, Environment Variables, Path, and Copying JAR Files.Before deploying a business rule and starting the engine, you must set the property be.cluster.ruletemplateinstances.deploy.dir in the CDD, be-engine.tra, or in a .properties file. The property specifies the directory from which the engine loads business rules for the specific project.The output of a design-time project is one or more Enterprise Archive (EAR) files and one or more Cluster Deployment Descriptor (CDD) files. For details on configuring and building these files, see TIBCO BusinessEvents Developer’s Guide.
•
For details about deploying TIBCO BusinessEvents Decision Manager classes (implemented virtual rule functions) see TIBCO BusinessEvents Decision Manager User’s Guide.For design time procedures relating to global variables see Working with Global Variables in TIBCO BusinessEvents Developer’s Guide.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 9, Hot Deployment.(TIBCO BusinessEvents Monitoring and Management also allows hot deployment. See Hot Deployment for information pertinent to MM.)
•
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |