Oracle Coherence Monitor User Guide

Oracle Coherence Monitor

User Guide

Verifying Your Configuration

The purpose of this section is to verify that your OC Monitor configuration (performed in earlier sections of this documentation) is operating properly before moving on to a full Web deployment.

Windows
On Windows, use the standalone OC Monitor to test data acquisition from the cluster.

1. Navigate to the bin directory of the OC Monitor installation and double-click the file Win_RunOCMDatabase.bat.

A command prompt window appears for the HSQLDB database.

2. Double-click the file Win_RunOCMonitor.bat.

A command prompt window appears, followed by the OC Monitor application.

3. Inspect the messages that appear in the command prompt window for errors.

If there are no errors, the Cluster Overview display appears. Your OC Monitor configuration is operating properly. It takes at least two JMX retrieval cycles to obtain data and fully populate the displays. Proceed to full deployment as described in the section Starting the Monitor.
If there are errors they appear in the command prompt window, or display fields remain empty. Proceed to Step 4.

4. Perform the following steps:

Note the errors that occurred.
Terminate the OC Monitor.
Modify the configuration files as needed.
Restart the OC Monitor.

5. Repeat steps 2 – 4 as needed to resolve any data acquisition issues.

Proceed to Starting the Monitor.

UNIX/Linux
1. Open a command prompt window and navigate to the OC Monitor installation directory.
Example: cd /opt/rtvoc_55c1

2.    Execute the Initialization script:
       Bourne shell:
       . ./rtvoc_init.sh (note that there are two periods with a space between them)

       Bash shell:
       source rtvoc_init.sh

3. Navigate to the myocm directory.
Example: cd projects/myocm

4. Start HSQLDB.
Example: Unix_RunOCMDatabase.sh –bg

5.    Check the HSQLDB log file for errors.
       Example without errors:
        cat hsqldb.log
        [Thread[main,5,main]]: checkRunning(false) entered
        [Thread[main,5,main]]: checkRunning(false) exited
        Startup sequence initiated from main() method
        Loaded properties from [/home/m/SLTest/rtvoc_55c1/projects/myocm/server.properties]
        Initiating startup sequence...
        Server socket opened successfully in 8 ms.
        Database [index=0, id=0, db=file:DATA/alertdefs, alias=alertdefs] opened sucessfully in 452 ms.
        Database [index=1, id=1, db=file:DATA/rtvhistory, alias=rtvhistory] opened sucessfully in 878 ms.
        Startup sequence completed in 1341 ms.
        2009-11-20 11:16:56.800 HSQLDB server 1.8.0 is online
        To close normally, connect and execute SHUTDOWN SQL
        From command line, use [Ctrl]+[C] to abort abruptly

6. Start the Data Server.
Example: Unix_RunOCMDataServer.sh -bg

7. Carefully inspect the Data Server log file, dataserver.log, for OC Monitor and Coherence errors.

NOTE: Coherence can produce a large number of long messages making errors difficult to notice. Common errors at this stage are "class not found" errors due to missing JAR files, and incorrect or blocked ports.

If there are no errors, proceed to Starting the Monitor.
If there are errors proceed to Step 8.

8. Terminate the Data Server and correct any configuration errors found.
Example: Unix_StopOCM.sh -data

9. Repeat steps 6 – 8 as needed until the Data Server output produces no errors.

10. Terminate the data server and HSQLDB and use “ps –ef | grep hsqldb” to find the HSQLDB process.

Proceed to Starting the Monitor.

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, 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.