Installing and Configuring Sun Cluster HA for Apache Tomcat
Installing and Configuring Solaris Cluster HA for Apache Tomcat
Solaris Cluster HA for Apache Tomcat
Planning the Solaris Cluster HA for Apache Tomcat Installation and Configuration
Apache Tomcat and Solaris Containers
Solaris Cluster HA for Apache Tomcat as a scalable configuration
Solaris Cluster HA for Apache Tomcat as a multiple master configuration
Restriction to deploy Oracle Solaris Cluster HA for Apache Tomcat in a scalable configuration
Restriction for the Load_balancing_policy
Restriction for Scalable Services and Solaris Containers
Restriction for the Apache Tomcat smf Service Name in a Failover Zone
Location of the Tomcat Home Directory for Scalable or Multiple Masters Configurations
Load Balancing for Multiple Master Configurations
Location of the Tomcat Home Directory for Failover Configurations
Apache Tomcat Component Dependencies
Apache Tomcat Configuration and Registration Files
Installing and Configuring Apache Tomcat
How to Enable Apache Tomcat to run in a Global Zone Configuration
How to Install and Configure Apache Tomcat in the Global Zone
How to Enable Apache Tomcat to run in a Zone Configuration
How to Install and Configure Apache Tomcat in a Zone
How to Enable Apache Tomcat to run in Failover Zone Configuration
How to Install and Configure Apache Tomcat in a Failover Zone
Verifying the Installation and Configuration of Apache Tomcat
How to Verify the Installation and Configuration of Apache Tomcat
How to Deploy the Apache Tomcat Application
Installing the HA for Apache Tomcat Packages
How to Install the HA for Apache Tomcat Packages
Registering and Configuring Solaris Cluster HA for Apache Tomcat
How to Register and Configure Solaris Cluster HA for Apache Tomcat as a Failover Data Service
How to Register and Configure Solaris Cluster HA for Apache Tomcat as a Scalable Data Service
Configuring Oracle Solaris Cluster HA for Apache Tomcat in Zones
Configuring Oracle Solaris Cluster HA for Apache Tomcat in a Failover Zone
How to Register Oracle Solaris Cluster HA for Apache Tomcat in a Failover Zone
How to Modify Parameters in the Oracle Solaris Cluster HA for Apache Tomcat Manifest
How to Remove a Oracle Solaris Cluster HA for Apache Tomcat Resource From a Failover Zone
Configuring Oracle Solaris Cluster HA for Apache Tomcat in a Zone
How to Register Oracle Solaris Cluster HA for Apache Tomcat in a Zone
Verifying the Solaris Cluster HA for Apache Tomcat Installation and Configuration
How to Verify the Solaris Cluster HA for Apache Tomcat Installation and Configuration
Understanding the Solaris Cluster Apache Tomcat HA Parameter File
Understanding Solaris Cluster HA for Apache Tomcat Fault Monitor
Probing Algorithm and Functionality
Debugging HA for Apache Tomcat
How to Activate Debugging for HA for Apache Tomcat
A. Deployment Example: Installing Apache Tomcat in the Global Zone
B. Deployment Example: Installing Apache Tomcat in a Failover Zone
C. Deployment Example: Installing Apache Tomcat in a Non-Global Zone
Use the information to understand the contents of the Solaris Cluster Apache Tomcat HA parameter file. This section describes the structure and the content of the Solaris Cluster Apache Tomcat HA parameter file, as well as the strategy to chose some of its variables.
Apache Tomcat HA uses a parameter file to pass parameters to the start, stop and probe command. This parameter file needs to be a valid Korn shell script which sets several variables. The structure of this file appears in Table 6. For examples of the parameter file refer to Registering and Configuring Solaris Cluster HA for Apache Tomcat.
Table 6 Structure of the Apache Tomcat HA parameter file
|
The parameters in Table 6 can be changed at any time. The only difference is when changes take effect.
The following parameters of the Apache Tomcat HA parameter file are used for starting and stopping Apache Tomcat. Changes to these parameters take effect at every restart or disabling and enabling of a Apache Tomcat resource.
EnvScript
User
Basepath
Startwait
The following parameters of the Apache Tomcat HA parameter file are used within the fault monitor. Changes to these parameters take effect at every Thorough_probe_interval.
Host
Port
TestCmd
ReturnString
Alternatives are available to chose the ReturnString:
Take the start page of your application and set the TestCmd to get /start_page. Set the ReturnString to a string contained in the startpage. With this strategy, you are monitoring that Apache Tomcat is serving your application.
Take the Apache Tomcat default startpage and set the TestCmd to get /default-startpage. In this case, set the ReturnString to a string contained in the startpage. This string depends on the deployed Apache Tomcat version, for 3.x it is Tomcat home and for 4.x and 5.x it is CATALINA. With this strategy, you are monitoring that Apache Tomcat is serving its default application.
Deploy a test application (which is not provided with the Solaris Cluster Apache Tomcat agent) to Apache Tomcat. Set the TestCmd to get /startpage-of-the-application. In this case, set the ReturnString to a string contained in the startpage. With this strategy, you are monitoring that Apache Tomcat is serving your test application.
If none of above is appropriate, set the TestCmd to get /a-page-which-does-not-exists. In this case, set the ReturnString to a string contained in the Error Page. With this strategy, you are monitoring that Apache Tomcat is operational, because it registers that it must deliver a page that does not exist.
You can evaluate the different pages by connecting using a browser with hostname:port and specifying the different pages.