796 lines
46 KiB
HTML
796 lines
46 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 triggered cache manager on HTTP Server (powered by Apache)" />
|
||
|
|
<meta name="abstract" content="This topic provides information about how to set up the triggered cache manager 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 the triggered cache manager for your HTTP Server with the IBM Web Administration for i5/OS interface." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiepartcm.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="rzaieconfigtcm" />
|
||
|
|
<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 triggered cache manager on HTTP Server (powered by Apache)</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaieconfigtcm"><a name="rzaieconfigtcm"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Set up triggered cache manager on HTTP Server (powered by Apache)</h1>
|
||
|
|
<div><p>This topic provides information about how to set up the triggered
|
||
|
|
cache manager 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>The triggered cache manager (TCM) may be used with the <a href="#rzaieconfigtcm_default">default configuration</a> or you may create your own <a href="#rzaieconfigtcm_custom">customized configuration</a>.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiepartcm.htm" title="This topic provides step-by-step tasks for the triggered cache manager.">Triggered cache manager tasks</a></div>
|
||
|
|
</div>
|
||
|
|
</div><div class="nested1" id="rzaieconfigtcm_default"><a name="rzaieconfigtcm_default"><!-- --></a><h2 class="topictitle2">Default configuration</h2>
|
||
|
|
<div><p>The following provides an overview of the process of configuring the <a href="rzaietriggeredcacheman.htm">triggered cache manager</a> function
|
||
|
|
with the default configuration.</p>
|
||
|
|
<p>You must write an application to send trigger messages to the triggered
|
||
|
|
cache manager server. Messages your application sends cause the server to
|
||
|
|
update, delete, or publish items in one or more cache targets (specified in
|
||
|
|
the server configuration), using data retrieved from data sources (also specified
|
||
|
|
in the server configuration). For more information on how to write a program
|
||
|
|
to send trigger messages, see <a href="rzaietrigger.htm">Trigger messages for triggered cache manager on HTTP Server (powered by Apache)</a>.
|
||
|
|
</p>
|
||
|
|
<p>Ensure that LPP 5722-DG1 Option 1 is installed on your iSeries™ system
|
||
|
|
and HTTP *ADMIN server is up and running. </p>
|
||
|
|
<ol><li>Start the <span>IBM Web Administration for i5/OS interface</span>. </li>
|
||
|
|
<li>Click the <span class="uicontrol">Advanced</span> tab.</li>
|
||
|
|
<li>Click the <strong>TCM</strong> subtab. </li>
|
||
|
|
<li>Click <strong>Create server</strong>. </li>
|
||
|
|
<li>Complete the following in the <strong>Create server</strong> form.
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th align="left" valign="top" width="21.428571428571427%" id="d0e101">Field</th>
|
||
|
|
<th align="left" valign="top" width="78.57142857142857%" id="d0e103">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td align="left" valign="top" width="21.428571428571427%" headers="d0e101 "><strong>Server Name</strong></td>
|
||
|
|
<td align="left" valign="top" width="78.57142857142857%" headers="d0e103 "><p>Enter a name that you will later use to identify
|
||
|
|
this server. For example, JKLTCMServer</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td align="left" valign="top" width="21.428571428571427%" headers="d0e101 "><strong>Autostart</strong></td>
|
||
|
|
<td align="left" valign="top" width="78.57142857142857%" headers="d0e103 "><p>Select <strong>Yes</strong>. </p>
|
||
|
|
<p>This will cause your server
|
||
|
|
to automatically startup when TCP/IP Services is started on your iSeries system.
|
||
|
|
If you do not want your server to startup automatically, select No.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td align="left" valign="top" width="21.428571428571427%" headers="d0e101 "><strong>TCP Port</strong></td>
|
||
|
|
<td align="left" valign="top" width="78.57142857142857%" headers="d0e103 "><p>Use the default value or enter a new TCP Port.</p>
|
||
|
|
<p>You
|
||
|
|
will use this port to communicate with your new server. When the server is
|
||
|
|
started it will establish a listening port on every IP interface configured
|
||
|
|
for TCP/IP Services on your iSeries system. Enter a different port number
|
||
|
|
if you do not want to use this default. Servers cannot share ports so if another
|
||
|
|
server is already configured to use the default port (7049) then you must
|
||
|
|
enter a different, unused port number for this server.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td align="left" valign="top" width="21.428571428571427%" headers="d0e101 "><strong>Options</strong></td>
|
||
|
|
<td align="left" valign="top" width="78.57142857142857%" headers="d0e103 "><p>Use the default, <strong>Create with default configuration</strong>,
|
||
|
|
or select a new option.</p>
|
||
|
|
<p>If you would rather copy the configuration of
|
||
|
|
a server you have already configured, select Create based on existing configuration
|
||
|
|
and then select that server name.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>Click <strong>Create</strong>. The message, "Server 'JKLTCMServer' has been created
|
||
|
|
with default configuration settings" will display at the bottom of your screen.
|
||
|
|
</li>
|
||
|
|
<li>In the list on the left, click Work with servers. </li>
|
||
|
|
<li>Select the server that you just created (for example, <tt>JKLTCMServer</tt>).
|
||
|
|
</li>
|
||
|
|
<li>Click <strong>Start</strong>. The message, "A request to start server 'JKLTCMServer'
|
||
|
|
has been submitted" will display at the bottom of your screen. It may take
|
||
|
|
a few minutes for the server to fully activate for the first time (click <strong>Refresh</strong> periodically
|
||
|
|
until you see the server listed as Active under the Status column). </li>
|
||
|
|
</ol>
|
||
|
|
<p>You have just created and started a triggered cache manager server that
|
||
|
|
uses the default configuration settings provided by IBM. Servers using the default configuration
|
||
|
|
settings are fully operational. IBM has established the following settings
|
||
|
|
for a default configuration: </p>
|
||
|
|
<ul><li>A host description named LOCALHOST is defined for IP address 127.0.0.1.
|
||
|
|
To view host descriptions, click <strong>Hosts</strong> in the list on the left.<p>IP
|
||
|
|
address 127.0.0.1 is the 'loopback' interface. The loopback interface is used
|
||
|
|
by many application servers to communicate with each other without using an
|
||
|
|
actual physical network. In this case, the triggered cache manage server uses
|
||
|
|
the loopback interface to communicate with a data source and potential cache
|
||
|
|
target applications that may be added to the configuration (see the section
|
||
|
|
titled <strong>Custom configuration</strong>, below, for details on how to add custom
|
||
|
|
configuration setting to the default configuration).</p>
|
||
|
|
</li>
|
||
|
|
<li>A data source description named LOCAL_HTTP is defined for a local HTTP
|
||
|
|
server. To view data source descriptions, click on <strong>Data sources</strong> in
|
||
|
|
the list on the left.<p>The local HTTP server is assumed to use the default
|
||
|
|
HTTP port (80) on the loopback interface (described previously). The triggered
|
||
|
|
cache manager server communicates with the local HTTP server over the loopback
|
||
|
|
interface to request Web pages it needs to send (or publish) to cache targets.</p>
|
||
|
|
</li>
|
||
|
|
<li>A cache target description named LOCAL_DIRECTORY is defined for the local
|
||
|
|
IFS (the iSeries Integrated File System). To view cache target descriptions,
|
||
|
|
click on <strong>Cache targets</strong> in the list on the left.<p>This description
|
||
|
|
specifies the root (/) directory by default. The triggered cache manager server
|
||
|
|
uses the local system's IFS as a cache target.</p>
|
||
|
|
</li>
|
||
|
|
<li>Two trigger handler descriptions are set, one named PUBLISH, and the other
|
||
|
|
named UPDATE_CACHE. To view trigger handler descriptions, click on <strong>Trigger
|
||
|
|
handlers</strong> in the list on the left.<p>Both descriptions are set to establish
|
||
|
|
trigger request handlers that manage the cache defined by LOCAL_DIRECTORY
|
||
|
|
using data obtained from the data source defined by LOCAL_HTTP. The trigger
|
||
|
|
request handler named UPDATE_CACHE simply updates cached items by copying
|
||
|
|
them from data source to cache target(s), whereas the trigger request handler
|
||
|
|
PUBLISH may be used to perform dependency parsing and page assembly prior
|
||
|
|
to sending updated items to cache. </p>
|
||
|
|
</li>
|
||
|
|
<li>An object dependency graph description named DEFAULT is defined for document
|
||
|
|
publishing. To view object dependency graph descriptions, click on <strong>Object
|
||
|
|
dependency graphs</strong> in the list on the left.<p>By default, the trigger request
|
||
|
|
handler PUBLISH (described previously) is set to use the object dependency
|
||
|
|
graph DEFAULT to record and query information pertaining to Web document dependency
|
||
|
|
parsing and page assembly. </p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>Your application must send trigger messages to one of the request handlers
|
||
|
|
(either UPDATE_CACHE or PUBLISH). This type of application is referred to
|
||
|
|
as an application trigger. When the server receives a trigger message from
|
||
|
|
an application trigger, it places the request in queue for the specified request
|
||
|
|
handler and returns message code 1102 (indicating that the request was accepted).
|
||
|
|
The server then continues to process the request asynchronously. </p>
|
||
|
|
<p>Servers running with a default configuration may be used in conjunction
|
||
|
|
with application triggers and a local HTTP server (using port 80) to store
|
||
|
|
dynamically produced Web pages as static files in the local file system. An
|
||
|
|
HTTP server may then be used to serve these static files rather than the dynamically
|
||
|
|
produced files, while application triggers ensure the cache of static files
|
||
|
|
are updated only when necessary.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="nested1" id="rzaieconfigtcm_custom"><a name="rzaieconfigtcm_custom"><!-- --></a><h2 class="topictitle2">Custom configuration</h2>
|
||
|
|
<div><p>The following section describes how to create customized configurations
|
||
|
|
for the <a href="rzaietriggeredcacheman.htm">triggered cache
|
||
|
|
manager function</a>. </p>
|
||
|
|
<ol><li>Follow the steps outlined in the previous section, <a href="#rzaieconfigtcm_default">Default configuration</a>, to create and start a new server. </li>
|
||
|
|
<li>Select the server that you just created (for example, JKLTCMServer). </li>
|
||
|
|
<li>Click <strong>Hosts</strong>. </li>
|
||
|
|
<li>Click <strong>Create New Description</strong> to add additional host descriptions
|
||
|
|
to the configuration. If you don't want to add additional host descriptions,
|
||
|
|
skip to step 5.<div class="note"><span class="notetitle">Note:</span> Host descriptions must be added before certain data source
|
||
|
|
types or cache target descriptions may be added (steps 6d, 8d, and 8e).</div>
|
||
|
|
<ol type="a"><li>Enter the server (or servers) host name or IP address you want this server
|
||
|
|
to use as a data source or cache target (for example, myserver.ibm.com).</li>
|
||
|
|
<li>Click <strong>Create</strong>.</li>
|
||
|
|
<li>To add more host descriptions, repeat steps 4 through 4b. </li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li>In the list on the left, click <strong>Data sources</strong>. </li>
|
||
|
|
<li>Click <strong>Create New Description</strong> to add additional data source descriptions
|
||
|
|
to the configuration. If you don't want to add additional data source descriptions,
|
||
|
|
skip to step 7.<div class="note"><span class="notetitle">Note:</span> Data source descriptions must be added before trigger
|
||
|
|
handler descriptions can be added (re: steps 10c and 10d).</div>
|
||
|
|
<ol type="a"><li>Do the following on the first <strong>Create data source description</strong> form.
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="14.14141414141414%" id="d0e280">Field</th>
|
||
|
|
<th valign="top" width="85.85858585858585%" id="d0e282">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="14.14141414141414%" headers="d0e280 "><strong>Name</strong></td>
|
||
|
|
<td valign="top" width="85.85858585858585%" headers="d0e282 "><p>Enter a name for this description. For example fields
|
||
|
|
for a file system data source, or webDS for an HTTP Server data source.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="14.14141414141414%" headers="d0e280 "><strong>Type</strong></td>
|
||
|
|
<td valign="top" width="85.85858585858585%" headers="d0e282 "><p>Select <strong>File System</strong> to define a local IFS directory
|
||
|
|
as a data source. </p>
|
||
|
|
<p>Select <strong>HTTP Server</strong> to define an HTTP server
|
||
|
|
as a data source. </p>
|
||
|
|
<p>For HTTP server data sources, the server hostname
|
||
|
|
or IP address is provided by selecting a host description on the next screen.
|
||
|
|
Host descriptions are not used when defining file system data sources.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>Click <strong>Next</strong>.</li>
|
||
|
|
<li>If <strong>File System</strong> was chosen previously, do the following on the second <strong>Create
|
||
|
|
data source description</strong> form. Otherwise, skip to the next step.
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="16.83673469387755%" id="d0e328">Field</th>
|
||
|
|
<th valign="top" width="83.16326530612244%" id="d0e330">Directory</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="16.83673469387755%" headers="d0e328 "><strong>Directory</strong></td>
|
||
|
|
<td valign="top" width="83.16326530612244%" headers="d0e330 "><p>Enter a directory name that is the data source. For
|
||
|
|
example, <tt>/tcm/files</tt></p>
|
||
|
|
<p>All files requested from this data source
|
||
|
|
will be relative to the specified directory.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="16.83673469387755%" headers="d0e328 "><strong>Threads</strong></td>
|
||
|
|
<td valign="top" width="83.16326530612244%" headers="d0e330 "><p>Use the default value or enter a new value.</p>
|
||
|
|
<p>When
|
||
|
|
started, the server will run in a multithreaded process on the iSeries system.
|
||
|
|
It will use the number of specified threads to interact with the data source.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>If <strong>HTTP Server</strong> was chosen previously, do the following on the second <strong>Create
|
||
|
|
data source description</strong> form.
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="15.151515151515152%" id="d0e367">Field</th>
|
||
|
|
<th valign="top" width="84.84848484848484%" id="d0e369">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="15.151515151515152%" headers="d0e367 "><strong>Host</strong></td>
|
||
|
|
<td valign="top" width="84.84848484848484%" headers="d0e369 "><p>Select the description that describes the HTTP server
|
||
|
|
data source hostname or IP address. </p>
|
||
|
|
<p>Host descriptions were created
|
||
|
|
in steps 4 through 4b. If there is no host description for the data source
|
||
|
|
you are describing, you must first create it by repeating steps 4 through
|
||
|
|
4b.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="15.151515151515152%" headers="d0e367 "><strong>TCP Port</strong></td>
|
||
|
|
<td valign="top" width="84.84848484848484%" headers="d0e369 "><p>Use the default value or enter a new value. </p>
|
||
|
|
<p>If
|
||
|
|
the HTTP Server data source is not using the default HTTP port, enter it here.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="15.151515151515152%" headers="d0e367 "><strong>Root Directory</strong></td>
|
||
|
|
<td valign="top" width="84.84848484848484%" headers="d0e369 "><p>Select the default, (/). </p>
|
||
|
|
<p>All URLs requested
|
||
|
|
from this data source will be relative to the specified directory (path).</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="15.151515151515152%" headers="d0e367 "><strong>Keep Alive</strong></td>
|
||
|
|
<td valign="top" width="84.84848484848484%" headers="d0e369 "><p>Select <strong>No</strong>.</p>
|
||
|
|
<p>If you know the data source
|
||
|
|
supports persistent HTTP connections, commonly referred to as 'keepalive'
|
||
|
|
support, you may want to select <strong>Yes</strong> to avoid having the server disconnect
|
||
|
|
after each read request.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="15.151515151515152%" headers="d0e367 "><strong>Timeout</strong></td>
|
||
|
|
<td valign="top" width="84.84848484848484%" headers="d0e369 "><p>Use the default value or enter a new value.</p>
|
||
|
|
<p>Zero
|
||
|
|
(0) indicates the server should wait indefinitely for responses from the data
|
||
|
|
source after requests are sent. If you would rather the server eventually
|
||
|
|
timeout rather than wait indefinitely, enter the number of seconds it should
|
||
|
|
wait before dropping connections. Just remember that an HTTP server may take
|
||
|
|
some time to respond to a request, especially if it needs to dynamically produce
|
||
|
|
the requested file. Be sure to specify a timeout value that is acceptable,
|
||
|
|
otherwise cache targets may not get updated.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="15.151515151515152%" headers="d0e367 "><strong>Threads</strong></td>
|
||
|
|
<td valign="top" width="84.84848484848484%" headers="d0e369 "><p>Use the default value or enter a new value.</p>
|
||
|
|
<p>When
|
||
|
|
started, the server will run in a multithreaded process on the iSeries system.
|
||
|
|
It will use the number of specified threads to interact with this data source.
|
||
|
|
</p>
|
||
|
|
<p>A data source thread is dedicated to fulfill one read request at a
|
||
|
|
time. When threads are waiting for a response from a data source (see Timeout
|
||
|
|
value above), it is not available to send other requests. Be sure to specify
|
||
|
|
enough threads to provide for a number of simultaneous requests acceptable
|
||
|
|
to the data source without overwhelming it.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>Click <strong>Create</strong>.</li>
|
||
|
|
<li>To add more data source descriptions, repeat steps 6 through 6e.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li>Click <strong>Cache targets</strong>.</li>
|
||
|
|
<li>Click <strong>Create New Description</strong> to add additional cache target descriptions
|
||
|
|
to the configuration. If you don't want to add additional cache target descriptions,
|
||
|
|
skip to step 9.<ol type="a"><li>Do the following on the first <strong>Create cache target description</strong> form.
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="14.646464646464647%" id="d0e463">Field</th>
|
||
|
|
<th valign="top" width="85.35353535353535%" id="d0e465">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="14.646464646464647%" headers="d0e463 "><strong>Name</strong></td>
|
||
|
|
<td valign="top" width="85.35353535353535%" headers="d0e465 "><p>Enter a name for this description. For example fileCT
|
||
|
|
for a file system cache target, or webCT for an HTTP Server cache target,
|
||
|
|
or routerCT for a router cache target. </p>
|
||
|
|
<p>This name is only used to refer
|
||
|
|
to the description you are about to create. It is not used for communication
|
||
|
|
with the cache target.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="14.646464646464647%" headers="d0e463 "><strong>Type</strong></td>
|
||
|
|
<td valign="top" width="85.35353535353535%" headers="d0e465 "><p>Select <strong>File System</strong> to define a local IFS directory
|
||
|
|
as a cache target. </p>
|
||
|
|
<p>Select <strong>HTTP Server</strong> to define an HTTP server
|
||
|
|
as a cache target. Select Router to define an IBM model 2212 or IBM model
|
||
|
|
2216 caching router as a cache target. </p>
|
||
|
|
<p>For HTTP server and router
|
||
|
|
cache targets, the server/router hostname or IP address is provided by selecting
|
||
|
|
a host description on the next screen. Host descriptions are not used when
|
||
|
|
defining file system cache targets.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>Click <strong>Next</strong>.</li>
|
||
|
|
<li>If <strong>File System</strong> was chosen previously, do the following on the second <strong>Create
|
||
|
|
cache target description</strong> form. Otherwise, skip to the next step.
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="14.14141414141414%" id="d0e513">Field</th>
|
||
|
|
<th valign="top" width="85.85858585858585%" id="d0e515">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="14.14141414141414%" headers="d0e513 "><strong>Status at Startup</strong></td>
|
||
|
|
<td valign="top" width="85.85858585858585%" headers="d0e515 "><p>Select <strong>Enabled</strong>. </p>
|
||
|
|
<p>The server creates
|
||
|
|
an internal handler for each cache target description at startup. These handlers
|
||
|
|
direct the server's interaction with cache targets. This option indicates
|
||
|
|
the initial handler state when the server is started. </p>
|
||
|
|
<p>Requests sent
|
||
|
|
to a disabled cache target handler always appear to be handled successfully
|
||
|
|
(when the handler actually does nothing). This allows you to take cache targets
|
||
|
|
off-line without having failed cache update attempts logged by your triggered
|
||
|
|
cache manager server. When cache targets go on-line again, their corresponding
|
||
|
|
handlers may be re-enabled.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="14.14141414141414%" headers="d0e513 "><strong>Directory</strong></td>
|
||
|
|
<td valign="top" width="85.85858585858585%" headers="d0e515 "><p>Enter a directory name that is the data source. For
|
||
|
|
example: <tt>/tcm/filect</tt> </p>
|
||
|
|
<p>All files requested from this cache
|
||
|
|
target will be relative to the specified directory. </p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="14.14141414141414%" headers="d0e513 "><strong>Threads</strong></td>
|
||
|
|
<td valign="top" width="85.85858585858585%" headers="d0e515 "><p>Use the default value or enter a new value.</p>
|
||
|
|
<p>When
|
||
|
|
started, the server will run in a multithreaded process on the iSeries system.
|
||
|
|
It will use the number of specified threads to interact with this cache target.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>If <strong>HTTP Server</strong> was chosen previously, do the following on the second <strong>Create
|
||
|
|
cache target description</strong> form. Otherwise, skip to the next step.
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="13.636363636363635%" id="d0e567">Field</th>
|
||
|
|
<th valign="top" width="86.36363636363636%" id="d0e569">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="13.636363636363635%" headers="d0e567 "><strong>Status at Startup</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e569 "><p>Select <strong>Enabled</strong>.</p>
|
||
|
|
<p>The server creates an
|
||
|
|
internal handler for each cache target description at startup. These handlers
|
||
|
|
direct the server's interaction with cache targets. This option indicates
|
||
|
|
the initial handler state when the server is started. </p>
|
||
|
|
<p>Requests sent
|
||
|
|
to a disabled cache target handler always appear to be handled successfully
|
||
|
|
(when the handler actually does nothing). This allows you to take cache targets
|
||
|
|
off-line without having failed cache update attempts logged by your triggered
|
||
|
|
cache manager server. When cache targets go on-line again, their corresponding
|
||
|
|
handlers may be re-enabled.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.636363636363635%" headers="d0e567 "><strong>Host</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e569 "><p>Select the description that describes the HTTP cache
|
||
|
|
target source hostname or IP address. </p>
|
||
|
|
<p>Host descriptions were created
|
||
|
|
in steps 4 through 4b. If there is no host description for the cache target
|
||
|
|
you are describing, you must first create it by repeating steps 4 through
|
||
|
|
4b.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.636363636363635%" headers="d0e567 "><strong>TCP Port</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e569 "><p>Use the default value or select a new value.</p>
|
||
|
|
<p>If
|
||
|
|
the HTTP server cache target is not using the default HTTP port, enter it
|
||
|
|
here.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.636363636363635%" headers="d0e567 "><strong>Root Directory</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e569 "><p>Use the default, (/). </p>
|
||
|
|
<p>All URLs posted to
|
||
|
|
this cache target will be relative to the specified directory (path).</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.636363636363635%" headers="d0e567 "><strong>Keep Alive</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e569 "><p>Select <strong>No</strong>. </p>
|
||
|
|
<p>If you know the cache target
|
||
|
|
supports persistent HTTP connections, commonly referred to as 'keepalive'
|
||
|
|
support, you may want to select <strong>Yes</strong> to avoid having the server disconnect
|
||
|
|
after each post request.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.636363636363635%" headers="d0e567 "><strong>Timeout</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e569 "><p>Use the default value or enter a new value.</p>
|
||
|
|
<p>Zero
|
||
|
|
(0) indicates the server should wait indefinitely for responses from the cache
|
||
|
|
target after requests are sent. If you would rather the server eventually
|
||
|
|
timeout rather than wait indefinitely, enter the number of seconds it should
|
||
|
|
wait before dropping connections. Just remember that an HTTP server may take
|
||
|
|
some time to respond to a request, especially if it needs to dynamically produce
|
||
|
|
the requested file. Be sure to specify a timeout value that is acceptable,
|
||
|
|
otherwise you cannot determine if the cache target received the request.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.636363636363635%" headers="d0e567 "><strong>Threads</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e569 "><p>Use the default value or enter a new value. </p>
|
||
|
|
<p>When
|
||
|
|
started, the server will run in a multithreaded process on the iSeries system.
|
||
|
|
It will use the number of specified threads to interact with this cache target.
|
||
|
|
</p>
|
||
|
|
<p>A cache target thread is dedicated to fulfill one post request at
|
||
|
|
a time. When threads are waiting for a response from a cache target (see <strong>Timeout</strong> value
|
||
|
|
above), it is not available to send other requests. Be sure to specify enough
|
||
|
|
threads to provide for a number of simultaneous requests acceptable to the
|
||
|
|
cache target without overwhelming it.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>If <strong>Router</strong> was chosen previously, do the following on the second <strong>Create
|
||
|
|
cache target description</strong> form.
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="13.636363636363635%" id="d0e665">Field</th>
|
||
|
|
<th valign="top" width="86.36363636363636%" id="d0e667">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="13.636363636363635%" headers="d0e665 "><strong>Status at Startup</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e667 "><p>Select <strong>Enabled</strong>. </p>
|
||
|
|
<p>The server creates
|
||
|
|
an internal handler for each cache target description at startup. These handlers
|
||
|
|
direct the server's interaction with cache targets. This option indicates
|
||
|
|
the initial handler state when the server is started. </p>
|
||
|
|
<p>Requests sent
|
||
|
|
to a disabled cache target handler always appear to be handled successfully
|
||
|
|
(when the handler actually does nothing). This allows you to take cache targets
|
||
|
|
off-line without having failed cache update attempts logged by your triggered
|
||
|
|
cache manager server. When cache targets go on-line again, their corresponding
|
||
|
|
handlers may be re-enabled.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.636363636363635%" headers="d0e665 "><strong>Host</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e667 "><p>Select the description that describes the hostname
|
||
|
|
or IP address of the router hosting the web document cache target. </p>
|
||
|
|
<p>Host
|
||
|
|
descriptions were created in steps 4 through 4b. If there is no host description
|
||
|
|
for the cache target you are describing, you must first create it by repeating
|
||
|
|
steps 4 through 4b.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.636363636363635%" headers="d0e665 "><strong>TCP Port</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e667 "><p>Use the default value or enter a new value. </p>
|
||
|
|
<p>If
|
||
|
|
the router is not using the default port, enter it here.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.636363636363635%" headers="d0e665 "><strong>Cluster ID</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e667 "><p>Enter the fully qualified host name or IP address
|
||
|
|
of the web server cluster for which the router is caching documents. </p>
|
||
|
|
<p>This
|
||
|
|
name applies to the name of the web document cache, not the router that is
|
||
|
|
hosting the cache. The router, specified by the Host field, may contain multiple
|
||
|
|
caches for different web server clusters. Use this field to specify which
|
||
|
|
web document cache you want to manage.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.636363636363635%" headers="d0e665 "><strong>Cluster TCP Port</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e667 "><p>Enter the TCP port number associated with the cluster
|
||
|
|
ID specified above. </p>
|
||
|
|
<p>The server combines the cluster ID and the cluster
|
||
|
|
TCP port to uniquely identify a cache target hosted by the router.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.636363636363635%" headers="d0e665 "><strong>Root Directory</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e667 "><p>Use the default, (/). </p>
|
||
|
|
<p>All URLs posted to
|
||
|
|
this cache target will be relative to the specified directory (path).</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.636363636363635%" headers="d0e665 "><strong>Keep Alive</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e667 "><p>Select <strong>No</strong>. </p>
|
||
|
|
<p>If you know the cache target
|
||
|
|
supports persistent HTTP connections, commonly referred to as 'keepalive'
|
||
|
|
support, you may want to select <strong>Yes</strong> to avoid having the server disconnect
|
||
|
|
after each post request.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.636363636363635%" headers="d0e665 "><strong>Threads</strong></td>
|
||
|
|
<td valign="top" width="86.36363636363636%" headers="d0e667 "><p>Use the default, 5. </p>
|
||
|
|
<p>When started, the server
|
||
|
|
will run in a multithreaded process on the iSeries system. It will use the
|
||
|
|
number of specified threads to interact with this cache target. </p>
|
||
|
|
<p>A
|
||
|
|
cache target thread is dedicated to fulfill one post request at a time. When
|
||
|
|
threads are waiting for a response from a cache target it is not available
|
||
|
|
to send other requests. Be sure to specify enough threads to provide for a
|
||
|
|
number of simultaneous requests acceptable to the cache target without overwhelming
|
||
|
|
it.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>Click <strong>Create</strong>.</li>
|
||
|
|
<li>To add more cache target descriptions, repeat steps 8 through 8f.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li>Click <strong>Trigger handlers</strong>.</li>
|
||
|
|
<li>Click <strong>Create New Description</strong> to add additional trigger handler
|
||
|
|
descriptions to the configuration. If you don't want to add additional trigger
|
||
|
|
handler descriptions, skip to step 11.<ol type="a"><li>Do the following on the first <strong>Create trigger handler description</strong> form.
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="13.131313131313133%" id="d0e784">Field</th>
|
||
|
|
<th valign="top" width="86.86868686868688%" id="d0e786">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="13.131313131313133%" headers="d0e784 "><strong>Name</strong></td>
|
||
|
|
<td valign="top" width="86.86868686868688%" headers="d0e786 "><p>Enter a name for this description. For example <tt>simpleDocUpdate</tt> for
|
||
|
|
an update cache trigger handler, or <tt>docPublisher</tt> for a publish trigger
|
||
|
|
handler. </p>
|
||
|
|
<p>The name you choose is used by your application triggers
|
||
|
|
when sending messages to the server. All trigger messages sent to the server
|
||
|
|
must contain the name of the trigger handler that is to process the request.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.131313131313133%" headers="d0e784 "><strong>Type</strong></td>
|
||
|
|
<td valign="top" width="86.86868686868688%" headers="d0e786 "><p>Select <strong>Update Cache</strong> to define a trigger handler
|
||
|
|
that does simple cache updates. </p>
|
||
|
|
<p>Select <strong>Publish</strong> to define a trigger
|
||
|
|
handler that does document publishing. </p>
|
||
|
|
<p>Update Cache trigger handlers
|
||
|
|
perform simple data transfers. They retrieve objects from a data source and
|
||
|
|
copy them to cache targets. </p>
|
||
|
|
<p>Publish trigger handlers may use object
|
||
|
|
dependency graphs and rule sets to perform dependency parsing and page assembly
|
||
|
|
(prior to doing cache updates). You may use the DEFAULT object dependency
|
||
|
|
graph description included in the default configuration, or you may create
|
||
|
|
and use a new one specifically for your handlers. </p>
|
||
|
|
<p>For more information,
|
||
|
|
click on <strong>Publishing rules</strong> and <strong>Rule set</strong> in the list on the left,
|
||
|
|
then click on the help icon in the top-right corner of these pages. If you
|
||
|
|
decide to create your own publishing rules and rule set(s) you may do so,
|
||
|
|
and then return to step 9 to add publish trigger handler descriptions to reference
|
||
|
|
your new rule set(s).</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>Click <strong>Next</strong>.</li>
|
||
|
|
<li>If <strong>Update Cache</strong> was chosen previously, do the following on the
|
||
|
|
second <strong>Create trigger handler description</strong> form. Otherwise, skip to
|
||
|
|
the next step.
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="12.626262626262626%" id="d0e850">Field</th>
|
||
|
|
<th valign="top" width="87.37373737373737%" id="d0e852">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="12.626262626262626%" headers="d0e850 "><strong>Data Source</strong></td>
|
||
|
|
<td valign="top" width="87.37373737373737%" headers="d0e852 "><p>Select the description that describes the data source
|
||
|
|
for this trigger handler. </p>
|
||
|
|
<p>Trigger handlers go to one, and only one,
|
||
|
|
data source to retrieve information. The same data source, however, may be
|
||
|
|
used by more than one trigger handler. Data source descriptions were created
|
||
|
|
in steps 6 through 6f. If there is no description for the data source you
|
||
|
|
want your handler to use, you must first create it by repeating steps 6 through
|
||
|
|
6f.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="12.626262626262626%" headers="d0e850 "><strong>Cache Targets</strong></td>
|
||
|
|
<td valign="top" width="87.37373737373737%" headers="d0e852 "><p>Select the descriptions that describe the cache targets
|
||
|
|
for this trigger handler, or select no descriptions to create a trigger handler
|
||
|
|
that retrieves data but does not sent it to cache. </p>
|
||
|
|
<p>Trigger handlers
|
||
|
|
can manage data for multiple cache targets. Moreover, the same cache target
|
||
|
|
can be managed by more than one trigger handler. Cache target descriptions
|
||
|
|
were created in steps 8 through 8g. If there is no descriptions for the cache
|
||
|
|
targets you want your handler to manage, you may first create them by repeating
|
||
|
|
steps 8 through 8g, or continue on to create this description and then come
|
||
|
|
back to include them later.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="12.626262626262626%" headers="d0e850 "><strong>Trigger Queue Collapse Policy</strong></td>
|
||
|
|
<td valign="top" width="87.37373737373737%" headers="d0e852 "><p>Use the default value. </p>
|
||
|
|
<p>Trigger messages sent
|
||
|
|
from application triggers to a server are always placed on a particular trigger
|
||
|
|
handler's request queue. The handler then processes the requests asynchronously
|
||
|
|
according to the queuing policy specified within the message. It is possible
|
||
|
|
for identical trigger messages to be in queue, either due to the queuing policy
|
||
|
|
or due to the server being overwhelmed by requests. This setting defines how
|
||
|
|
identical triggers in queue are to be handled.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="12.626262626262626%" headers="d0e850 "><strong>Cache Request Queue Priority</strong></td>
|
||
|
|
<td valign="top" width="87.37373737373737%" headers="d0e852 "><p>Use the default value. </p>
|
||
|
|
<p>The same cache target
|
||
|
|
can be managed by more than one trigger handler. Cache update requests from
|
||
|
|
trigger handlers are queued and processed according to priority. This setting
|
||
|
|
defines the priority this handler is to specify when placing cache update
|
||
|
|
requests. The lower the number, the higher the priority. The default is the
|
||
|
|
lowest priority. Enter a lower number if you want this handler to have a higher
|
||
|
|
priority.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="12.626262626262626%" headers="d0e850 "><strong>Threads</strong></td>
|
||
|
|
<td valign="top" width="87.37373737373737%" headers="d0e852 "><p>Use the default value or enter a new value.</p>
|
||
|
|
<p>When
|
||
|
|
started, the server will run in a multithreaded process on the iSeries system.
|
||
|
|
It will use the number of specified threads to process requests sent to this
|
||
|
|
trigger handler.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="12.626262626262626%" headers="d0e850 "><strong>Success/ Failures</strong></td>
|
||
|
|
<td valign="top" width="87.37373737373737%" headers="d0e852 "><p>Use the default value. </p>
|
||
|
|
<p>Trigger handlers can
|
||
|
|
post success or failure messages to acknowledgment targets after requests
|
||
|
|
are handled. This setting allows you to specify the two acknowledgment target
|
||
|
|
lists this handler uses. One list is used to send success messages; the other
|
||
|
|
is used to send failure messages. </p>
|
||
|
|
<p>Default configuration settings do
|
||
|
|
not include acknowledgment target descriptions. If you want your trigger handler
|
||
|
|
to post completion messages, you must first write an application that listens
|
||
|
|
for such messages (using HTTP POST method). You can then add an acknowledgment
|
||
|
|
target description to this server's configuration and reference it here.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>If <strong>Publish</strong> was chosen previously, do the following on the second <strong>Create
|
||
|
|
trigger handler description</strong> form.
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="12.307692307692308%" id="d0e925">Field</th>
|
||
|
|
<th valign="top" width="87.6923076923077%" id="d0e927">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="12.307692307692308%" headers="d0e925 "><strong>Data Source</strong></td>
|
||
|
|
<td valign="top" width="87.6923076923077%" headers="d0e927 "><p>Select the description that describes the data source
|
||
|
|
for this trigger handler. </p>
|
||
|
|
<p>Trigger handlers go to one, and only one,
|
||
|
|
data source to retrieve information. The same data source, however, may be
|
||
|
|
used by more than one trigger handler. Data source descriptions were created
|
||
|
|
in steps 6 through 6f. If there is no description for the data source you
|
||
|
|
want your handler to use, you must first create it by repeating steps 6 through
|
||
|
|
6f.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="12.307692307692308%" headers="d0e925 "><strong>Cache Targets</strong></td>
|
||
|
|
<td valign="top" width="87.6923076923077%" headers="d0e927 "><p>Select the descriptions that describe the cache targets
|
||
|
|
for this trigger handler, or select no descriptions to create a trigger handler
|
||
|
|
that retrieves data but does not sent it to cache. </p>
|
||
|
|
<p>Trigger handlers
|
||
|
|
can manage data for multiple cache targets. Moreover, the same cache target
|
||
|
|
can be managed by more than one trigger handler. Cache target descriptions
|
||
|
|
were created in steps 8 through 8g. If there is no descriptions for the cache
|
||
|
|
targets you want your handler to manage, you may first create them by repeating
|
||
|
|
steps 8 through 8g, or continue on to create this description and then come
|
||
|
|
back to include them later.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="12.307692307692308%" headers="d0e925 "><strong>Default Include Object</strong></td>
|
||
|
|
<td valign="top" width="87.6923076923077%" headers="d0e927 "><p>Use the default value. </p>
|
||
|
|
<p>All document component
|
||
|
|
must be triggered before they can be processed by a publish trigger handler.
|
||
|
|
This setting defines an object (by name) that is included during page assembly
|
||
|
|
when neither the source object nor the specified default object in a %fragment
|
||
|
|
tag has been triggered. The default value, none, indicates that such a global
|
||
|
|
default include object is not specified for this handler.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="12.307692307692308%" headers="d0e925 "><strong>Object Dependency Graph</strong></td>
|
||
|
|
<td valign="top" width="87.6923076923077%" headers="d0e927 "><p>Select the DEFAULT description. </p>
|
||
|
|
<p>Publish trigger
|
||
|
|
handlers only use one object dependency graph to record and query object dependency
|
||
|
|
information. The same graph, however, may be used by more than one publish
|
||
|
|
trigger handler.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="12.307692307692308%" headers="d0e925 "><strong>Edge Type to Traverse</strong></td>
|
||
|
|
<td valign="top" width="87.6923076923077%" headers="d0e927 "><p>Use the default value. </p>
|
||
|
|
<p>When publish trigger
|
||
|
|
handlers query an object dependency graph to determine dependency relationships
|
||
|
|
between document components, they traverse a particular edge type (by name).
|
||
|
|
Other edge types, perhaps added by other handlers, are ignored. This setting
|
||
|
|
defines the name of the edge type this handler is to build and traverse. If
|
||
|
|
not specified (the default) a system supplied edge type is used.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="12.307692307692308%" headers="d0e925 "><strong>Rule Set</strong></td>
|
||
|
|
<td valign="top" width="87.6923076923077%" headers="d0e927 "><p>Use the default value. </p>
|
||
|
|
<p>Publish trigger handlers
|
||
|
|
abide by a set of publishing rules when publishing documents. The same rule
|
||
|
|
set, however, may be used by more than one publish trigger handler. If not
|
||
|
|
specified (the default) the default publishing rule is used for all components.
|
||
|
|
</p>
|
||
|
|
<p>For more information, click on <strong>Publishing rules</strong> and <strong>Rule
|
||
|
|
set</strong> in the list on the left (after creating this trigger handler description),
|
||
|
|
then click on the help icon in the top-right corner of these pages. If you
|
||
|
|
decide to create your own publishing rules and rule sets you may then change
|
||
|
|
this trigger handler description to reference your new rule sets.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="12.307692307692308%" headers="d0e925 "><strong>Threads</strong></td>
|
||
|
|
<td valign="top" width="87.6923076923077%" headers="d0e927 "><p>Use the default value.</p>
|
||
|
|
<p>When started, the server
|
||
|
|
will run in a multithreaded process on the iSeries system. It will use the
|
||
|
|
number of specified threads to process requests sent to this trigger handler.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="12.307692307692308%" headers="d0e925 "><strong>Success/ Failures</strong></td>
|
||
|
|
<td valign="top" width="87.6923076923077%" headers="d0e927 "><p>Use the default value. </p>
|
||
|
|
<p>Trigger handlers can
|
||
|
|
post success or failure messages to acknowledgment targets after requests
|
||
|
|
are handled. This setting allows you to specify the two acknowledgment target
|
||
|
|
lists this handler uses. One list is used to send success messages; the other
|
||
|
|
is used to send failure messages. </p>
|
||
|
|
<p>Default configuration settings do
|
||
|
|
not include acknowledgment target descriptions. If you want your trigger handler
|
||
|
|
to post completion messages, you must first write an application that listens
|
||
|
|
for such messages (using HTTP POST method). You can then add an acknowledgment
|
||
|
|
target description to this server's configuration and reference it here. </p>
|
||
|
|
<p>The <strong>Include
|
||
|
|
object dependency information in acknowledgments</strong> option may be used.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>Click <strong>Create</strong>. </li>
|
||
|
|
<li>To add more trigger handler descriptions, repeat steps 10 through 10e. </li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li>Click <strong>Work with servers</strong>. </li>
|
||
|
|
<li>Select the server that you just customized. For example: JKLTCMServer.
|
||
|
|
</li>
|
||
|
|
<li>If your server is listed as "Active" under the Status column, click Stop.
|
||
|
|
Otherwise skip to step 15. The message, "A request to end server 'JKLTCMServer'
|
||
|
|
has been submitted" will display at the bottom of your screen. It may take
|
||
|
|
a few moments for the server end (click <strong>Refresh</strong> periodically until
|
||
|
|
you see the server listed as "Not Active"). </li>
|
||
|
|
<li>Select the server that you just customized. For example: JKLTCMServer.
|
||
|
|
</li>
|
||
|
|
<li>Click <strong>Start</strong>. </li>
|
||
|
|
<li>The message, "A request to start server 'JKLTCMServer' has been submitted"
|
||
|
|
will display at the bottom of your screen. It may take a few minutes for the
|
||
|
|
server to fully activate for the first time (click <strong>Refresh</strong> periodically
|
||
|
|
until you see the server listed as "Active" under the Status column).</li>
|
||
|
|
</ol>
|
||
|
|
<p>You have just created, configured, and started a triggered cache manager
|
||
|
|
server using a custom configuration. Your application triggers may now send
|
||
|
|
trigger messages to the active server to request that documents be updated,
|
||
|
|
deleted, or published to the cache targets specified in the configuration.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|