Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 1 Introduction to Administration : Overview of Administration

Overview of Administration
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.
The main administration tasks and the chapters in which they are documented are as follows:
Building EAR Files for Deployment
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.
You can build EAR files as follows:
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.
Deploy-Time Configuration
System level configuration is generally needed. Edit the engine TRA file to add and set values for settings that are read before the engine starts.
If you will use TIBCO BusinessEvents Monitoring and Management (MM) component, you must first configure it to work with your cluster. Two kinds of configuration are documented:
Manually Copy Custom Function and Third-Party Jars at Deploy-time
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.
Set the Business Rules Deployment Directory Property Before Deploying a Business Rule
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.
During startup, the engine reads the business rules from the specified directory and loads them into all the rule sessions. Ensure that the directory is local to the machine on which the engine is running. To avoid conflicts, the deployment directory specified should not contain business rules for other projects.
Deployment
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.
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:
Overriding Global Variables at Deploy Time
All methods of deployment enable you to override global variables at deploy time:
For design time procedures relating to global variables see Working with Global Variables in TIBCO BusinessEvents Developer’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 9, Hot Deployment.
(TIBCO BusinessEvents Monitoring and Management also allows hot deployment. See Hot Deployment for information pertinent to MM.)
Management and Monitoring
Depending on your method of deployment, you can use either MM or TIBCO Administrator (with TIBCO Hawk) for monitoring and management.
Authentication and Authorization
Certain components use authentication (BEMM, TIBCO BusinessEvents Views, TIBCO BusinessEvents Decision Manager). Currently only TIBCO BusinessEvents Decision Manager uses authorization (access control).

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved