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


Chapter 3 Basic MM Configuration : Overview of MM Configuration

Overview of MM Configuration
This section explains at a high level how to configure the TIBCO BusinessEvents Monitoring and Management (MM) component for use with a deployed TIBCO BusinessEvents cluster. Sections follow providing detailed configuration steps.
The tasks are arranged in a reasonable order, but the specified order is not required for many of them.
Before You Begin
Before you begin, the following monitored cluster project files must be correctly configured and available on the MM server machine.
See TIBCO BusinessEvents Developer’s Guide for details on maintaining these resources.
MM Runtime Architecture
The following conceptual diagram shows the MM cluster in the center, the web-based MM Console on the left, and one instance of the monitored cluster on the right. The monitored cluster is connected to the MM cluster through JMX, and through a Java process that uses RMI to connect the two clusters. This process is known as a broker. Note that the broker is used only with the Coherence cache provider and is not required for the TIBCO BusinessEvents DataGrid cache provider.
Figure 1 MM Runtime Architecture
Remote JMX connections enable MM to connect to the MBeans exposed in the monitored cluster’s engines. These MBeans allow the user to invoke remote operations from MM Console to gather performance metrics.Additionally, software utilities are used for remote start and deployment, and TIBCO Hawk is used for machine level metrics.
Files used to configure the console and the connection to the monitored cluster are shown along the top of the diagram. Configuration is explained in this chapter.
Summary of Configuration Tasks
The configuration tasks with detailed procedures are listed below.

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