Oracle Coherence Monitor

User Guide

 

Using an OCM Agent
This section describes how to use the OCM Agent to gather data from the Coherence cluster. The OCM Agent is a method for acquiring JMX data from a Coherence cluster that reduces the occurrence of packet loss errors sometimes seen in large clusters. This method is especially useful for monitoring very large clusters containing many MBeans.

Normally, and by default, the Data Server acquires data from a Coherence cluster and supplies it to the OC Monitor.  The Data Server also aggregates and processes raw data into caches, and in the process creates large amounts of transient data. This extra overhead can cause long garbage collection pauses on a node in the cluster, and increase both communication delays and other garbage collection activity in the cluster.

The OCM Agent method employs an OCM Agent Data Server that joins the cluster and is dedicated solely to acquiring JMX data and forwarding it to the Data Server. The Data Server does not join the cluster and is dedicated solely to aggregating and processing raw data into caches. This configuration minimizes garbage collection, reducing the overhead for optimal monitoring.

To summarize the OCM Agent method process:

  1. The Data Server receives a request for a new data sample.  
  2. The Data Server forwards the request to the OC Monitor Agent Data Server.  
  3. The OC Monitor Agent Data Server provides the data to the Data Server.  
  4. The Data Server updates its caches with the new data sample.  

The OCM Agent method entails an additional Java process (the OCM Agent) and an additional connection (between the Agent and the Data Server).

These instructions assume you have a project directory, as described in OCM Setup. The rtview.properties file is located in your project directory.  

To use the OCM Agent

1.  Verify that all OC Monitor applications and the cluster are stopped. See Stopping the Monitor for details about stopping OC Monitor applications.

2.  In an initialized command window, navigate to the ocmon/projects/sample directory.

3. In the projects/sample directory, start the OCM applications by typing:

start_rtv agentmode all  
     
  NOTE: If you do not wish to start all the OC Monitor applications at once, you must start each application (or "server") individually and in the following order:  
    start_rtv agentmode database  
    start_rtv agentmode dataserver  
    start_rtv agentmode agentsender  
    start_rtv agentmode historian  
    start_rtv agentmode displayserver  

NOTE: The start_rtv script starts processes in an OCM configuration as specified in the rtvservers.dat configuration file.

The OCM Agent is now configured to gather data from the Coherence cluster.

 

 

 


 

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-2013 Sherrill-Lubinski Corporation. All Rights Reserved.