IBM SG24-6320-00 User Manual
6320ch_planning.fm
Draft Document for Review July 28, 2004 7:33 pm
50
Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
3. Deploy the code changes from the development environment to the
production environment to finish the migration of the production environment
3.6.1 Detailed overview of development migration steps
Since all the following steps are performed on the development environment
there should not be any downtime on the production environment.
there should not be any downtime on the production environment.
1. Backup: Backup files, database and environment assets
2. Install/migrate software stack:
– upgrade Database level to DB2 Universal Database V8.1.5
– Install WebSphere Commerce Development environment on the same
– Install WebSphere Commerce Development environment on the same
system as your WebSphere Commerce Suite V5.1 development
environment. Switch-Over migration scenario for this environment is not
supported. This involves installing: WebSphere Studio Application
Developer, eFixes and WebSphere Commerce V5.6 Toolkit
environment. Switch-Over migration scenario for this environment is not
supported. This involves installing: WebSphere Studio Application
Developer, eFixes and WebSphere Commerce V5.6 Toolkit
•
Reconfigure development environment to use DB2 database by
running the “setdbtype” script
running the “setdbtype” script
– If required, install VisualAge for Java V4.0 on a separate machine, import
repository and apply fixes
3. Pre-migration actions
– Setup custom constraints
•
Before migrating the database you need to drop all your custom
constraints
constraints
•
Once you have finished migrating the database, the custom constraints
you dropped need to be re-established.
you dropped need to be re-established.
– Ensure that your data meets various other premigration requirements.
This includes messages, messages types, payments, catalog, members
and access control data.
and access control data.
4. Prepare code for importation into the WebSphere Commerce V5.6
development environment
– Export Java project from WebSphere Commerce Studio V5.1 as JAR
– Export EJB projects from VisualAge for Java V3.5.3 and import into
– Export EJB projects from VisualAge for Java V3.5.3 and import into
VisualAge for Java V4.0 to migrate the EJB level from 1.0 to 1.1. Export
EJB project from VisualAge for Java V4.0 as EJB 1.1 JARs.
EJB project from VisualAge for Java V4.0 as EJB 1.1 JARs.
You could also recreate EJBs in the WebSphere Commerce V5.6
development environment instead of installing VisualAge for Java V4.0
and channeling through it.
development environment instead of installing VisualAge for Java V4.0
and channeling through it.
5. Import files to WebSphere Commerce V5.6 development environment
– Import EJB project into WebSphere Commerce V5.6 development
environment in WebSphereCommerceServerExtensionData