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
andAdminPwd
Note: If theAdminPwd
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
andAdminPwd
values must be the same on your version 8.0 environment as they were on your version 7.0 environment.Note: If theAdminPwd
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.