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
Structure of the Apache Tomcat HA parameter file
Strategy to Chose the TestCmd and the ReturnString Variable
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
The Oracle Solaris Cluster HA for Apache Tomcat can be configured in afailover zone and in a zone. This section describes the additional steps which are necessary to configure Oracle Solaris Cluster HA for Apache Tomcat in both zone types.
This procedure uses the configuration file to register Oracle Solaris Cluster HA for Apache Tomcat in a failover zone.
Before You Begin
Before you register Oracle Solaris Cluster HA for Apache Tomcat in a failover zone, perform the following tasks. Follow procedures in the Oracle Solaris Cluster Data Service for Solaris Containers Guide and Oracle Solaris Cluster Data Service for Apache Tomcat Guide.
Install Oracle Solaris Cluster HA for Containers and Oracle Solaris Cluster HA for Apache Tomcat data-service packages in the global zone of each cluster node that you want to run the failover zone.
Create the failover zone.
Configure the boot component to control your failover zone.
You can place this configuration file in any directory that is accessible to the failover zone.
These variables are used only when the data service is installed in a non-global zone. Set the values of these variables as follows:
Set the name of the zone where Oracle Solaris Cluster HA for Apache Tomcat should run.
Set the name of the resource that controls the zone.
Set the name of the Sun Resource Manager Project in the failover zone. If the PROJECT variable is omitted from the configuration file, the data service uses the default project of the user, :default, in a Solaris Service Management Facility (SMF) context. This project name is placed in the start/project property and the stop/project property of the SMF service.
Note - Keep this modified configuration file for possible future use.
# ksh /opt/SUNWsctomcat/util/sctomcat_register -f filename
Specifies the configuration file name.
The configuration file name.
The registration of Oracle Solaris Cluster HA for Apache Tomcat generates an SMF manifest and registers an SMF service in the failover zone that is specified by the ZONE variable in the configuration file. The manifest is named resourcename.xml, where resource is the name that is specified by the RS variable in the configuration file. This manifest is placed in the /var/svc/manifest/application/sczone-agents/ directory. The SMF service is named svc:/application/sczone-agents/resource.
The Oracle Solaris Cluster HA for Apache Tomcat data service uses the SMF component of the Oracle Solaris Cluster HA for Containers data service to control and probe this SMF service of the Oracle Solaris Cluster HA for Apache Tomcat. It registers a Oracle Solaris Cluster HA for Containers SMF component on top of the already-created SMF service. The name of the script that starts and stops the manifest as well as probes the SMF component is control_sctomcat.
Perform this task to change parameters in the Oracle Solaris Cluster HA for Apache Tomcat manifest and to validate the parameters in the failover zone. Parameters for the Oracle Solaris Cluster HA for Apache Tomcat manifest are stored as properties of the SMF service. To modify parameters in the manifest, change the related properties in the SMF service then validate the parameter changes.
# svccfg svc:/application/sczone-agents:resource
For more information, see the svccfg(1M) man page.
# /opt/SUNWsctomcat/bin/control_sctomcat validate resource
Messages for this command are stored in the /var/adm/messages/ directory of the failover zone.
# clresource disable resource # clresource delete resource
# /opt/SUNWsctomcat/util/sctomcat_smf_remove -f filename
Specifies the configuration file name.
The name of the configuration file that you used to register Oracle Solaris Cluster HA for Apache Tomcat with the SMF service.
Note - If you no longer have the configuration file that you used to register Oracle Solaris Cluster HA for Apache Tomcat with the SMF service, create a replacement configuration file:
Make a copy of the default file, /opt/SUNWsctomcat/util/sctomcat_config.
Set the ZONE and RS parameters with the values that are used by the data service.
Run the sctomcat_smf_remove command and use the -f option to specify this configuration file.
This procedure uses the configuration file to register Oracle Solaris Cluster HA for Apache Tomcat in a zone.
Before You Begin
Before you register Oracle Solaris Cluster HA for Apache Tomcat in a zone, perform the following tasks. .
Install Oracle Solaris Cluster HA for Apache Tomcat data-service packages in the global zone of each cluster node that you want to run the zone.
Create the zone on each node to host Oracle Solaris Cluster HA for Apache Tomcat.
Note - The zones configuration parameter autoboot must be set to true
These variables are used only when the data service is installed in a non-global zone managed by the Container Agent.
Note - Keep this modified configuration file for possible future use.
# ksh /opt/SUNWsctomcat/util/sctomcat_register -f filename
Specifies the configuration file name.
The configuration file name.