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 provide detailed steps.The tasks are arranged in a reasonable order, but the specified order is not required for many of them.
• All agents and nodes to be monitored must belong to the same TIBCO BusinessEvents cluster (that is, have the same cluster name). That cluster must use Cache based object management.
• For monitoring of 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 file: See Chapter 3, CDD Configuration Procedures. Cache OM is required.
• The EAR file: The EAR file contains the project details. See TIBCO BusinessEvents Developer’s Guide.The following conceptual diagram shows the MM cluster in the center, the web-based MM Console on the left, and the monitored cluster on the right, 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 ArchitectureRemote JMX connections enable MM to use 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.
Copyright © TIBCO Software Inc. All Rights Reserved.