Basic MM Configuration
TIBCO BusinessEvents Monitoring and Management (MM) component has to be configured for use with a deployed TIBCO BusinessEvents cluster.
The tasks are arranged in a reasonable order, but the specified order is not required for many of them:
- The MM server cluster uses cache-based object management, but MM can monitor TIBCO BusinessEvents engines running in In-Memory mode too.
- TIBCO BusinessEvents MM allows you to monitor multiple clusters. Each cluster is configured using its own site topology file. The cluster names must be unique.
- For monitoring machine-level metrics, TIBCO Hawk is required. Other metrics are available without use of TIBCO Hawk. The version of TIBCO Hawk provided with TIBCO Runtime Agent is sufficient.
- TIBCO BusinessEvents Express edition can monitor and manage only engines running in In-Memory mode.
Before you begin, the following monitored cluster project files must be correctly configured and available on the MM server machine.
- The CDD files: Cache OM and In-Memory are supported. However, monitoring In-Memory and Cache OM simultaneously is not supported.
- The EAR files: The EAR files containing the compiled TIBCO BusinessEvents Studio projects.
See TIBCO BusinessEvents Developer’s Guide for details on maintaining these resources.
- MM Runtime Architecture
TIBCO BusinessEvents Monitoring and Management (MM) consists of MM consoles and a MM cluster. - Software for Remote Start and Deployment
Several software utilities are available to perform remote operations. - TIBCO Hawk Configuration for Machine Level Metrics
To monitor machine level statistics, use TIBCO Hawk software as well as TIBCO Rendezvous as the transport. - JMX Properties and To-Be-Monitored Engine TRA Files
After the TIBCO BusinessEvents cluster engines are started, they use JMX MBeans to expose monitoring and management information to the MM server, and to allow remote method invocation. - User Authorization for Administrator and User Roles
MM authorization uses two preconfigured roles. - Site Topology
The site topology file contains deploy-time information such as what processing units to deploy to specific machines in your environment. - Basic MM Settings in MM.cdd
The MM server uses the MM.cdd file to perform basic configuration and also to configure alerts, health metric rules, and actions. - Coherence WKA Cluster Discovery
If you are using the Oracle Coherence cache provider and you have configured the monitored project to discover cluster members using well-known addresses (WKA), then make some additional changes to the project CDD so that MM can monitor and manage the cluster. - TIBCO BusinessEvents DataGrid WKA Discovery
If you use the TIBCO BusinessEvents DataGrid cache provider, and you have configured the monitored project to discover cluster members using well-known addresses (WKA) then you must make some additional changes to the monitored project CDD so that MM can monitor and manage the cluster.
Copyright © TIBCO Software Inc. All rights reserved.