The commands SAVLICPGM and RSTLICPGM can be used to save
and restore IBM i
Access for Web from
one system to another. Using these commands has the same effect as
installing IBM i
Access for Web using
the install media (CD-ROM). However, the advantage of using the commands
is that any IBM i
Access for Web PTFs
that have been applied are saved from the source system and restored
to the target system.
If IBM i
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 IBM i
Access for Web and
propagate the user data, do the following:
- Complete the Planning, installing, and configuring checklist.
The RSTLICPGM command does not make IBM i
Access for Web available for use
on the target system. IBM i
Access for Web must
first be configured and started before it can be used. To configure IBM i
Access for Web, refer to the Planning,
installing, and configuring checklist. The checklist contains steps
to install IBM i
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.
- Use the
CFGACCWEB command.
Continue with the checklist and run the steps to configure IBM i
Access for Web on the target system
using the CFGACCWEB command.
- Run the WRKLNK command.
After configuring IBM i
Access for Web, run the command WRKLNK
OBJ('/QIBM/UserData/Access/Web2/*') on the target system.
- 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
CFGACCWEB 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.
- Run the WRKLNK command.
On the source system,
run the command WRKLNK OBJ('/QIBM/UserData/Access/Web2/*').
- 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.
- 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.
- 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.
- Run the
CFGACCWEB command.
Now that all the user data files have been saved from the source
system and restored to the target system, the
CFGACCWEB 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.
- Return to the checklist.
Return to the Planning,
installing, and configuring checklist and complete any remaining steps.