150 lines
11 KiB
HTML
150 lines
11 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="topic" />
|
||
|
|
<meta name="DC.Title" content="Set up and administration of a highly available Web server cluster on HTTP Server (powered by Apache)" />
|
||
|
|
<meta name="abstract" content="This topic provides information about how to set up and administer highly available Web server clusters for your HTTP Server with the IBM Web Administration for i5/OS interface." />
|
||
|
|
<meta name="description" content="This topic provides information about how to set up and administer highly available Web server clusters for your HTTP Server with the IBM Web Administration for i5/OS interface." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaieparhttp.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2002,2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2002,2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaieconfigha" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Set up and administration of a highly available Web server cluster
|
||
|
|
on HTTP Server (powered by Apache)</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaieconfigha"><a name="rzaieconfigha"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Set up and administration of a highly available Web server cluster
|
||
|
|
on HTTP Server (powered by Apache)</h1>
|
||
|
|
<div><p>This topic provides information about how to set up and administer
|
||
|
|
highly available Web server clusters for your HTTP Server with the <span>IBM<sup>®</sup> Web Administration for i5/OS™ interface</span>.</p>
|
||
|
|
<div class="important"><span class="importanttitle">Important:</span> Information
|
||
|
|
for this topic supports the latest PTF levels for HTTP Server for i5/OS .
|
||
|
|
It is recommended that you install the latest PTFs to upgrade to the latest
|
||
|
|
level of the HTTP Server for i5/OS. Some of the topics documented here are
|
||
|
|
not available prior to this update. See <a href="http://www-03.ibm.com/servers/eserver/iseries/software/http/services/service.html" target="_blank">http://www.ibm.com/servers/eserver/iseries/software/http/services/service.htm</a> <img src="www.gif" alt="Link outside Information Center" /> for more information. </div>
|
||
|
|
<p>All required programs (HTTP Server, WebSphere<sup>®</sup>, Servlets, Net.Data<sup>®</sup>,
|
||
|
|
and Clustering support) must already be installed on all nodes. See <a href="http://www.iseries.ibm.com/ha" target="_blank">http://www.iseries.ibm.com/ha</a> <img src="www.gif" alt="Link outside Information Center" /> and <a href="rzaiehighavailability.htm">Highly available Web server cluster on HTTP Server</a> for more information. </p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Step 1 - Configure the iSeries™ Cluster for highly available
|
||
|
|
HTTP Server (powered by Apache)</h4><p>For each node, configure your cluster
|
||
|
|
using the IBM Simple
|
||
|
|
Cluster Management interface available through <a href="../rzahg/rzahginav.htm">iSeries
|
||
|
|
Navigator</a> or use the cluster CL commands. See <a href="rzaiesetha_cl.htm">Set up a cluster using clustering CL commands for HTTP Server</a> and <a href="../rzaig/rzaigicclust.htm">Clusters</a> for more information.</p>
|
||
|
|
<ol><li>Start the node.<p>Use the Cluster CL commands found in <a href="rzaiesetha_cl.htm">Set up a cluster using clustering CL commands for HTTP Server</a> or use the IBM Simple Cluster Management interface available
|
||
|
|
through <a href="../rzahg/rzahginav.htm">iSeries
|
||
|
|
Navigator</a>.</p>
|
||
|
|
</li>
|
||
|
|
<li>Continue to step 2.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Step 2 - Configure the highly available Web server</h4><p><strong>Configure
|
||
|
|
IP addresses.</strong></p>
|
||
|
|
<p>For each iSeries node in the cluster that a highly
|
||
|
|
available Web server will be running on, configure the IP address that the
|
||
|
|
Web server will be using. This can be done using the <tt><strong>CFGTCP</strong></tt> CL
|
||
|
|
command. You should configure one IP address for each unique Web server. Each
|
||
|
|
Web server is configured to a dedicated TCP/IP line interface. When using
|
||
|
|
the Network Dispatcher model or comparable IP director with either HAModel
|
||
|
|
IPTakeoverWithDispatcher of PurePeer model, the IP Line interface should be
|
||
|
|
typed <tt><strong>*VIRTUALIP</strong></tt>. See <a href="../rzahg/rzahgictcp2.htm" target="_blank">TCP/IP</a> for more information.</p>
|
||
|
|
<ol><li>Start the <span>IBM Web Administration for i5/OS interface</span>.</li>
|
||
|
|
<li>Click the <strong>Manage</strong> tab.</li>
|
||
|
|
<li>Click the <span class="uicontrol">HTTP Servers</span> subtab.</li>
|
||
|
|
<li>Select your HTTP Server (powered by Apache) from the <strong>Server</strong> list.</li>
|
||
|
|
<li>Select the <a href="rzaiecontext.htm">context</a> you
|
||
|
|
want to work with from the <strong>Server area</strong> list.</li>
|
||
|
|
<li>Expand <strong>Server Properties</strong>.</li>
|
||
|
|
<li>Click <strong>General Server Configuration</strong>.</li>
|
||
|
|
<li>Click the <strong>General Settings</strong> tab in the form.</li>
|
||
|
|
<li>Click <strong>Add</strong> under the <strong>Server IP addresses and ports to listen</strong> on
|
||
|
|
table.<div class="note"><span class="notetitle">Note:</span> Directive <a href="rzaiemod_core.htm#HotBackup">HotBackup</a> will be set to <em>off</em> and
|
||
|
|
ignored if currently configured for your HTTP Server (powered by Apache).</div>
|
||
|
|
<div class="p">You
|
||
|
|
may want to perform the next steps on one iSeries and copy (for example using
|
||
|
|
FTP or NetServer™)
|
||
|
|
the HTTP Server (powered by Apache) configuration and instance files to each
|
||
|
|
iSeries server where the highly available HTTP Server will be running in the
|
||
|
|
cluster. The files that must be copied are:<ul><li>/www/server_name/conf/server_name.conf </li>
|
||
|
|
<li>/QSYS.LIB/QUSRSYS.LIB/QATMINSTC.FILE/instance_name.MBR </li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>Add the IP address the highly available Web server will be running on.</li>
|
||
|
|
<li>Click <strong>OK</strong>.</li>
|
||
|
|
</ol>
|
||
|
|
<p><strong>Configure highly available HTTP Server (powered by Apache)</strong></p>
|
||
|
|
<ol><li>Start the <span>IBM Web Administration for i5/OS interface</span>.</li>
|
||
|
|
<li>Click the <strong>Manage</strong> tab.</li>
|
||
|
|
<li>Click the <span class="uicontrol">HTTP Servers</span> subtab.</li>
|
||
|
|
<li>Select your HTTP Server (powered by Apache) from the <strong>Server</strong> list.</li>
|
||
|
|
<li>Select the <a href="rzaiecontext.htm">context</a> you
|
||
|
|
want to work with from the <strong>Server area</strong> list.</li>
|
||
|
|
<li>Expand <strong>Server Properties</strong>.</li>
|
||
|
|
<li>Click <strong>System Resources</strong>.</li>
|
||
|
|
<li>Click the <strong>Highly Available Server</strong> tab in the form.</li>
|
||
|
|
<li>Specify one specific server IP address to listen on.</li>
|
||
|
|
<li>Click <strong>Enable HTTP server</strong> to be highly available.</li>
|
||
|
|
<li>Select a highly available model.<div class="note"><span class="notetitle">Note:</span> If you are implementing the primary/backup
|
||
|
|
with network dispatcher model or the peer model, configure the network dispatcher
|
||
|
|
according to the existing cluster nodes and the configured Web server.</div>
|
||
|
|
</li>
|
||
|
|
<li><strong>Optional</strong>: Click<strong> Enable highly available CGI program</strong>.</li>
|
||
|
|
<li>Enter your liveness monitor settings. The <a href="rzaiemod_ha.htm#lmurlcheck">LMUrlCheck</a> directive is required. The other
|
||
|
|
LM directives have defaults.</li>
|
||
|
|
<li>Click <strong>OK</strong>.</li>
|
||
|
|
<li>Continue to step 3.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Step 3 - Start highly available HTTP Server (powered by Apache)</h4><p>Start
|
||
|
|
your highly available HTTP Server (powered by Apache).</p>
|
||
|
|
<ol><li>Start a 5250 session on the iSeries you are going to use the highly available
|
||
|
|
HTTP Server (powered by Apache).</li>
|
||
|
|
<li>Use <strong><tt>STRTCPSVR</tt></strong> CL command on the appropriate node.</li>
|
||
|
|
<li>Continue to step 4.</li>
|
||
|
|
</ol>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> In the case of the primary/backup model, the first highly available
|
||
|
|
server to be started will automatically assume the role of the primary. The
|
||
|
|
second highly available server to be started will automatically assume the
|
||
|
|
role of the backup.</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Step 4 - Manage your highly available HTTP Server (powered
|
||
|
|
by Apache)</h4><p>Use the <strong><tt>ENDTCPSVR</tt></strong> CL command on the appropriate
|
||
|
|
node or use the IBM Simple Cluster Management interface available through <a href="../rzahg/rzahginav.htm">iSeries Navigator</a> to stop
|
||
|
|
or end your highly available HTTP Server (powered by Apache). In the case
|
||
|
|
of primary/backup model depending on which server you are ending this may
|
||
|
|
or may not force a fail over. Ending the primary server with a backup server
|
||
|
|
running will force a fail over from primary to backup to occur. Ending the
|
||
|
|
backup will only affect the backup server. Ending the primary server with
|
||
|
|
no backup will end the primary server. In the case of PurePeer model only
|
||
|
|
the server you are ending will be affected as any other peer servers will
|
||
|
|
continue to process client requests. See <a href="rzaiesetha_cl.htm">Set up a cluster using clustering CL commands for HTTP Server</a> and <a href="../rzaig/rzaigicclust.htm">Clusters</a> for
|
||
|
|
more information.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> In the case of primary/backup model, it is possible
|
||
|
|
to determine which highly available Web server is the primary or backup server.
|
||
|
|
The QBATCH subsystem will have a job running named <strong><tt>QZHBEXPG</tt></strong> on
|
||
|
|
the primary node only. For the client data it is suggested that you set up
|
||
|
|
a method to automatically publish static files to each Web server. Static
|
||
|
|
files include HTML and highly available CGI programs.</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaieparhttp.htm" title="This topic provides step-by-step tasks for HTTP Server.">HTTP Server tasks</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|