Oracle Coherence Monitor

User Guide

 

Configuring a Data Connection
This section provides step-by-step instructions for configuring a connection to acquire data from the cluster. There are five data connection method options: a direct connection, three types of JMX connection methods, and an OCM agent. JMX connection methods are generally used for small clusters, and direct or OCM agent connection methods are generally used for large clusters. NOTE: To configure the OC Monitor for multiple Coherence clusters a JMX connection method is required.

See Data Connection Methods for an overview of data connection methods.

If you have an existing management node in your cluster, choose the JMX connection variant that applies. If you do not have an existing management node in your cluster, see the following requirements.

See Appendix A - JMX Connection Choices for details about JMX connection options.

The data connection method options are:
  • JMX Remote Port
    The JMX Remote Port method requires changes to the OC Monitor configuration files for the selected node. The selected node must also be restarted.
     
  • JMX RMI URL Connection
    The MBeanConnector class provided with the OC Monitor is often used for this purpose. The OC Monitor MBeanConnector is described at http://wiki.tangosol.com/display/COH35UG/How+to+Manage+Coherence+Using+JMX. This method requires a change to your cluster startup to include an MBeanConnector node.
     
  • Named JMX Connection
    This method is can be used with both the JMX remote port and the JMX RMI URL connection methods. Use this method when the JMX connection requires a user name and password.
     
  • Multi-Cluster Configuration
    This method is suitable for monitoring many small clusters with a single OCM instance, or for monitoring a single large cluster. This method consolidates the monitoring of Coherence clusters (rather than having a monitoring system for each cluster), is easy to configure (using one of the JMX Connection methods) and requires a single historical database instance.
  • OCM Agent
    This method is generally used for large clusters     to minimize the amount of garbage collection associated with collecting and processing JMX monitoring data.

Initializing a Command Prompt or Terminal Window

 To start any OC Monitor process (Data Server, Historian, Viewer and so forth), you must first initialize a command line window on the host. UNIX scripts are Bourne shell compatible.

To initialize a command line window, execute the rtvoc_init script. For example:

Windows
Go to your OC Monitor installation directory and type:

        rtvoc_init

UNIX
The script used to initialize a terminal window depends on whether you are in csh or rsh (e.g. Linux, Mac OS X). With a Bourne shell, open a terminal window, go to your OC Monitor installation directory and type:

        . \rtvoc_init.sh

 

 

 

 

 


 

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.