MM Runtime Architecture

TIBCO BusinessEvents Monitoring and Management (MM) consists of MM consoles and a MM cluster.

The 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.

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.