Using Tomcat Toolkit in a HP Serviceguard Cluster README Revision: B.06.00

ManualsBrandsHP ManualsSoftwareHP Serviceguard Enterprise Cluster Master Toolkit

Using Tomcat Toolkit in a HP Serviceguard Cluster

========================================================================

Revision: B.06.00

CONTENTS:

A. Tomcat package configuration Overview

B. Configuring the Tomcat Servlet engine with Serviceguard

C. Setting Up the Package

D. Setting Up the Toolkit

D.1 Toolkit overview

D.2 Toolkit user configuration

E. Error Handling

F. Tomcat Servlet engine maintenance

G. Configuring Apache web server with Tomcat in a single package

PREFACE:

This document describes the toolkit that integrates and runs HP Tomcat

in the HP Serviceguard environment. This README file is intended for

users who want to install, configure, and execute the Tomcat servlet

engine application in a Serviceguard clustered environment. It is

assumed that users of this document are familiar with Serviceguard and

the Tomcat Servlet engine, including installation, configuration, and

execution.

NOTE: This toolkit supports:

- HP Serviceguard versions

* A.11.19

* A.11.20

- Tomcat version that is available with HP Web Server Suite(WSS)

2.X and 3.X

- HP-UX 11i v2 and HP-UX 11i v3

At time of publication, this version supports the above mentioned SG,

application and HPUX versions. More recent versions of these

products may be certified with B.06.00. For the latest information,

see the compatibility matrix located at:

http://docs.hp.com/en/ha.html

NOTE:

This version of the toolkit supports both, legacy and modular style

packages.

NOTE:

Unless otherwise stated, this toolkit supports all filesystems,

storage and volume managers that Serviceguard supports other than CFS.

Summary of content (19 pages)

