Oracle Coherence Monitor User Guide

Oracle Coherence Monitor

User Guide

Before Installing OCM
Prior to installing the OC Monitor:

Verify System Requirements for the OC Monitor (next).
Verify System setup for monitoring Oracle for Coherence.
Obtain Information You Need for installing OCM.

System Requirements

Platforms Supported
All OS that supports Sun’s JDK (Win XP, 2000, NT, Solaris 2.x, Linux)

Hardware Requirements
Processor: 1 GHz or higher multi-core (multi CPU) processor minimum.
RAM: 4 -8 gigabytes (GB) of RAM or higher recommended.

Software Requirements
Java: Minimum JRE 1.5.0+ recommended;
JDK required for compiling servlet code, custom functions and custom commands.
Coherence 3.3.1 or higher.
Database with available JDBC or ODBC drivers.
The default shell for UNIX/Linux systems must be a Bourne compatible shell such as sh or bash.

Memory Requirements
Data Server: 1 GB heap recommended.
Display Server: 1 GB heap recommended.
Historian: 1 GB heap or higher recommended.

Network Connectivity Requirements
The Data Server must reside on a system that has network connectivity with systems that host Coherence cluster nodes.
Display Server and Historian must reside on systems with network connectivity to the system hosting the Data Server.

Verify System
Verify Coherence Settings and JMX Compatibility, and make adjustments as needed.

Coherence Settings
Verify that your Coherence cluster is configured with unique Member Names for each node. For information, see Oracle Coherence documentation: http://docs.oracle.com/cd/E18686_01/coh.37/e18677/cluster_setup.htm#CEGHGHGD.

JMX Compatibility
Verify that your system is able to monitor Coherence using JMX. See Using JMX to Manage Coherence at the following link: http://docs.oracle.com/cd/E18686_01/coh.37/e18682/jmx.htm. Specifically consider section 2.2 Accessing Coherence MBeans: http://docs.oracle.com/cd/E18686_01/coh.37/e18682/jmx.htm#BABDIEJG.

Information You Need for Installing OCM
Use the following check list to gather information you need for installing the OC Monitor application. If the Java properties and class path used by the cluster you want to monitor are not readily available from cluster design documents, cluster launch scripts, or knowledgeable personnel, the following might assist with discovery of the required settings:

Use the Coherence MBeanConnector to add a management node to your cluster as described in section 2.2.3 Setting Up the Coherence MBean Connector at the following link: http://docs.oracle.com/cd/E18686_01/coh.37/e18682/jmx.htm#CEGBECFH
Adjust JVM options and the class path as needed so that the MBean Connecter joins the cluster.
Use jconsole to connect to the MBean Connector node, and verify that all Coherence MBeans appear in the jconsole Mbeans tab. (Cache,Cluster,Connection,ConnectionManager,Node,Platform,Service,StorageManager)
Save the JVM options and class path settings that work with the MBean Connector for configuring OCM.

Area	Information Needed		Notes
JAR File Information	Paths to Coherence JARs and patch JARs.
	Paths to all JAR files that facilitate deserialization of MBeans, including JAR files for custom and third party MBeans.
	Paths to database JDBC JAR files.

Direct Connection - Cluster Discovery	Override File - The name of the override file, if one is used, that contains all cluster discovery parameters.
	WKA Connection	The name of the cluster.
		WKA IP or host, or WKA list.
		WKA port if not using default.
	Multicast Parameters Used By Existing Cluster Nodes	Cluster name
		Cluster address
		Cluster port
		Local port
		Edition
		Mode

JMX Connection to An Existing MBean Server	JMX Remote Port Connection	The IP or host name.
		The port number.
	JMX RMI Adapter Connection	The URL for the connection.
	Authenticated JMX Remote Port Connection	The name of the connection in JMXOPTIONS.ini (created using the Builder).

Java Properties
	All Coherence command line override properties used by existing cluster nodes.
	All Java properties that effect communication with cluster nodes such as network protocol properties.
	JMX authentication properties if applicable.

Proceed to Installing OCM for Windows or UNIX/Linux when you have all the above information. If you are connecting to a single Coherence cluster, using the Direct Connection data connection method, and are using the default settings, you can use the Quick Start instructions.

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.