Oracle Coherence Monitor User Guide

Configuring a Direct Connection
This section provides step-by-step instructions for configuring a direct connection to acquire data from the cluster. This method requires the OC Monitor Data Server to join the cluster as a node. For an overview, see the Direct Connection system diagram.

All Coherence parameters, options, configuration files and JAR files used by existing cluster nodes must be made available for Data Server configuration. This includes JARs that contain custom MBeans, patches, cluster configuration file, cache configuration file, POF configuration file and any configuration files that they reference.

To Get Coherence Parameters
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 steps 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 Connecter 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 later use in OCM configuration.

To configure a direct connection perform the following steps.
1. Open the cluster.properties file, located in the conf directory, in a text editor and make the following changes:

• sl.rtview.ocm.node=true
  
• Set Coherence Properties for Cluster Node configuration. OC Monitor cluster property files support the following Coherence command line override properties:
          tangosol.coherence.cluster
          tangosol.coherence.clusteraddress
          tangosol.coherence.clusterport
          tangosol.coherence.edition
          tangosol.coherence.mode
          tangosol.coherence.wka
          tangosol.coherence.wka.port
          tangosol.coherence.localhost
          tangosol.coherence.localport
          tangosol.coherence.override
          tangosol.coherence.cacheconfig
          tangosol.coherence.management.refresh.policy
          tangosol.coherence.management.refresh.expiry
  
• Define values for the properties that your cluster nodes use to join the cluster. If your cluster nodes require command line override properties that are not in the above list, add them to the appropriate section of the ocm_setup (.bat or .sh) script as described in Step 3.
• Uncomment, and set the value of the value of the sl.rtview.ocm.jmxconn property to the desired name of the direct connection. The name of the cluster properties file is typical for this value.
  
  Example:
  sl.rtview.ocm.jmxconn=DevClusterA
  
• Save the file.

2. Using the Jar Properties information you previously obtained, edit coherence_setup.bat or coherence_setup.sh, located in the conf subdirectory. Edit the following environment variables to match the cluster property file created previously:

• COHERENCE_CLASSPATH
  The path to the Coherence JAR files required by the existing cluster. Include any patch JARs used by cluster nodes, as well as the paths to JAR files for POF serialization.

Windows Example (coherence_setup.bat):
set COHERENCE_CLASSPATH=c:\coherence352\lib\coh-352-patch-01.jar;c:\coherence352\lib\coherence.jar

• COHERENCE_CLUSTER
  The name of the default cluster property file without the .properties file extension.

Windows Example (coherence_setup.bat):
set COHERENCE_CLUSTER= DevClusterA

3. Using the Java Properties information you previously obtained, edit ocm_setup.bat or ocm_setup.sh, located in the conf subdirectory.

• Add JVM options to RTV_JAVAOPTS.
• Add the path to the database JDBC driver, and other required JAR files to RTV_USERPATH.

The ocm_setup script needs editing if:

• the existing cluster uses Java authentication features.
• more Coherence options are needed than are supported in the cluster property files.
• additional JAR files are needed to connect to the cluster.
• additional JAR files are needed to support custom and third party MBeans.
• additional JAR files are needed for database access.
• additional file paths are needed for Coherence configuration files such as POF configuration.

4. If any of the conditions listed apply to the existing cluster, select the appropriate setup script and make the following changes:

• COHERENCE_CLASSPATH
  Add the paths to JAR files required to join the cluster.
• RTV_USERPATH
  Add the paths needed for JAR and Coherence configuration file directories required by the existing cluster, third party applications or database.
• RTV_JAVAOPTS
  Add additional Coherence overrides and Java security properties used by the existing cluster.

Proceed to Verifying Your Configuration.

RTView contains components licensed under the Apache License Version 2.0.

Treemap Algorithms v1.0  is used without modifications and licensed by MPL Version 1.1. Copyright © 2001 University of Maryland, College Park, MD

Datejs is licensed under MIT. Copyright © Coolite Inc.

jQuery is licensed under MIT. Copyright © John Resig,

JCalendar 1.3.2 is licensed under LGPL. Copyright © Kai Toedter.

jQuery is licensed under MIT. Copyright (c) 2009 John Resig, http://jquery.com/ JCalendar 1.3.2 is licensed under LGPL. Copyright © Kai Toedter.

JMS, JMX and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. They are mentioned in this document for identification purposes only. 

SL, SL-GMS, GMS, RTView, SL Corporation, and the SL logo are trademarks or registered trademarks of Sherrill-Lubinski Corporation in the United States and other countries. Copyright © 1998-2011 Sherrill-Lubinski Corporation. All Rights Reserved.