Oracle Coherence Monitor

Enterprise RTView®
User Guide

Oracle® Coherence Monitor - Running the Oracle® Coherence Monitor

There are two ways the Oracle Coherence Monitor (OCM) can communicate with a Coherence cluster: via remote JMX port or by running the Oracle Coherence Monitor as a management node. Instructions on how to run the OCM are different depending on your selected option. Before following the instructions below, refer to Oracle Coherence Monitor Communication Options to select a communication mode.

To run the Oracle Coherence Monitor, Display Server, Data Server, Historian or Report Generator you will use one of the following command line arguments:

-ocm	Used for all applications, except the OCM, when running via remote JMX port.
-ocmnode	Used for all applications, including the OCM, when running as a management node.

NOTE: When using multiple command line arguments, these must come first. For example, run_ocmonitor -ocmnode -u1000 will work; run_ocmonitor -u1000 -ocmnode will not.

Run HSQLDB Database
The Oracle Coherence Monitor will try to connect to a Historian database and an alert database at startup. If these databases are not running, history and alert data will not be available in the OCM. By default, the Oracle Coherence Monitor is configured to connect to the HSQLDB database in the demos\ocmdemo directory for both the history and alert data. Unless you have customized the Historian database, or do not want to see history and alert data, be sure this HSQLDB database is running before you start the OCM.

In an initialized command window go to demos\ocmdemo and type:

run_hsqldb

Type Ctrl-C in the database console to shutdown the database. On shutdown, the database writes all of its memory to rtvhistory.log. When it restarts, it uses this .log file to restore data from the previous session. If you want to clear the data in the database, in demos\ocmdemo type:

reset_history

Run OCM via Remote JMX Port

1. Confirm that you have completed setup for monitoring the grid via remote JMX port.

2. By default, the Oracle Coherence Monitor is setup to attach to port 9991 on localhost with no authentication. If this is not correct for your setup, you must customize the RemoteJmxRMI connection to point to the IP address of the machine running the Coherence node enabled with JMX remote capability and the exposed JMX port.

3.In an initialized command window type:

run_ocmonitor

4. Enter user credentials in the login screen.

Run OCM as Management Node

1. Confirm that you have completed setup for running the OCM as a management node.

2. In an initialized command window type:

run_ocmonitor -ocmnode

3. Enter user credentials in the login screen.

Enterprise RTView contains components licensed under the Apache License Version 2.0.

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, Enterprise 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-2009 Sherrill-Lubinski Corporation. All Rights Reserved.