Gather Information for Configuration

After installing the Monitor you configure it to monitor your Coherence Cluster(s). We recommend that you gather the necessary configuration information prior to installing the Monitor. Choose the appropriate connection and monitoring mechanism:

JMX Connection Information , next: JMX Connection requires knowledge of how JMX monitoring is enabled and configured on the cluster.

Direct Connection Information : Direct Connection requires knowledge of how the cluster is configured so the Monitor can join the cluster directly as a node.

JMX Connection Information

Use the table below to gather information you need for configuring a JMX Connection to an existing MBean Server.

Information Needed
JMX Remote Port Connection: The IP or host name. The port number.
JMX RMI Adapter Connection: The URL for the connection.
Authenticated JMX Remote Port Connection: JMX Authentication and authorization mechanisms (for example, Username and password).

Direct Connection Information

Use the table below to gather information you need for configuring the Monitor application. If the Java properties and class path used by the cluster you want to monitor are not readily available from cluster design documents, cluster launch scripts, or knowledgeable personnel, the following might assist with discovery of the required settings:

Use the Coherence MBeanConnector to add a management node to your cluster as described in section 2.2.3 Setting Up the Coherence MBean Connector at the following link: http://docs.oracle.com/cd/E18686_01/coh.37/e18682/jmx.htm#CEGBECFH.

Adjust JVM options and the class path as needed so that the MBean Connector joins the cluster.

Use jconsole to connect to the MBean Connector node, and verify that all Coherence MBeans appear in the jconsole MBeans tab (Cache,Cluster,Connection,ConnectionManager,Node,Platform,Service,StorageManager).

Save the JVM options and class path settings that work with the MBean Connector for configuring the Monitor.

Information Needed
JAR File Information: Paths to Coherence JARs and patch JARs. Paths to all JAR files that facilitate deserialization of MBeans, including JAR files for custom and third party MBeans. Paths to database JDBC JAR files.
Direct Connection - Cluster Discovery: Override File - The name of the override file, if one is used, that contains all cluster discovery parameters. WKA Connection - The name of the cluster. WKA IP or host, or WKA list. WKA port if not using default.
Multicast Parameters Used By Existing Cluster Nodes Cluster name Cluster address Cluster port Local port Edition Mode
Java Properties:
All Coherence command line override properties used by existing cluster nodes. All Java properties that effect communication with cluster nodes such as network protocol properties. JMX authentication properties if applicable.

Proceed to Quick Start, next to install, configure and start the Monitor using default settings.