Oracle Coherence Monitor User Guide

Oracle Coherence Monitor

User Guide

Configuring Servlets
A servlet container such as Tomcat is required for an OC Monitor Web deployment. An OC Monitor Web deployment makes use of two servlets that enable the servlet container to obtain data from OC Monitor server processes:

Display Servlet
A Display Servlet allows the servlet container to communicate with an OC Monitor Display Servlet to satisfy the servlet requests for data used in a Web page. A Display Servlet requires the IP or host name of the system where the OC Monitor Display Server is running, and the port on which the Display Server is listening. The default Display Servlet, myocm.war, uses localhost and Port 3361.
Data Servlet
The data servlet allows a desktop client to connect to an OC Monitor Data Server via the servlet container. This technique allows a remote desktop client to obtain data from an OC Monitor Data Server when firewalls or network routing prevent a direct connection. A Data Servlet requires the IP or host name of the system where the OC Monitor Data Server is running, and the port on which the Data Server is listening. The default Data Servlet, myocm_rtdata.war, uses localhost and Port 3381.

OC Monitor Display and Data Servlets are configured and built using batch files and shells scripts provided for that purpose which are found in the webconf subdirectory of the OC Monitor installation.

NOTE: An initial or test deployment can use the WAR files in the webconf directory, which are based on the default ports, as long as the default ports are available.

Example: The OC Monitor for Coherence cluster DevClusterA is deployed with Tomcat running on WebHost1. The OC Monitor Data Server and Display Server are running on DevHost1.

Windows

1. Navigate to the webconf directory of the OC Monitor installation using Windows Explorer.

2. Make a copy of make_myocm_wars.bat for building the DevClusterA servlets named make_DevClusterA_wars.bat.

3. Edit make_DevClusterA_wars.bat with the following changes:

	Change From:	Change To:
	call make_ocmonitor_war myocm localhost 3361	call make_ocmonitor_war DevClusterA DevHost1 3367

	call make_rtvdata_war myocm localhost 3381	call make_rtvdata_war DevClusterA DevHost1 3387

4. Save the file.

5. Double-click make_DevClusterA_wars.bat to create the new WAR files.

6. Deploy the servlets by transferring them to Tomcat’s webapps directory on WebHost1.

UNIX/Linux

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

2. Run the OC Monitor initialization script.
Example: . ./rtvoc_init.sh (note there are two periods with a space between them)

3. Navigate to the webconf directory.
Example: cd webconf

4. Make a copy of make_myocm_wars.sh for building the DevClusterA servlets named make_DevClusterA_wars.sh.
Example: cp make_myocm_wars.sh make_DevClusterA_wars.sh

5. Edit make_DevClusterA_wars.sh with the following changes:

	Change From:	Change To:
	./make_ocmonitor_war.sh myocm localhost 3361	./make_ocmonitor_war.sh DevClusterA DevHost1 3367

	./make_rtvdata_war.sh myocm localhost 3381	./make_rtvdata_war.sh DevClusterA DevHost1 3387

6. Save the file

7. Execute the script to create the new WAR files.
Example: ./make_DevClusterA_wars.sh

8. Deploy the servlets by transferring them to Tomcat’s webapps directory on WebHost1.

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.