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.
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.
Copyright © Cloud Software Group, Inc. All rights reserved.