Introduced in Feature Pack 2

Migrating store functions and store style from WebSphere Commerce Accelerator to Management Center

Use the migrateStoreFunctions utility to migrate store functions and store style from WebSphere Commerce Accelerator to Management Center.

By running the store functions migration utility, you migrate existing store function data and store style data so that business users can use the Store Management tool within Management Center to manage store functions and store style, instead of WebSphere Commerce Accelerator.
Note: Prior to WebSphere Commerce Version 7 Feature Pack 2, store functions were referred to as change flows.

Before you begin

Ensure that you review and understand the information in Overview of migrating store functions and store style from WebSphere Commerce Accelerator to Management Center Version 7 Feature Pack 2.

Ensure that you complete the following tasks before you run the store functions migration utility:

About this task

The store functions migration utility is a script that calls an ANT task. This ANT task loads a configuration file to migrate store functions data and store style data to the Management Center database tables. Error conditions are written to standard output. The store functions migration script performs the following actions:
  • Converts store function settings and store style settings that are contained in the Features.xml file to e-Marketing Spot data.
  • Disables the change flow option in WebSphere Commerce Accelerator.

Procedure

  1. Stop the WebSphere Commerce server.
  2. SolarisLinuxAIX Ensure that you run the store functions migration utility as the wasuser user. To do so, issue the following command:

    su - wasuser_IDWhere wasuser_ID is the non-root user ID. This ID must be created before you install WebSphere Commerce. The default WebSphere Application Server user name is wasuser.

  3. Open a command-line utility.
  4. Run the store functions migration utility with arguments that specify the build file and the information that is needed to connect to a database in the server environment
    • WebSphere Commerce DeveloperCall the migration script with the following command: WCDE_installdir/components/management-center/bin/migrateStoreFunctions.bat -Dstore="storeId1, storeId2" -verbose
      -Dstore
      (Mandatory). Specifies the store IDs of the stores that you want to migrate, separated by commas. To migrate all of the stores in the database, use -Dstore="ALL"
      -verbose
      Indicates that you require more logging for use when you need to debug the command.

      You can review the migrateStoreFunctions.log file in the WCDE_installdir/logs/directory.

    • WebSphere Commerce EnterpriseWebSphere Commerce ProfessionalWebSphere Commerce - ExpressCall the migration script with the following command:
      • WindowsWC_installdir\bin\config_ant.bat -buildfile WC_installdir\components\management-center\migration\optional\components\management-center\subcomponents\store\config\StoreFunctionsMigration.xml -DinstanceName=instance_name -DdbUserName=database_username -DdbUserPassword=database_password -Dstore="storeId1, storeId2" -logfile logfile_path -verbose
      • SolarisLinuxAIXWC_installdir/bin/config_ant.sh -buildfile WC_installdir/components/management-center/migration/optional/components/management-center/subcomponents/store/config/StoreFunctionsMigration.xml -DinstanceName=instance_name -DdbUserName=database_username -DdbUserPassword=database_password -Dstore="storeId1, storeId2" -logfile logfile_path -verbose
      -buildfile
      (Mandatory) Specifies the build file to use for the migration. This parameter must be followed by the path to the migration build file as shown.
      -DinstanceName
      (Mandatory) Specifies the instance to migrate. When you use this parameter, replace instance_name with the name of the WebSphere Commerce instance for which you are migrating the store functions data and the store style data.
      -DdbUserName
      (Mandatory) Provides the user account to use to connect to the database. When you use this parameter, replace database_username with the WebSphere Commerce database user's username.
      -DdbUserPassword
      R(Mandatory) Provides the password to use to connect to the database. When you use this parameter, replace database_password with the WebSphere Commerce database user's password.
      -Dstore
      (Mandatory) Specifies the store IDs of the stores that you want to migrate, separated by commas. To migrate all of the stores in the database, use -Dstore="ALL"
      -logfile
      . Specifies the location of a log file. When you use this parameter, replace logfile_path with the absolute path of a file to contain logging information, for example, C:\logs\migrateStoreFunctionsLog.txt. If you do not specify this parameter, the logging information is displayed in the console.
      -verbose
      Indicates that you require more logging for use when you need to debug the command.

What to do next

After you run the store functions migration utility, you must manually migrate the Management Center user interface files. This migration ensures that your site is configured to support the new store function settings and store style settings available with Management Center.
If you plan to use WebSphere Commerce search:
  1. Review the information and tasks in Migrating WebSphere Commerce search.
  2. Feature Pack 7 or laterPerform the following task: Disabling the remote Business Context Service (BCS) call.