TIBCO BusinessEvents Administration Components

Administration of a deployed system involves management of objects generated by the inference engine, deploy-time configuration for tuning and other aspects of the system, deployment, management, and monitoring.

This section describes the TIBCO BusinessEvents components. For cache, you can optionally use a supported version of Oracle Coherence, for which you have a license that is appropriate for your usage. For deployment, monitoring, and management, you can optionally use TIBCO Administrator. Customers who are already using these software products may find it convenient to continue to do so. These products are not provided with TIBCO BusinessEvents.

Object Management
How you manage objects generated by the rules executing in the inference engine depends on whether you want to keep them for later use. You can manage objects in memory only, or using a distributed cache, or using a cache with a backing store. The recommended way to manage objects for most production needs is to use a cache and a backing store. When cache-based object management is used, agents of different types co-operate to provide efficient object storage and access, with options to use load balancing and fault tolerance of data and engine processes.
Object management is partly a design-time and partly an administration topic, because your choice of object management type can affect how you design rules. For example, you may have to retrieve objects if they are stored only in the cache or only in the backing store, so they can be used in the Rete network. See Object Management Types for an introduction to these topics.
Deploy-time Configuration Settings are in the Cluster Deployment Descriptor (CDD)
Using the Cluster Deployment Descriptor (CDD) editor, you edit the CDD file to specify all the deploy-time properties for the entire cluster, from cluster-wide settings dealing with object management, through processing unit settings (that is, those at the TIBCO BusinessEvents engine level), to individual agent class settings.
To deploy any engine (processing unit) in the cluster, the only details needed are these: the EAR file, which contains all the project resources, the CDD file, and the name of the processing unit (a unit that deploys as an engine). You can change deploy-time configuration settings in the CDD file, without having to rebuild the EAR file.
TIBCO BusinessEvents Monitoring and Management (MM)
The MM component enables you to deploy cache-based or in-memory TIBCO BusinessEvents engines, and then monitor and manage a deployed cluster. It uses a canvas-based site topology editor to configure the physical deployment of the cluster. It also provides a web-based dashboard, the MM Console, to enable you to monitor the deployment and perform the various tasks.
You can configure the health metric and alert thresholds that define the graphical display of system health, and the actions to take when thresholds are reached, such as sending email. MM monitoring features enable you to easily spot bottlenecks or other troublespots in the system so you can address any issues. MM also has a profiler and can generate other helpful reports
Deployment Topology Configuration Using a Site Topology Editor
See Deploy-time and Runtime Overview for details.