This topic contains information about upgrading iSeries™ Access
for Web from a previous release.
Portal environment considerations
If the iSeries Access
for Web default pages were created during the original portal configuration
and you changed those pages, it is recommended that you do not re-create the
default pages when you upgrade. If you re-create the pages, all customizations
and configurations settings are lost.
The page creation option is a parameter
on the iSeries Access
for Web configuration command CFGACCWEB2. Specify WPDFTPAG(*NOCREATE) if
you do not want to re-create the default pages. Specify WPDFTPAG(*CREATE)
to create the default pages. Refer to the help text for the CFGACCWEB2 command
and its parameters for more detail.
Note: If you used the IBM® Web Administration
for iSeries wizard
interface to create the portal instance and deploy the iSeries Access for Web portlets, the iSeries Access
for Web default pages were created automatically.
Upgrade from V5R1 iSeries Access for Web
If you
have V5R1 iSeries Access
for Web (5722-XH1) installed on your server, installing V5R4 iSeries Access
for Web (5722-XH2) has no impact on the V5R1 installation. V5R1 and V5R4 iSeries Access
for Web can coexist on the same server.
When V5R4 iSeries Access for Web is configured
using the CFGACCWEB2 command, the following automatically occur the first
time the command is run:
- V5R1 iSeries Access
for Web user generated data is copied to the V5R4 iSeries Access for Web directory structure.
- The V5R1 iSeries Access
for Web policy information is copied to the V5R4 iSeries Access for Web configuration.
- The V5R1 iSeries Access
for Web file content-type (MIME-type) mappings are copied to the V5R4 iSeries Access
for Web configuration.
To prevent these from happening automatically, follow these steps before
running the CFGACCWEB2 command:
- Create the file /QIBM/UserData/Access/Web2/config/migration.properties.
- Using an editor, add was35migrationrun=true to the migration.properties
file.
