Installing and Configuring Apache Toolkit for Serviceguard for Linux

SETTING UP THE APACHE WEB SERVER APPLICATION FOR AN SG/LX
CLUSTER
Once you decide on the storage configuration option, you can install the High Availability Apache
Web Server Toolkit. However, before you start installing the toolkit, ensure that your environment
meets the following prerequisites:
HP Serviceguard for Linux must be installed on all nodes that need to be configured in the
cluster
The toolkit is installed on all the target nodes of the cluster
Apache Web Server is installed and configured on all target nodes
o The same version of the server must be installed and configured on all target
nodes.
o Identical copies of the server root directory must be available on all nodes.
o Each node must have the same document root directory that contains identical
copies of the Web documents for a particular instance.
For this white paper, the environment is assumed to be that of a cluster with two nodes with a
shared storage device and a quorum server for the cluster. However, these instructions are
applicable for a cluster that has more than two nodes, provided the prerequisites are met.
NOTE: The installation instructions illustrate commands for a Red Hat environment. If your
environment has SUSE Linux Enterprise Servers, then replace all occurrences of /usr/local with
/opt.
Installing and setting up the Apache toolkit involves the following tasks:
Set up the Apache Web Server
Install the Toolkit
Configure the Apache Web Server Packages
The following sections describe these tasks in detail.
Setting Up the Apache Web Server
To manage an Apache Web Server using Serviceguard, you need to modify the default Apache
configuration information. Before you create and configure the Serviceguard packages, ensure that
the configurations listed later in this section are completed for the Apache Web Server application
on all other cluster nodes.
1) Disable the automatic start-up of the default instance of the Apache Server.
After installing the Apache Server, you can configure it to automatically start at system start
up time by using the runlevel (rc) scripts in the /etc/rc.d directory. However, you must
disable the automatic start-up of this default instance in an SG/Linux environment, because
it can affect the behavior of the Serviceguard or Apache packages. For more information on
configuring the Apache Server, see the Apache Documentation that comes along with the
Apache installation.
2) Customize an Apache instance to run on a node by using the httpd.conf file. This
httpd.conf file is associated with the default Apache instance and has a Listen directive
"Listen 80", which is equivalent to listening for all IP addresses at port 80. Following is the
default location of this file:
Red Hat: /etc/httpd/conf/httpd.conf
SLES: /etc/apache2/httpd.conf
If an Apache instance needs to be configured so that it listens to specific IP Addresses, the
LISTEN directive has to be changed to "Listen <IP Address> :<Port>".
NOTE: The httpd.conf file of SLES distribution has several include directives. One of
them includes the file /etc/apache2/sysconfig.d/include.conf which does not