Saving and restoring iSeries Access for Web in a Web application server environment

The commands SAVLICPGM and RSTLICPGM can be used to save and restore iSeries™ Access for Web from one system 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 system and restored to the target system.

If iSeries Access for Web has been used on the source system and users have generated and saved user data, the SAVLICPGM and RSTLICPGM process will not propagate that user data to the target system. To propagate the user data, additional steps must be performed.

To start iSeries Access for Web and propagate the user data, do the following:

1. Complete the Plan, install, and configure checklist. The RSTLICPGM command does not make iSeries Access for Web available for use on the target system. 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 system 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 system to the target system.

2. Use the CFGACCWEB2 command. Continue with the checklist and run the steps to configure iSeries Access for Web on the target system using the CFGACCWEB2 command.

3. Run the WRKLNK command. After configuring iSeries Access for Web, run the command WRKLNK OBJ('/QIBM/UserData/Access/Web2/*') on the target system.
4. Identify the users path on the target system. 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.

   Expand the directories until a directory named 'users' is displayed. Make note of this complete directory path. User data will be copied to this users directory in a later step.

   If you have multiple Web application server types configured, you might need to locate multiple users directories under different directory trees.

5. Run the WRKLNK command. On the source system, run the command WRKLNK OBJ('/QIBM/UserData/Access/Web2/*').
6. Identify the users path on the source system. 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 system. That directory contains subdirectories that identify the instance and application server of the Web application server type that is configured.

   Expand that directory tree until a directory named users is displayed. Make note of this complete directory path. This users directory contains the user data that is to be saved and restored to the target system.

   If you have multiple Web application server types configured, you might need to locate multiple users directories under different directory trees.

7. Save and restore the users directory. The users directory on the source system should now be saved and restored to the users directory on the target system. Use the save and restore mechanism you are most comfortable using.
8. Save and restore the config directory. The directory that contains the users directory also contains a directory called config. The config 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.
9. Run the CFGACCWEB2 command. Now that all the user data files have been saved from the source system and restored to the target system, 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.

   If you have multiple Web application server types configured, you need to repeat steps 7, 8, and 9 for each pair of user directories located in steps 4 and 6.

10. Return to the checklist. Return to the Plan, install, and configure checklist and complete any remaining steps.

Parent topic:

Related concepts
Checklist: Planning, installing, and configuring