130 lines
10 KiB
HTML
130 lines
10 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="task" />
|
||
|
|
<meta name="DC.Title" content="Save and restore iSeries Access for Web in a Web application server environment" />
|
||
|
|
<meta name="abstract" content="The server commands SAVLICPGM and RSTLICPGM can be used to save and restore iSeries Access for Web from one server to another. Using these commands has the same effect as installing iSeries Access for Web using the install media (CD-ROM). However, the advantage of using the commands is that any iSeries Access for Web PTFs that have been applied are saved from the source server and restored to the target server." />
|
||
|
|
<meta name="description" content="The server commands SAVLICPGM and RSTLICPGM can be used to save and restore iSeries Access for Web from one server to another. Using these commands has the same effect as installing iSeries Access for Web using the install media (CD-ROM). However, the advantage of using the commands is that any iSeries Access for Web PTFs that have been applied are saved from the source server and restored to the target server." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzammwebappservenv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzammhdrchecklist.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzammhdrchecklist.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/cfgaccweb2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/wrklnk.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2003, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2003, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzammsaveandrestore" />
|
||
|
|
<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>Save and restore iSeries Access for Web in a Web application server
|
||
|
|
environment</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzammsaveandrestore"><a name="rzammsaveandrestore"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Save and restore iSeries Access for Web in a Web application server
|
||
|
|
environment</h1>
|
||
|
|
<div><p>The server commands SAVLICPGM and RSTLICPGM can be used to save
|
||
|
|
and restore iSeries™ Access
|
||
|
|
for Web from one server to another. Using these commands has the same effect
|
||
|
|
as installing iSeries Access
|
||
|
|
for Web using the install media (CD-ROM). However, the advantage of using
|
||
|
|
the commands is that any iSeries Access for Web PTFs that have been applied
|
||
|
|
are saved from the source server and restored to the target server.</p>
|
||
|
|
<div class="p"><p>If iSeries Access
|
||
|
|
for Web has been used on the source server and users have generated and saved
|
||
|
|
user data, the SAVLICPGM and RSTLICPGM process will not propagate that user
|
||
|
|
data to the target server. To propagate the user data, additional steps must
|
||
|
|
be performed. </p>
|
||
|
|
</div>
|
||
|
|
<div class="section"> <p>To start iSeries Access for Web and propagate the user data,
|
||
|
|
do the following:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li class="stepexpand"><span><strong>Complete the Plan, install, and configure checklist.</strong></span> Please note that the RSTLICPGM command does not make iSeries Access
|
||
|
|
for Web available for use on the target server. iSeries Access for Web must first be
|
||
|
|
configured and started before it can be used. To configure iSeries Access
|
||
|
|
for Web, refer to the Plan, install, and configure checklist. The checklist
|
||
|
|
contains steps to install iSeries Access for Web on the server using the install
|
||
|
|
media (CD-ROM). At the point in the checklist that installation is addressed,
|
||
|
|
you would run the SAVLICPGM and RSTLICPGM commands from the source server
|
||
|
|
to the target server. </li>
|
||
|
|
<li class="stepexpand"><span><strong>Use the CFGACCWEB2 command.</strong></span> Continue with the
|
||
|
|
checklist and run the steps to configure iSeries Access for Web on the target
|
||
|
|
server using the CFGACCWEB2 command. </li>
|
||
|
|
<li class="stepexpand"><span><strong>Run the WRKLNK command.</strong></span> After configuring iSeries Access
|
||
|
|
for Web, run the server command WRKLNK OBJ('/QIBM/UserData/Access/Web2/*')
|
||
|
|
on the target server. </li>
|
||
|
|
<li class="stepexpand" id="rzammsaveandrestore__four"><a name="rzammsaveandrestore__four"><!-- --></a><span><strong>Identify the <samp class="codeph">users</samp> path on the target
|
||
|
|
server.</strong></span> Several directories will be listed. One directory has
|
||
|
|
a name that corresponds to the Web application server type that was configured
|
||
|
|
using the CFGACCWEB2 command. That directory contains subdirectories that
|
||
|
|
identify the instance and application server of the Web application server
|
||
|
|
type that is configured. <p>Expand the directories until a directory named <samp class="codeph">'users'</samp> is
|
||
|
|
displayed. Make note of this complete directory path. User data will be copied
|
||
|
|
to this <samp class="codeph">users</samp> directory in a later step.</p>
|
||
|
|
<p>If you have
|
||
|
|
multiple Web application server types configured, you might need to locate
|
||
|
|
multiple <samp class="codeph">users</samp> directories under different directory trees.</p>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span><strong>Run the WRKLNK command.</strong></span> On the source server,
|
||
|
|
run the server command WRKLNK OBJ('/QIBM/UserData/Access/Web2/*'). </li>
|
||
|
|
<li class="stepexpand" id="rzammsaveandrestore__six"><a name="rzammsaveandrestore__six"><!-- --></a><span><strong>Identify the <samp class="codeph">users</samp> path on the source
|
||
|
|
server.</strong></span> Several directories will be listed. One directory has
|
||
|
|
a name that corresponds to the Web application server type that has been used
|
||
|
|
on the source server. That directory contains subdirectories that identify
|
||
|
|
the instance and application server of the Web application server type that
|
||
|
|
is configured. <p>Expand that directory tree until a directory named <samp class="codeph">users</samp> is
|
||
|
|
displayed. Make note of this complete directory path. This <samp class="codeph">users</samp> directory
|
||
|
|
contains the user data that is to be saved and restored to the target server. </p>
|
||
|
|
<p>If
|
||
|
|
you have multiple Web application server types configured, you might need
|
||
|
|
to locate multiple <samp class="codeph">users</samp> directories under different directory
|
||
|
|
trees.</p>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand" id="rzammsaveandrestore__seven"><a name="rzammsaveandrestore__seven"><!-- --></a><span><strong>Save and restore the <samp class="codeph">users</samp> directory.</strong></span> The <samp class="codeph">users</samp> directory on the source server should now
|
||
|
|
be saved and restored to the <samp class="codeph">users</samp> directory on the target
|
||
|
|
server. Use the save and restore mechanism you are most comfortable using. </li>
|
||
|
|
<li class="stepexpand" id="rzammsaveandrestore__eight"><a name="rzammsaveandrestore__eight"><!-- --></a><span><strong>Save and restore the <samp class="codeph">config</samp> directory.</strong></span> <img src="./delta.gif" alt="Start of change" />The directory that contains the <samp class="codeph">users</samp> directory
|
||
|
|
also contains a directory called <samp class="codeph">config</samp>. The <samp class="codeph">config</samp> directory
|
||
|
|
contains files that should also be saved and restored. If they exist, the
|
||
|
|
files to save and restore are: webaccess.policies extension.properties,
|
||
|
|
and disposition.properties.<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li class="stepexpand" id="rzammsaveandrestore__nine"><a name="rzammsaveandrestore__nine"><!-- --></a><span><strong>Run the CFGACCWEB2 command.</strong></span> Now that
|
||
|
|
all the user data files have been saved from the source server and restored
|
||
|
|
to the target server, the CFGACCWEB2 command must be run again. Running the
|
||
|
|
command again will ensure that all the user data files that were saved and
|
||
|
|
restored have the correct data and object authority settings. <p><img src="./delta.gif" alt="Start of change" />If
|
||
|
|
you have multiple Web application server types configured, you need to repeat
|
||
|
|
steps <a href="#rzammsaveandrestore__seven">7</a>, <a href="#rzammsaveandrestore__eight">8</a>,
|
||
|
|
and <a href="#rzammsaveandrestore__nine">9</a> for each pair of user directories
|
||
|
|
located in steps <a href="#rzammsaveandrestore__four">4</a> and <a href="#rzammsaveandrestore__six">6</a>. <img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span><strong>Return to the checklist.</strong></span> Return to the Plan,
|
||
|
|
install, and configure checklist and complete any remaining steps. </li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"></div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzammwebappservenv.htm" title="Learn how to configure, customize, use, and save iSeries Access for Web in a Web application server environment.">iSeries Access for Web in a Web application server environment</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzammhdrchecklist.htm" title="Use this checklist to guide you through the steps necessary to plan, install, verify, and configure a simple iSeries Access for Web environment. These steps do not take into account other Web applications or more complex Web environments.">Checklist: Plan, install, and configure</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../cl/cfgaccweb2.htm">CFGACCWEB2 CL command</a></div>
|
||
|
|
<div><a href="../cl/wrklnk.htm">WRKLNK CL command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|