66 lines
4.5 KiB
HTML
66 lines
4.5 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="Overview of High Availability CGI" />
|
||
<meta name="abstract" content="High availability CGI programs use APIs to preserve the CGI’s state between successive client requests. A High availability CGI program stores its state data on the Web server and can retrieve its state even after a failure or switchover of the HTTP Server or system." />
|
||
<meta name="description" content="High availability CGI programs use APIs to preserve the CGI’s state between successive client requests. A High availability CGI program stores its state data on the Web server and can retrieve its state even after a failure or switchover of the HTTP Server or system." />
|
||
<meta name="DC.Relation" scheme="URI" content="rzaieparcgi.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="rzag3ch4ovrvwhghavailcgi" />
|
||
<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>Overview of High Availability CGI</title>
|
||
</head>
|
||
<body id="rzag3ch4ovrvwhghavailcgi"><a name="rzag3ch4ovrvwhghavailcgi"><!-- --></a>
|
||
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
<h1 class="topictitle1">Overview of High Availability CGI</h1>
|
||
<div><p>High availability CGI programs use APIs to preserve the CGI’s state
|
||
between successive client requests. A High availability CGI program stores
|
||
its state data on the Web server and can retrieve its state even after a failure
|
||
or switchover of the HTTP Server or system.</p>
|
||
<p>Although maintaining a CGI program’s state across multiple requests is
|
||
a concept used by both Persistent CGI and High availability CGI programs,
|
||
the mechanisms used by the two types of programs are significantly different
|
||
and a High Availability CGI program should not be confused with a Persistent
|
||
CGI program.</p>
|
||
<p>During the configuration of a Web server, the server administrator indicates
|
||
whether CGI programs are allowed to be cluster-enabled High Availability CGI
|
||
programs. If the server receives a request for a CGI program that is allowed
|
||
to be Highly Available (HA), the Web server passes to the CGI an environment
|
||
variable that indicates the CGI may be cluster-enabled. The server also creates
|
||
and passes a unique session handle to the CGI. The CGI program must then acknowledge
|
||
that it is a cluster-enabled HA CGI program to the server, otherwise the server
|
||
will regard the CGI as not being cluster-enabled.</p>
|
||
<p>The Web server associates a HA CGI program’s state with the unique session
|
||
handle that was passed as an environment variable to the CGI. If a request
|
||
to run the CGI is sent to the Web server, and the requested URL includes the
|
||
specific session handle, the Web server will be able to correctly restore
|
||
the previous state of the CGI. For this reason it is important that the session
|
||
handle appear in all URLs that were generated by the HA CGI program to be
|
||
returned to the client.</p>
|
||
<p>An HA CGI program will use two APIs to maintain its state. To store state
|
||
information on the Web server, the CGI calls the API QzhbCgiSendState. To
|
||
receive its previous state from the Web server, the CGI should call the API
|
||
QzhbCgiRecvState.</p>
|
||
</div>
|
||
<div>
|
||
<div class="familylinks">
|
||
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaieparcgi.htm" title="This topic provides information about Common Gateway Interfaces (CGI).">Common Gateway Interface</a></div>
|
||
</div>
|
||
</div>
|
||
</body>
|
||
</html> |