Review this information while using the Migration wizard
to migrate your WebSphere Application tier. Follow the information
if you want to migrate your application tier using the WCIM script.
Before you begin
- Ensure you have completed the database migration successfully.
- Application tier migration using mapped or networked drives is
not supported.
- If WebSphere Application Server Global Security
is enabled, disable it before you migrate your application.
- If you are performing a remote application migration,
the following steps must be completed before starting the application
migration script:
- Install WebSphere Application Server version 7 on the WebSphere
Commerce Version 5.6.1 or 6.0 machine.
- Copy WC_installdir/bin/backupAppWAS400.sh on
the WebSphere Commerce Version 7 machine to a temporary directory tempDir on
the WebSphere Commerce Version 5.6.1 or 6.0 machine.
- Run tempDir/backupAppWAS400.sh on the WebSphere
Commerce Version 5.6.1 or 6.0 machine. For more information, run backupAppWAS400.sh
directly to see its usage details.
- Copy prod.jar, user.jar, and backupforpostupgrade.jar from /tmp on
the WebSphere Commerce Version 5.6.1 or 6.0 machine to a temporary
directory tempDir70 on the WebSphere Commerce Version
7 machine.
- Run WC_installdir/bin/restoreAppWAS400.sh on
the WebSphere Commerce Version 7 machine to restore the backup files.
For more information, run restoreAppWAS400.sh directly to see its
usage details.
- Ensure your WebSphere Application Deployment Manager and all federated
node agents for WebSphere Commerce version 5.6.1 or 6.0 are stopped.
About this task
The following functions are performed by the WCIM utility:
- Backing up of the existing application tier that is being migrated
- Migration of the existing application tier to the WebSphere Commerce
Version 7.0 level
Note: If you are using multiple instances on your previous installation
of WebSphere Commerce, you must back up and migrate each instance
separately.
Procedure
- Choose one of the following options to migrate your application
tier:
- WebSphere Commerce Version 7.0 and previous
version are on different machines
- Insert the WebSphere Commerce Version
7.0 media into the drive on the machine where the previous version
of WebSphere Commerce is installed.
Note: You might also
be prompted to insert a WebSphere Application Server supplemental
DVD.
- If you run the
installation on AIX version 5.3, you may get an error forcing you
to cancel the installation, with a message similar to the following
example:
AIX 53 Maintenance Level 06-01 was detected. AIX 53 Maintenance level 07-01 is required.
Upgrading
your operating system will prevent this message. If you do not want
to upgrade your old WebSphere Commerce server operating system, an
alternate migration path has been provided. Perform the following
steps:
- On your WebSphere Commerce 7.0 system, make a copy of WC_installdir\bin\backupAppWAS60.sh to
a temporary directory, tempdir, on the remote (old)
machine.
- Run the following command as the root user on your old WebSphere
Commerce server:
tempDir/backupAppWAS.sh -oldWASDir WAS_installdir -oldWCSDir WCS_installdir [oldProfileName]
- The script creates two folders in tempDir.
Copy tempDir to your WebSphere Commerce version
7 server.
- Run the following command on the WebSphere Commerce version 7
server:
chown -R wasuser:wasgroup tempDir
- If you are not running AIX 5.3, and are
not forced to cancel the installation, select Custom installation and
choose to install only the Remote WebSphere Commerce Management
Utilities component.
- If you are migrating from WebSphere
Application Server Version 6.1, you need to change some file permissions
before running the wcimRemoteBackup script:
- Log in as root.
- Open a command line session and change to the WAS_installdir\properties directory.
- Run the following command:
chmod o+r NIFRegistry.properties profileRegistry.xml WSCustomConstants.properties
Remember: Change the file permission back for security reasons
after completing the application migration.
- On the machine
where you just installed the remote WebSphere Commerce Management
Utilities, navigate to the WC_installdir/bin directory
and run the following command:
where:
- version
- The original WebSphere Commerce version. Enter 561 or 60.
This script creates a folder,
WC_installdir/temp/zip,
containing two files:
- backupwas.zip
- backupwc_version_instance_name.zip.
- Copy the resulting
folders to the WebSphere Commerce Version 7.0 target system. Ensure
the files are put in WC_installdir/temp/zip and
ensure that the WebSphere Commerce non-root user is the owner of WC_installdir/temp/zip and
the files. The Migration wizard displays the directories where the
files must be placed.
- If you used backupAppWAS.sh or backupAppWAS400.sh
to backup previous WebSphere Commerce application in step 2, then
on your WebSphere Commerce version 7 machine, back up your version
7 WebSphere Commerce application tier and the application tier related
assets using WCIM. For example:
where:
- previous_version
- Is the version of WebSphere Commerce you are migrating from for
example, 561 or 60.
When prompted, ensure that you:
- Specify the tempDir/WAS as
the previous WebSphere Application Server directory.
- Specify tempDir/Commerce as
the previous WebSphere Commerce directory.
- Migrate your application using the
WCIM utility:
- Verify that WCIM ran successfully.
- Perform post migration steps.
- Configuring the application server and web server tiers from the command line.
- WebSphere Commerce Version 7.0 and previous
version are on the same machine
- On your source machine, back up your current WebSphere
Commerce application tier and the application tier related assets
using WCIM. For example:
where:
- previous_version
- Is the version of WebSphere Commerce you are migrating from for
example, 561 or 60.
For example:
./wcim_ant.sh -tier app -from 60 -action backup -instanceName mig60inst3
Are the two WebSphere Commerce products installed on the same machine? [ Yes ] (Yes,No,)
Yes
Previous WebSphere Commerce installation directory?
/QIBM/Proddata/CommerceServer60
Previous WebSphere Application Server installation directory?
/QIBM/UserData/WebSphere/AppServer/V6/ND/profiles/<instance_name>
Previous WebSphere Application Server profile name?
<instance_name>
- Migrate your application using the WCIM utility:
For example:
./wcim_ant.sh -tier app -from 60 -action migrate -instanceName <instance_name>
Database type? [ db2 ] (cloudscape,db2,os400,oracle,)
os400
Remote database? [ false ] (true,false,)
false
Database name?
<database_name>
Database user?
<instance_name>
Database user password?
<db password>
Database server port?
50000
Web server type? [ HTTP ] (HTTP,IIS,NES,)
HTTP
Remote Web server? [ false ] (true,false,)
false
Are the two WebSphere Commerce products installed on the same machine? [ Yes ] (Yes,No,)
Yes
Is the WebSphere Application Server Global Security enabled? [ No ] (Yes,No,)
No
Is it a cluster member? [ No ] (Yes,No,)
No
- Verify that WCIM ran successfully.
- If
you disabled WebSphere Application Server Global Security before you
migrated the application, you can re-enable it.
- Configuring the application server and web server tiers from the command line.