Filter
Top Products
6320ax02.fm Draft Document for Review July 28, 2004 7:33 pm
260 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
– The JDBC provider and the datasource is configured for the server. The
migrated EAR is installed onto the server.
– The deployment descriptor is modified as well.
– Configuration of the original instance, including instance itself, access
control, organization, trading, loader, payment, and store JSPs are
migrated.
– The Web server host name and the database name / SID can also be
changed by WCIM during the migration if users choose to do so.
– For the Switch-Over migration, the correct Web server host name,
WebSphere Application Server node name and WebSphere Application
Server cell name are configured for the migrated instance.
– For local replace migration, the same Web server host name is assumed
but user can take this opportunity to switch to a different Web server. For
local coexistence migration, a different Web server host name is enforced.
Local IHS is configured. WebSphere Application Server plug-in
configuration is regenerated. Backup step and migration step can be
executed together for local migration. No human intervention is required in
between.
– For local coexistence migration or 5.5 to 5.6 local replace migration, a
temporary host name is required for migration. WCIM can perform
IP-switching to reconfigure the migrated instance to use the final Web
server host name. WebSphere Application Server virtual hosts, instance
configuration XML file and local IHS configuration are modified.
WebSphere Application Server plug-in configuration is regenerated.
3. The development environment is migrated by WCIM is a similar fashion as
detailed in the steps 3 and 4. In addition, custom store assets, servlets,
commands are moved to pre-configured projects of Stores and
WebSphereCommerceServerExtensionLogic in the new workspace.
Custom database migration scripts behavior
To ease the task of migrating the database we created custom scripts which
would run prepare, migrate and post migration tasks on the database. In this
section we describe the behavior of the scripts.
Note: The WCIM tool will convert all occurrences of <%@ page
language="JAVA" %> to <%@ page language="java" %> during this step,
although we found that not all occurrences was modified. After this step
ensure that no more occurrences of <%@ page language="JAVA" %>
exists. This can be done by doing a file content search