Migrating WebSphere Commerce 5.4 Professional Edition to WebSphere Commerce 5.4 Business Edition on iSeries

This document describes how to migrate from IBM® WebSphere® Commerce 5.4 Professional Edition to WebSphere Commerce 5.4 Business Edition on the iSeries® platform.  The document assumes that you currently have a working WebSphere Commerce 5.4 Professional Edition system, and wish to upgrade to Business Edition in order to take advantage of the additional B2B functionality that the Business Edition offers. That is, using the WebSphere Commerce 5.4 Installation Guide for iSeries, you have successfully:

• Installed WebSphere Commerce 5.4 Professional Edition
• Created an instance
• Published a store at which users can shop.

Before you begin migration:

• You require the WebSphere Commerce 5.4 Business Edition CD in order to upgrade your software level from Professional Edition to Business Edition.
• You need to download the latest WebSphere Commerce 5.4 FixPaks for Professional Edition and for Business Edition from the following web site to your machine:
      http://www.ibm.com/software/webservers/commerce/wc_pe/downloads.html (Professional Edition)
    http://www.ibm.com/software/webservers/commerce/wc_be/downloads.html (Business Edition)
  
  You will need to apply the FixPak for Professional Edition before you upgrade to Business Edition in order to have access to rmCommerceServer script required in this process. You will need to apply the FixPak for Business  Edition after you upgrade your software from WebSphere Commerce 5.4 Professional Edition to WebSphere Commerce 5.4 Business Edition but prior to migrating your assets, such as the WebSphere Commerce database and instance. Refer to the installation instructions that accompany the FixPaks for details on how to apply them.
• Ensure that your machine hardware and prerequisite software meets the requirements documented in the "Preinstallation requirements" chapter in the WebSphere Commerce 5.4 Installation Guide for iSeries.

The following are the steps to migrate your WebSphere Commerce 5.4 Professional Edition system to WebSphere Commerce 5.4 Business Edition:

1. Back up your WebSphere Commerce 5.4 Professional Edition instance.
   
   Before proceeding with the migration, back up your current instance.  Refer to the chapter "Backing up Commerce Suite 5.1" in the WebSphere Commerce 5.4 Migration Guide for iSeries for guidance. In particular, use the following commands:
   • SAVLIB  <your_instance>
   • SAV DEV('/qsys.lib/<your_Lib>.lib/<your_instance>_ifs.file') OBJ(('/QIBM/UserData/WebCommerce/instances/<your_instance>'))
   • SAV DEV('/qsys.lib/j<your_Lib>.lib/<your_instance>_pym.file') OBJ(('/QIBM/UserData/pymsvr/<your_instance>'))  Only required if you are using WebSphere Payment Manager.
      

   Rename /qibm/UserData/WebASAdv4/<your_WAS_Instance>/installedApps/WC_Enterprise_App_<your_instance>.ear to: /qibm/UserData/WebASAdv4/<your_WAS_Instance>/installedApps/WC_Enterprise_App_<your instance>.ear_PRO

   This renamed .ear file will required later for store asset migration.
    

2. Apply the latest WebSphere Commerce 5.4 Professional Edition FixPak.
   
   Follow the instructions provided in the FixPak to install it.
    

3. Remove the WebSphere Commerce application server.
   
   Remove the WebSphere Commerce server in the WebSphere Application Server Administration Console by running the rmCommerceServer script supplied with the FixPak:

   • Start WebSphere Application Server, if it is stopped.

   • Stop the WebSphere Commerce application server in the Administrative Console, if it is running.

   • Start a Qshell session by typing QSH on the command line.
   • In the Qshell session, traverse to the WebSphere Commerce BIN subdirectory (/QIBM/ProdData/WebCommerce/bin) and run the rmCommerceServer script as follows:

     rmCommerceServer instance_name

     where instance_name is your WebSphere Commerce instance (for example, demo).

     Notes:

     • The rmCommerceServer script does not delete the  /QIBM/UserData/WebAsAdv4/<WAS_admin_server_instance>/installedApps/WC_Enterprise_App_<instance_name>.ear folder (ear folder) and its contents, because it contains the store assets. You need to rename the ear folder. The instance migration program (MIGWCSINST) will create a new ear folder that contains business features. You need to restore your store assets from the old ear folder to the new ear folder after you migrate your instance.
     • If you receive errors similar to the following in the rmCommerceServer.log file, you can safely ignored them:
       
       WSCP0061E: Object not found : /JDBCDriver:ywtbx WebSphere Commerce Suite Toolbox JDBC Driver/
       
       Toolbox JDBC driver is used by a remote database instance, if your instance uses local database, it does not have a Toolbox to be deleted. The error can be ignored.
       
       RemoteException occurred in server thread; nested exception is:
       java.rmi.RemoteException: ADMR3421E: The Virtual Host cannot be removed because it is currently being used by Module.
       
       If the commerce instance shares the same virtual host with some other application server (for example, a Payment Manager instance), that virtual host will be in use and cannot be deleted. The error can be ignored.
        
