Home
User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
Migrating
Before you migrate to WebSphere Commerce Version 8.0, review this information to help plan and execute your migration.
Migrating WebSphere Commerce
The following section outlines the available migration paths for moving from WebSphere Commerce Version 7.0 to WebSphere Commerce Version 8.0.
Migrating runtime environments (with staging servers)
The following section outlines the high-level steps that must be followed to migrate your runtime instance from version 7.0 to version 8.0. These steps are specific to version 7.0 environments that are configured with a staging or authoring instance.
Migrating the staging server
The following section outlines the high-level steps that must be followed to migrate your staging server from version 7.0 to version 8.0. The sequence of these migration steps is specific to version 7.0 environments that are configured with a staging or authoring instance.
Migrating WebSphere Commerce XML configuration files
You must prepare your wc-server.xml on your WebSphere Commerce Version 8.0 staging environment for migration. Once the file is updated, run the configMigration utility to migrate the wc-server.xml and any remaining XML configuration files.
Preparing the wc-server.xml file for migration
Many aspects of the WebSphere Commerce runtime application are configured in the wc-server.xml file, including configurations for your custom assets. To ensure that your version 7.0 customizations function as intended on version 8.0, you must update the version 8.0 wc-server.xml file to match the various version 7.0 configurations.

WebSphere Commerce Version 8.0.1.0 or later

Preparing the wc-server.xml file for migration

Many aspects of the WebSphere Commerce runtime application are configured in the wc-server.xml file, including configurations for your custom assets. To ensure that your version 7.0 customizations function as intended on version 8.0, you must update the version 8.0 wc-server.xml file to match the various version 7.0 configurations.

For your migrated customizations to work correctly, the following configurations must remain consistent across both version 7.0 and version 8.0 wc-server.xml files:

Host names
All paths and installation directories
AdminUser and AdminPwd
Note: If the AdminPwd values do not match, use the wcs_encrypt utility to generate an encrypted password. For more information about the wcs_encrypt utility, see Generate encrypted data (wcs_encrypt).

Before you begin

Manually copy your WebSphere Commerce Version 7.0 wc-server.xml file to a temporary directory on your WebSphere Commerce Version 8.0 environment.

Procedure

Open the wc-server.xml file that you copied to your version 8.0 environment.
Manually edit the file to ensure that the following configurations are met:
- Update hosts name from version 7.0 environment to version 8.0 environment.
- Update all paths from version 7.0 environment to version 8.0 environment.
- AdminUser and AdminPwd values must be the same on your version 8.0 environment as they were on your version 7.0 environment.
  Note: If the AdminPwd values do not match, use the wcs_encrypt utility to generate an encrypted password. For more information about the wcs_encrypt utility, see Generate encrypted data (wcs_encrypt).
Save the wc-server.xml file.
Check the file into a source code repository, and deploy the file by using WCBD (with synchronization Ant script) to your version 8.0 runtime environment. For more information about configuring WCBD to use the synchronization Ant script, see Setting up the WebSphere Commerce configuration file synchronization Ant script.