This section explains at a high level how to configure the TIBCO BusinessEvents Monitoring and Management (MM) component for use with a deployed 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 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.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 broker.Figure 1 MM Runtime ArchitectureJMX remote connections enable MM to use the MBeans exposed in the monitored cluster’s engines 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.The configuration tasks are listed below. Specific steps are provided in the referenced procedures.
Copyright © TIBCO Software Inc. All Rights Reserved.