Filter
Top Products
Chapter 12. Post-migration steps 231
Draft Document for Review July 28, 2004 7:33 pm 6320ch_post_migration.fm
Example 12-1 WebSphere Commerce section of httpd.conf
########## IBM WebSphere Commerce (Do not edit this section) #################
.
.
.
########## End of IBM WebSphere Commerce (Do not edit this section) ##########
If one of the following Web Server is used, then the configuration must be
migrated manually:
IBM HTTP Server running remote from WebSphere Commerce V5.6
Sun ONE Web Server (formerly known as iPlanet Web Server) running local
or remote from WebSphere Commerce V5.6
Refer to Migration Guide for Windows 2000 and Windows 2003 - migrating from
WebSphere Commerce Suite V5.1 for details on how to configure the above
mentioned Web servers.
12.2 Deploying
In order to finish the migration we must do a fresh deploy to the runtime
environment. This deploy will contain a build of all migrated EJBs, commands
and databeans and store assets. In each section below is described how to
deploy the individual components of the complete build.
The type of deployment described in this section is an incremental deployment.
In an incremental deployment, you must already have a WebSphere Commerce
enterprise application installed on the production WebSphere Commerce Server.
12.2.1 Deploying EJBs
Deploying the EJB consists of 2 steps:
1. Configuring and exporting the JAR file
2. Applying the JAR file to the production environment
The steps below describes the steps needed to deploy EJBs. These steps are
only valid for DB2 in development and production environment. If the production
database is different to the development database, refer to WebSphere
Commerce V5.6 Information Center.
Note: The Lotus Domino Web Server is no longer supported.