Appendix C. Migration scripts 259
Draft Document for Review July 28, 2004 7:33 pm 6320ax02.fm
The following two are additional steps for Switch-Over instance migration (for
Runtime environment only). You will not need to do these before migrating a local
WebSphere Commerce Suite V5.1 instance or a WebSphere Commerce Studio
V5.1 instance.
1. Package WCIM on v5.6 machine and its environment for remote execution:
Run WCIM to create a zip file including WCIM itself as well as the
environment it requires. This package will be used to build the migration
environment for the Switch-Over migration.
2. Unpack WCIM on v5.1 machine: Unzip the WCIM zip package generated
above. This builds the runtime environment with correct level of JDK, XML
parser, ANT, Configure Manager client, WCIM while maintaining the file
permission and ownership. Note that since the package created includes all
these platform dependent files, scripts and attributes you can not migrate
across platforms.
Migrating a local WebSphere Commerce Suite V5.1 instance or a WebSphere
Commerce Studio V5.1 instance:
1. Backup the instance to be migrated: Backup of the WebSphere Commerce
runtime environment is required in case of Switch-Over instance m igration. It
is optional, but recommended, in other instances. The backup includes:
– Configuration and ins tallation information of the previous WebSphere
Commerce install
– The configuration infor mation of the WebSphere Commerce instance to be
migrated
– The configuration infor mation of the local IBM HTTP Server
– The configuration information of WebSphere Commerce Payments and
supported payment cassettes and the deployed EAR.
– If there is no EAR, W CIM will collect enough information to be used to
build a migrated EAR. All files are compressed into a single ZIP
backup-instance.zip to be transferred to the target WebSphere Commerce
server.
2. Migrate the instance: This includes:
– Creating a migrated EAR ba sed on the original EAR and the default EAR
in the new release.
– Stores published before migration are wrap ped into a Web module.
Multiple Web modules and resource adaptors are added.
– EJBs for the correct database typ e, JSPs, servlets, commands, HTML
files, images from the new version are packaged into the migrated EAR,
too.
– An application ser ver 'WC_xxxx' is created with the correct configuration
required to run the migrated EAR.