Migrate > Migrating WebSphere Commerce > Overview of migrating the WebSphere Commerce database using the Migration wizard

Migrate the WebSphere Commerce database using the Migration wizard

The Migration wizard server runs on the system where WebSphere Commerce v7.0 is installed. For systems without graphic support, launch the Migration wizard client from another system that does have graphic support.

Before you begin

Review the following information before you start the database migration:

• If you are migrating the WebSphere Commerce database from one system (source) to another system (target), ensure you create a database user on the target system that has the same name as the database user on the source system.

• Ensure the X11 graphic library is installed.

• Verify the following files and directories are readable by the non-root user:

  • /root

  • /root/vpd.properties

  • WC_INSTALL/instances/instance/xml/instance.xml

• If you are running the Migration wizard on a system that is different from the one that has the WebSphere Commerce v5.6.1 or 6.0, copy the file:

  • WC_INSTALL/instances/instance/xml/instance.xml

  to a temporary directory on the WebSphere Commerce v7.0 system. During the migration, you are prompted for the location of this XML file.

• Execute the following steps to update the schemas before running the Migration wizard:

  1. Backup the WebSphere Commerce v6 schema by running the following commands:

     CRTSAVF FILE(mylib/WC6TO7) TEXT('WC v6 to v7')
     SAVLIB LIB(myinstance) DEV(*SAVF) SAVF(mylib/WC6TO7) ACCPTH(*YES)
     

  2. Open the following files:

     • QIBM/ProdData/CommerceServer70/properties/Toolbox_EXTWCSDTA_Customizer.properties

     • QIBM/ProdData/CommerceServer70/wc.ear/properties/Toolbox_EXTWCSDTA_Customizer.properties

     • QIBM/ProdData/CommerceServer70/properties/Toolbox_LODWCSDTA_Customizer.properties

     • QIBM/ProdData/CommerceServer70/wc.ear/properties/Toolbox_LODWCSDTA_Customizer.properties

     • QIBM/ProdData/CommerceServer70/properties/Toolbox_RESWCSID_Customizer.properties

     • QIBM/ProdData/CommerceServer70/wc.ear/properties/Toolbox_RESWCSID_Customizer.properties

  3. Add the following lines to the bottom of each file to add the IASPUrl variable:

     ### Added for database migration per IBM when using remote database or redirected RSTLIB
     IASPUrl = WCDEV/instance;database name=WCDEV;cursor hold=false 
     

     Where WCDEV is the relational database name and instance is the name of the WebSphere Commerce instance.

     This line fails when using the full hostname. For example, IASPUrl = wcdev.yourcompany.com/WCDEV7;database name=WCDEV;cursor hold=false.

  4. Open a terminal session emulator and perform the following steps:

     1. Login with the WebSphere Commerce v7 instance user:

        profile account (WCDEV7)
        

     2. Start an SQL command line:

        strsql 
        

     3. Create the WebSphere Commerce v7 schema (WCDEV7):

        CREATE SCHEMA WCDEV7 
        

        Then press F3 and 2 to close.

     4. Change the instance user profile's current library to the instance schema name (WCDEV7):

        CHGUSRPRF USRPRF(WCDEV7) CURLIB(WCDEV7) 
        

     5. Create the data area for the WebSphere Commerce v7 schema (WCDEV7) so that the journals under the WebSphere Commerce Version 6 schema register with the new owner:

        CRTDTAARA DTAARA(WCDEV7/QDFTJRN) TYPE(*CHAR) LEN(40) VALUE('WCDEV7 QSQJRN *ALL *RSTOVRJRN') 
        

     6. Confirm that the data area is correct:

        DSPDTAARA WCDEV7/QDFTJRN 
        

        Ensure the data area appears correct 'WCDEV7 QSQJRN *ALL *RSTOVRJRN' before restoring the library, then press F3 to close.

     7. Restore the WebSphere Commerce v6 schema as the WebSphere Commerce v7 schema name.

        RSTLIB SAVLIB(WCDEV6) DEV(*SAVF) SAVF(mylib/WC6TO7) OPTION(*NEW)
        MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(WCDEV7) 
        

     8. Save this restored schema before running the migration wizard:

        CRTSAVF FILE(mylib/WC7DEVA)
        SAVLIB LIB(WCDEV7) DEV(*SAVF) SAVF(TRACYTEST/WC7DEVA) 
        

     9. Delete the data area to bypass an issue with automatic journaling when the migration wizard runs:

        DLTDTAARA WCDEV7/QDFTJRN 
        

Procedure

The Migration wizard server must be launched from the WebSphere Commerce v7.0 system. The Migration wizard client can be run any system with graphic support.

1. To start the Migration wizard server:

   1. Complete one of the following steps:

      • Sign on with the non-root user and start a command line console.

      • Open a DOS command window.

      • Start a Qshell session.

   2. Navigate to directory: WC_INSTALL/bin.

   3. Complete one of the following tasks:

      • wcimServer.sh [-port port_number -loglevel log_level]

      • wcimserver.bat [-port port_number -loglevel log_level]

      Where:

      port_number

      Optional: The number of the endpoint port. If a number is specified, the value must be between 1024 and 65535. If a number is not specified, the default number is 10,999.

      log_level

      Optional: The level of logging can be set to ERROR, WARNING, INFO, DEBUG, or VERBOSE. The default value is VERBOSE.

   4. Wait for the following message to be displayed:

      Event: WCIM server started with protocol rmi at port 10,999.
      

      This indicates the server has started successfully.

2. To start the Migration wizard client:

   1. Complete one of the following steps:

      • Sign on with the non-root user and start a command line console.

      • Open a DOS command window.

   2. Complete one of the following tasks depending on the location of the Migration wizard server:

      • Local server: The Migration wizard server and client are running on the same system. Enter one of the following commands:

        • wcimClient.sh

        • wcimclient.bat

      • Remote server: The Migration wizard server and client are running on different systems. Enter one of the following commands:

        • wcimRemoteClient.sh -hostname hostname [-port port_number -loglevel log_level]

        • wcimRemoteClient.bat -hostname hostname [-port port_number -loglevel log_level]

        where:

        hostname

        The hostname of the system where the Migration wizard server is running.

        This is the fully qualified host name of the System i.

        port_number

        (Optional) The number of the endpoint port. If a number was specified to start the Migration wizard server, the same port number value must be specified for the client.

        log_level

        (Optional) The level of logging can be set to ERROR, WARNING, INFO, DEBUG, or VERBOSE. The default value is VERBOSE.

3. The Migration wizard's default user is wcimadmin and the default password is wcimibm. Use these values to sign in.

4. Select a product to be migrated, then click Launch.

What to do next

Follow the instructions within the Migration wizard to start the database migration.

To access the online help, click Help > Online Help.

• Complete the database migration
  After you have successfully migrated the database using the Migration wizard, additional tasks are required to complete the database tier migration.

+

Search Tips   |   Advanced Search