4. Rename the IBM HTTP Server configuration files related to your instance.
   
   For example, if your instance name is demo, rename the following files:
   • /QUSRSYS.LIB/QATMHINSTC.FILE/DEMO.MBR
   • /QUSRSYS.LIB/QATMHINSTC.FILE/DEMOT.MBR
   • /QUSRSYS.LIB/QATMHTTPC.FILE/DEMO.MBR
   • /QUSRSYS.LIB/QATMHTTPC.FILE/DEMOT.MBR

   The instance migration program (MIGWCSINST) will create new IBM HTTP Server configuration files for your instance. If you have customized the IBM HTTP Server configuration files for your instance, you need to retrofit the changed into the new IBM HTTP Server configuration files after the migration.

    

5. Upgrade WebSphere Commerce 5.4 Professional Edition to Business Edition. 
   
   Perform this upgrade by installing Option 3 on the Restore Licensed Program command as follows:
   1. Type RSTLICPGM  (Restore Licensed Program) on the command line.
   2. Press PF4 for a prompt.
   3. Type the LICPGM (5733WC5) and DEV name in the appropriate entry fields.
   4. Type OPTION(3)and RSTOBJ(*PGM) to install additional WebSphere Commerce Business Edition components, and press Enter. An acknowledgment message displays, indicating that Option 3 has been restored. You have now completed installing WebSphere Commerce Business Edition.

   Ensure that you apply the latest WebSphere Commerce 5.4 FixPaks for Business Edition.
    

6. Migrate your instance.
   
   Ensure that the WebSphere Application Administrative Server is running. The same administrative server will be used.

   Using an iSeries profile that has *SECOFR authority, run the MIGWCSINST (Migrate WebSphere Commerce Instance) command from the command line:
   
   MIGWCSINST your_instance

   The command has one input, your_instance, which is the instance name that the you want to migrate. The specified instance is migrated from Commerce Suite 5.4 Professional Edition to WebSphere Commerce 5.4 Business Edition. The MIGWCSINST command migrates your instance configuration files, creates two Web server configuration files, and creates the WebSphere Application server instance for your instance.

   To verify that the instance migration completed successfully, check the instance_name_instMigrate.log file in the /QIBM/UserData/WebCommerce/instances directory. You should see a statement indicating that the migration completed successfully at the end of the log to indicate a successful migration of the instance.

   Also, to check whether the Enterprise JavaBeans (EJBs) deployment is successful, check the WASConfig.log file (the log file for importing EJBs) in the /QIBM/UserData/WebCommerce/instances/instance_name directory. To verify that the instance configuration migration completed successfully, ensure that no exceptions have occurred.

   After a successful migration, copy wcstores.war from /qibm/UserData/WebASAdv4/<your_WAS_Instance>/installedApps/WC_Enterprise_App_<your_instance>.ear_PRO to: /qibm/UserData/WebASAdv4/<your_WAS_Instance>/installedApps/WC_Enterprise_App_<your_instance>.ear

   This will restore your store assets.

   
    

7. Migrate your database.
   
   The commands below only alter the SITE table and WebSphere Commerce bootstrap data.

   1. Using SQL - delete all entries from the <your_instance>.SITE table.
   2. LODWCSDTA DATABASE(TORASCSA) SCHEMA(<your_instance>) PASSWD(<your_instance_logon_password>)INSTROOT(<your_instance_root>) INFILE('/qibm/proddata/webcommerce/schema/xml/wcs.site.xml') METHOD(*SQL)
   3. LODWCSDTA DATABASE(TORASCSA) SCHEMA(<your_instance>) PASSWD(<your_instance_logon_password>)INSTROOT(<your_instance_root>) INFILE('/qibm/proddata/webcommerce/schema/xml/wcs.bootstrap_adv.xml') METHOD(*SQL)

   where the default WebSphere Commerce instance root directory is '/QIBM/UserData/WebCommerce/instances/<your_instance>'
    

8. Restart IBM HTTP Server and your migrated WebSphere Commerce 5.4 Business Edition instance
   
   For instructions on how to start WebSphere Commerce servers, refer to Appendix A. "Starting and stopping components" in the WebSphere Commerce 5.4 Installation Guide for iSeries.
    
9. Verify that your migrated WebSphere Commerce 5.4 Business Edition system and stores are operational.
   
   Ensure that your migrated stores continue to run as before.  Use the WebSphere Commerce 5.4 online help system to implement B2B features as required for your migrated Business Edition system. You may also consult the "What ’s New in IBM WebSphere Commerce, 5.4" manual to see what additional features are now available to you. An easy way to get familiar with the Business Edition is to publish a sample store called ToolTech. This store shows you the new B2B features such as Inventory Control, Contracts, and so on.

The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both: