Oracle Coherence Monitor User Guide

Configuring Desktop Clients
This section is optional.

Most OC Monitor installations use the full Web deployment which does not require desktop clients. However, the OC Monitor and RTView Builder desktop clients are sometimes useful with small test or development clusters. There are also times when the Builder is required to perform advanced configuration tasks.

There are three options for using the OC Monitor and Builder desktop clients:

• Standalone Operation
• Data Server Connection
• Data Servlet Connection

Standalone Operation
In a standalone operation setup the OC Monitor or Builder connects to the cluster either directly or via JMX.

1.    Configure as described in Configuring a JMX Connection or Configuring a Direct Connection. For details about choosing a data connection method, see Configuring a Data Connection.

2.    Use the following scripts to start the desktop clients:

Windows:
Win_RunOCMonitor.bat

     There are three methods for executing the scripts:

• Double-click the batch files in the OC Monitor bin directory.
• Double-click rtvoc_cmd.bat in the OC Monitor installation directory to open an initialized command prompt window, then change to a cluster project directory such as myocm.
• Use the OC Monitor desktop shortcuts (created by rtvoc_setup.bat).

UNIX/Linux:
Unix_RunOCMonitor.sh

Data Server Connection
In a Data Server connection setup the OC Monitor or Builder connects to an OC Monitor Data Server. The connection is defined in the cluster property file found in the conf subdirectory of the OC Monitor installation. 

1.    Open the cluster property file in a text editor.

       The line that defines the ocm.dataserver_url property is the line of interest:

ocm.dataserver_url=-dataserver://dataserver_host:dataserver_port

2.    Make the following changes:

• Change dataserver_host to the IP address or host name of the system hosting the Data Server.
• Change the dataserver_port to the port that the Data Server is listening on.

3.    Use the following scripts to start the desktop clients:

Windows:
Win_RunOCMonitor_DS.bat

There are three methods for executing the scripts:

• Double-click the batch files in the OC Monitor bin directory.
• Double-click rtvoc_cmd.bat in the OC Monitor installation directory to open an initialized command prompt window, then change to a cluster project directory such as myocm.
• Use the OC Monitor desktop shortcuts (created by rtvoc_setup.bat).

UNIX /Linux:
Unix_RunOCMonitor_DS.sh

Data Servlet Connection
In a Data Servlet connection setup the OC Monitor or Builder connect to an OC Monitor Data Server using a Data Servlet hosted by a servlet container such as Tomcat. The connection is defined in the cluster property file found in the conf subdirectory of the OC Monitor installation.

1.    Open the cluster property file in a text editor.

       The line that defines the ocm.dataserver_url property is the line of interest:

ocm.dataserver_url=-dataserver:remote:http://http_host:http_port/myocm_rtvdata

2.    Make the following changes:

• Change http_host to the IP address or host name of the system hosting the servlet container.
• Change the http_port as needed to the port that the servlet container is listening on.
• Change myocm_rtvdata to the name of the Data Servlet that connects to the OC Monitor Data Server (DevClusterA_rtvdata).

3.    Use the following scripts to start the desktop clients:

Windows:
Win_RunOCMonitor_DS.bat

There are three methods for executing the scripts:

• Double-click the batch files in the OC Monitor bin directory.
• Double-click rtvoc_cmd.bat in the OC Monitor installation directory to open an initialized command prompt window, then change to a cluster project directory such as myocm.
• Use the OC Monitor desktop shortcuts (created by rtvoc_setup.bat).

UNIX/Linux:
Unix_RunOCMonitor_DS.sh

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