Before You Begin
Determine how Apache Tomcat will be deployed in Oracle Solaris Cluster.
Ensure that you have enabled Apache Tomcat to run in a failover, multiple-masters, or scalable data service.
For conceptual information on scalable and failover data services, see Concepts for Oracle Solaris Cluster 4.4.
Determine which user name will run Apache Tomcat.
Determine how many Apache Tomcat versions and instances will be deployed.
If more than one instance of a version will be deployed, determine whether they share the binaries.
Determine which cluster file system will be used by each Apache Tomcat instance.
Caution - In this scenario, the deployment of the Apache Tomcat group and user needs to occur on every node where Apache Tomcat is hosted.
If Apache Tomcat is to run under a non-root user, you have to create the appropriate user and the appropriate group. For these tasks, use the following commands.
# su - user-name
If you deploy Apache Tomcat as a failover data service, install Apache Tomcat onto a shared file system within Oracle Solaris Cluster.
You should install Apache Tomcat onto shared disks. For a discussion of the advantages and disadvantages of installing the software on a local versus a cluster file system, see Determining the Location of the Application Binaries in Planning and Administering Data Services for Oracle Solaris Cluster 4.4.
If you will deploy Apache Tomcat as a failover data service ,install the Apache Tomcat binaries on the shared storage on one node. If Apache Tomcat will be deployed as a scalable or a multiple-masters data service, install the Apache Tomcat binaries on the local storage on every node, that will host the Apache Tomcat data service.
If you deploy Apache Tomcat as a scalable data service for a scalable or a multiple-masters configuration, repeat the following step at every node that will host Apache Tomcat.
Create a Korn shell or a C shell script (dependent on the login-shell of your Apache Tomcat user name) to set the environment variables for Apache Tomcat. You must set the environment variables in a shell script and not in the user's profile.
With this mechanism you can install and run multiple Apache Tomcat versions and instances under one user name.
# more env.ksh #!/usr/bin/ksh # # Environment for Tomcat # JAVA_HOME=/usr/j2se export JAVA_HOME CATALINA_HOME=/global/mnt1/jakarta-tomcat-6.0.28 export CATALINA_HOMEExample 2 C Shell Script to Set the Environment Variables for Apache Tomcat
# more env.csh #!/usr/bin/csh # # Environment for Tomcat # setenv JAVA_HOME /usr/j2se setenv CATALINA_HOME /global/mnt1/jakarta-tomcat-6.0.28
The environment variables are version and configuration dependent.