Oracle Coherence Monitor User Guide

Oracle Coherence Monitor

User Guide

Quick Start - Installation & Setup

If you are connecting to a single Coherence cluster, using the Direct Connection data connection method (in which the OC Monitor joins the Coherence cluster as a node) and are using the default settings, you can use the following Quick Start instructions. If you are using a different connection method, refer to the standard Windows or UNIX/Linux installation instructions.

At This Point You Have:

Viewed and completed the Before Installing OCM section of this document.

Perform the following steps to download the OC Monitor package, install and setup the OC Monitor application:

Windows (next)
UNIX/Linux

Windows (Quick Start)

To install and setup the OC Monitor

1. Download OCM 5.x.x.x and Apache Tomcat.

2. Unzip the contents to your local server.

3. Execute rtvoc_setup.bat to install the license.

4. In the conf directory, make a copy of the SampleCluster.properties file and name the copy:

mycluster_name.properties

where mycluster_name is the name of your cluster.

5. Edit the new mycluster_name.properties file as follows:

Replace MyClusterName with your cluster name and enter WKA:
tangosol.coherence.cluster=MyClusterName
tangosol.coherence.wka=

Replace MyClusterName with your cluster name in the following entries:
ocm.agent_log=MyClusterName_agent.log
ocm.data_log=MyClusterName_dataserver.log
ocm.display_log=MyClusterName_displayserver.log
ocm.historian_log=MyClusterName_historian.log

REMOVE the suffix _MyClusterName from the following entries:
ocm.cachetotals_sub=-sub:$CACHETOTALS_TABLE:CACHETOTALS_MyClusterName
ocm.nodestats_sub=-sub:$NODESTATS_TABLE:NODESTATS_MyClusterName
ocm.alertdefs_sub=-sub:$ALERTDEFS_TABLE:ALERTDEFS_MyClusterName
ocm.alertdefs_tab_sub=-sub:$ALERTDEFS_TAB_TABLE:ALERTDEFS_TAB_MyClusterName

Use the following entries only if they are setup in your cluster:
#tangosol.coherence.override=
#tangosol.coherence.mode=
#tangosol.coherence.cacheconfig=

6. Verify that the JAVA_HOME environment variable points to JDK 1.6 or above.

7. Using the JAR File information you previously obtained, edit the coherence_setup.bat script as follows:

Set COHERENCE_CLASSPATH to the JAR file paths for the version of Coherence used by the cluster.
Add any additional JAR files needed to join the cluster.
Set COHERENCE_CLUSTER to the name of the cluster property file created in step 4 (without the .properties file extension).

8. Using the Java Properties information you previously obtained, add the JVM options to RTV_JAVAOPTS in the ocm_setup.bat script.

9. Install Tomcat and set the variable CATALINA_HOME to point to the Tomcat installation.

10. Copy myocm.war to the webapps directory of Tomcat.

11. Start Tomcat by running the script startup.bat located in the bin directory.

12. Go the OCM shortcuts folder on your desktop and start up the following processes.

OCM Database
OCM Data Server
OCM Display Server (DS)
OCM Historian (DS)

13. Check the logs located in rtvoc_5.8.0.0\projects\myocm\logs for errors.

14. Open a browser from your desktop and go to the following URL to view the OC Monitor:

http://localhost:8068/myocm (login: demo/demo

UNIX/Linux (Quick Start)

To install and setup the OC Monitor

1. Download OCM 5.x.x.x and Apache Tomcat.

2. Unzip the contents to your local server using the command unzip –a OCMonitor_XXXX.zip.

3. Execute the fixperms.sh script. If you are using the Bourne shell, use the dot command to execute the script (. fixperms.sh). If you are using the Bash shell, use the source command to execute the script (source fixperms.sh).

4. Execute the rtvoc_setup.sh script to install the license (./rtvoc_setup.sh).

5. In the conf directory, make a copy of the SampleCluster.properties file and name the copy:

mycluster_name.properties

where mycluster_name is the name of your cluster.

6. Edit the new mycluster_name.properties file as follows:

Replace MyClusterName with your cluster name and enter WKA:
tangosol.coherence.cluster=MyClusterName
tangosol.coherence.wka=

Replace MyClusterName with your cluster name in the following entries:
ocm.agent_log=MyClusterName_agent.log
ocm.data_log=MyClusterName_dataserver.log
ocm.display_log=MyClusterName_displayserver.log
ocm.historian_log=MyClusterName_historian.log

REMOVE the suffix _MyClusterName from the following entries:
ocm.cachetotals_sub=-sub:$CACHETOTALS_TABLE:CACHETOTALS_MyClusterName
ocm.nodestats_sub=-sub:$NODESTATS_TABLE:NODESTATS_MyClusterName
ocm.alertdefs_sub=-sub:$ALERTDEFS_TABLE:ALERTDEFS_MyClusterName
ocm.alertdefs_tab_sub=-sub:$ALERTDEFS_TAB_TABLE:ALERTDEFS_TAB_MyClusterName

Use the following entries only if they are setup in your cluster:
#tangosol.coherence.override=
#tangosol.coherence.mode=
#tangosol.coherence.cacheconfig=

7. Verify that the JAVA_HOME environment variable points to JDK 1.6 or above.

8. Using the JAR File information you previously obtained, edit the coherence_setup.sh script as follows:

Set COHERENCE_CLASSPATH to the JAR file paths for the version of Coherence used by the cluster.
Add any additional JAR files needed to join the cluster.
Set COHERENCE_CLUSTER to the name of the cluster property file created in step 5 (without the .properties file extension).

9. Using the Java Properties information you previously obtained, add the JVM options to RTV_JAVAOPTS to the ocm_setup.sh script.

10. Install Tomcat and set the variable CATALINA_HOME to point to the Tomcat installation.

11. Copy myocm.war to the webapps directory of Tomcat.

12. Start Tomcat by running the script startup.sh located in the bin directory.

13. cd to the rtvoc_XXXX directory and execute the following scripts:

rtvoc_init.sh (Bourne shell: . rtvoc_init.sh, or Bash shell: source rtvoc_init.sh)
startocm.sh (./startocm.sh)

14. Check the logs located in rtvoc_XXXX\projects\myocm\logs for errors.

15. Open a browser from your desktop and go to the following URL to view the OC Monitor:

http://localhost:8068/myocm (login: demo/demo)

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.