PAGE 1
Using Tomcat Toolkit in a HP Serviceguard Cluster ======================================================================== Revision: B.06.00 CONTENTS: A. B. C. D. Tomcat package configuration Overview Configuring the Tomcat Servlet engine with Serviceguard Setting Up the Package Setting Up the Toolkit D.1 Toolkit overview D.2 Toolkit user configuration E. Error Handling F. Tomcat Servlet engine maintenance G.
PAGE 2
This toolkit consists of a set of shell scripts for configuring, starting, monitoring, and stopping the Tomcat Servlet engine application. The toolkit works with the Serviceguard package control script, managed by Serviceguard in case of legacy packages or the Serviceguard master control script in case of modular packages. Each Tomcat instance is configured in its own Serviceguard package.
PAGE 3
acts as an interface between the Master Control Script and the Toolkit interface script (toolkit.sh). It is responsible for calling the Toolkit Configuration File Generator Script (described below). tkit_gen.sh the This script is called by the Module Script when package configuration is applied using 'cmapplyconf' to generate the toolkit user configuration file in the package directory (TKIT_DIR).
PAGE 4
If you do not set CATALINA_BASE to an explicit value, it will be initialized to the same value as is set for CATALINA_HOME (which means that the same directory is used for all relative path resolutions). NOTE: In an HP-UX 11.x installed in the environment, the Tomcat server is usually location /opt/hpws22/tomcat and the default configuration file "server.xml" resides in the sub-directory under this directory. if HP-UX WSS 2.
PAGE 5
If the user chooses to use this configuration, it is the user's responsibility to ensure the data is propagated to all nodes, and is consistently maintained. A disadvantage of storing the configuration on local disks is that this can increase the chance of the configuration for a Tomcat instance becoming inconsistent if changes are made, but not distributed to all nodes that can run that Tomcat instance.
PAGE 6
To manage a Tomcat Server with Serviceguard, the default Tomcat configuration needs to be modified. Before creating and configuring Serviceguard packages, you need to make sure that the following configurations have been completed for the Tomcat Server application for all cluster nodes: When the Tomcat Server is installed, the default instance may be automatically configured to be started during system startup via the runlevel (rc) script "hpws22_tomcatconf" in the /etc/rc.config.
PAGE 7
To configure a shared file system which is managed by LVM, you need to create volume group(s) and logical volume(s) on the shared disks and construct a new file system for each logical volume for the Tomcat Server web applications (and CATALINA_BASE). Static web data such as web pages with no data update features may reside on a local disk. However, all web data that needs to be shared must reside on shared storage. This data may contain dynamic data generated and updated by a client's HTTP POST request.
PAGE 8
NOTE: As mentioned before, under shared configuration, you can choose to put the Tomcat binaries as well in a shared file system. You can configure this by 2 methods: Suppose you wish to create a shared configuration for the Tomcat Server on the shared file system mounted at /mnt/tomcat: Method #1 1. Create the shared storage that will be used to store the Tomcat files for all nodes configured to run the Tomcat package.
PAGE 9
5. Now you can configure the hatomcat.conf file as required for the Tomcat Server package on all nodes in case of legacy packages and the Tomcat toolkit parameters in the package ASCII file in case of modular packages. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NOTE: The following sections describe the method for creating the Serviceguard package using the legacy method.
PAGE 10
control (tomcat_pkg.cntl) files, cd to the package directory (example, cd /etc/cmcluster/pkg/tomcat_pkg1). 1. Create a Serviceguard package configuration file with the command "cmmakepkg -p tomcat_pkg1.conf". The package configuration file "tomcat_pkg1.conf" must be edited as indicated by the comments in that file. The package name must be unique within the cluster. Example: PACKAGE_NAME tomcat_pkg1 NODE_NAME node1 NODE_NAME node2 RUN_SCRIPT HALT_SCRIPT /etc/cmcluster/pkg/tomcat_pkg1/http_pkg.
PAGE 11
function customer_defined_run_cmds { # Start the Tomcat Web Server. /etc/cmcluster/pkg/tomcat_pkg1/toolkit.sh start test_return 51 } Edit the customer_defined_halt_cmds function to execute the toolkit.sh script with the stop option. In the example below, the line "/etc/cmcluster/pkg/tomcat_pkg1/toolkit.sh stop" was added, and the ":" null command line deleted. EXAMPLE: function customer_defined_halt_cmds { # Stop the Tomcat Web Server. /etc/cmcluster/pkg/tomcat_pkg1/toolkit.sh stop test_return 51 } 3.
PAGE 12
control script. The scripts used in legacy packages are: User Configuration file (hatomcat.conf) This script contains a list of pre-defined variables that may be customized for the user's environment. This script provides the user a simple format of the user configuration data. This file will be included (that is, sourced) by the toolkit main script hatomcat.sh. Main Script (hatomcat.sh) This script contains a list of internal-use variables and functions that support the start and stop of a Tomcat instance.
PAGE 13
directory that contains its own server configuration file (server.xml). The Tomcat server default server root directory is "/opt/hpws22/tomcat".However, if you want to have multiple instances running in a cluster, you need to set a value for this variable. JAVA_HOME (For example: JAVA_HOME=/opt/java1.5 This is the base directory of Java Development a pre-requisite for running Tomcat kit.
PAGE 14
RETRY_TIMES (For example: RETRY_TIMES=2) This variable holds the number of times to attempt to check the 'tomcat' daemon processes before giving up and exiting to fail state. If not defined, its default value will be 2. For the alert mail notification feature, an additional parameter called ALERT_MAIL_ID is introduced in the ADF. ALERT_MAIL ID: Sends an email message to the specified email address when packages fail.
PAGE 15
3. Apply the Serviceguard package configuration "cmapplyconf -P tomcat_pkg.conf". using the command You can use the same procedures to create multiple Tomcat instances for Serviceguard packages that will be running on the cluster. E. Error Handling On startup, the Tomcat server application will check for the existence of the server.
PAGE 16
configuration file, hatomcat.conf. If this file is changed, please remember to distribute the new file to all cluster nodes). - Start the tomcat instance again if you stopped it cd /etc/cmcluster/pkg/tomcat_pkg1/ $PWD/toolkit.sh start - Allow monitoring scripts to continue normally as shown below: rm -f /etc/cmcluster/pkg/tomcat_pkg1/tomcat.debug A message "Starting Tomcat toolkit monitoring again after maintenance" appears in the Serviceguard Package Control script log.
PAGE 17
1. mkdir -p /etc/cmcluster/pkg/http_pkg1 /etc/cmcluster/pkg/tomcat_pkg1 2. Copy the Apache and Tomcat toolkits files into the respective directories. 3. Edit the user configuration files of both Apache and Tomcat and make suitable changes. Please refer to the README files for each of the toolkits for more details. 4. cd /etc/cmcluster/pkg/tomcat_pkg1 5. Create the Serviceguard Package configuration and Package control scripts cmmakepkg -p pkg1.
PAGE 18
SERVICE_NAME[1]="http_pkg1.monitor" SERVICE_CMD[1]="/etc/cmcluster/pkg/http_pkg1/toolkit.sh monitor" SERVICE_RESTART[1]="" Edit the customer_defined_run and customer_defined_halt function as shown below:function customer_defined_run_cmds { # ADD customer defined run commands. /etc/cmcluster/pkg/tomcat_pkg1/toolkit.sh start /etc/cmcluster/pkg/http_pkg1/toolkit.sh start test_return 51 } function customer_defined_halt_cmds { # ADD customer defined run commands. /etc/cmcluster/pkg/tomcat_pkg1/toolkit.
PAGE 19
constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.