Migrating WebSphere Commerce Enabled Portal

This page describes the migration steps for the WebSphere Commerce Enabled Portal to the WebSphere Commerce Version, 6.0 level for base WebSphere Commerce portlet functionality.

  1. Migrate WebSphere Portal from version 5.0 to version 5.1.0.1 according to the instructions in the WebSphere Portal Information Center at: http://www.ibm.com/developerworks/websphere/zones/portal/proddoc.html. For Commerce portlet migration, the following portal migration command are required.
     export-apps/import-apps -DincludeApps=com.ibm.commerce.portal.WCSPortalNameSpace 
     export-pages/import-pages -DincludePages=wcep.* -DconfigThemesSkins=true
     export-portlets-configs/import-portlets-config -DincludeApps=com.ibm.commerce.*
     export-themes-skins-configs/import-themes-skins-configs
     
    
    For more details, refer WebSphere Portal Information Center.
  2. Install WebSphere Commerce Portal on the WebSphere Commerce machine (ensure that you do not choose to "configure" the Commerce Portal, only choose to "install" it).

    Note: When installing WebSphere Commerce, ensure the Portal option has been passed to the installer. For example:

    • AIXsetup_aix -Portal
    • i5/OSFrom a Windows machine, type: setup.exe -os400 -Portal
    • Linuxsetup_linux -Portal
    • Sun Solaris Operating Environmentsetup_solaris -Portal
    • Windowssetup -Portal
  3. After installation is complete, copy the file commerceportal.jar from the following directory on the WebSphere Commerce machine to the portal machine:
    • i5/OSLinuxWC_installdir/Portals/B2CPortletApp/WEB-INF/lib
    • WindowsWC_installdir\Portals\B2CPortletApp\WEB-INF\lib
  4. Replace the commerceportal.jar file in the following directory in the Portal machine with the commerceportal.jar file from WebSphere Commerce 6.0:
    • i5/OSLinuxPortal_installdir/installedApps/portlet_app_ear_name/portlet_war_name/web-inf/lib
    • WindowsPortal_installdir\installedApps\portlet_app_ear_name\portlet_war_name\web-inf\lib

    Note: There are many .ear directories under the installedApps subdirectory with similar names. The portlet_app_ear_name might be similar to "WCEP_B2C_PA_1_0_69.ear", and portlet_war_name might be similar to "WCEP_B2C.war" on your system. If you are using Winstone store, copy Default.jsp and ToolBarInclude.jsp files from

    <WC60_HOME>/Portals/skins/WinstonsTheme.zip 
    
    file on WebSphere Commerce machine to the WebSphere Commerce Portal machine. Replace these two files on
    <WAS6>/profiles/default/installedApps/<NodeCell>/wps.ear/wps.war/themes/html/WinstonsTheme
    
    directory on the WebSphere Commerce Portal machine.
  5. Before migrating the WebSphere Commerce instance, clear the "enable security" check box in the WebSphere Application Server administration console. Save you modification.
  6. Migrate the WebSphere Commerce instance as described in Migrating your WebSphere Commerce instance configuration.
  7. Add WAPPORTAL, PORTAL to /webapp/wcs/stores module in wc-sever.xml file, which is in
    <WAS6_Home>/profiles/<instance_name>/installedApps/WC_<instance_name>_cell/WC_<instance_name>ear/xml/config>.
    
    <Module contextPath="/webapp/wcs/stores"
    fileServletEnabled="false"
    name="Stores"
    urlMappingPath="/servlet"
    webAlias="/wcsstore">
    <InitParameters adapters="XML/HTTP, WAPPORTAL, PORTAL, BrowserAdapter"
    contextSetName="Store"
    handleDoubleClick="true" />
    </Module>
    
  8. After completing the WebSphere Commerce instance migration, check the "enable security" check box in the WebSphere Application Server administration console.
  9. Save your modification. Restart WebSphere Commerce Server.
  10. If Portal migration takes place remotely, the following steps might be required:
    1. If WebSphere Portal and the LDAP server have been installed on a single node, the LDAP server settings could need to be changed. If so, you need to correct the LDAP Server address on the corresponding fields of the WebSphere Portal and the WebSphere Commerce machines. See the sections on Commerce Enabled Portal.
    2. Enable Single Sign On (SSO) by exporting LTPA key from the WebSphere Commerce, and then importing LTAP key into WebSphere Portal.
    3. Configure LDAP settings on the WebSphere Commerce node to ensure that user "wpsbind" can be authenticated. If WMM is installed on the WebSphere Commerce node, the user wpsbind needs to be authenticated for the WMM application also. For more information on enabling security, go to Enabling security with an LDAP user registry.
      1. Open the WebSphere Application Server Administration Console for the WebSphere Commerce machine.
      2. Go to Security --> Ldap --> Advanced LDAP Settings
      3. Modify the User Filter value to "(&(uid=%v)(objectclass=inetOrgPerson))"
      4. Save the changes
      5. Restart WebSphere Application Server instances.
  11. Exchange the SSL certificate between the WebSphere Commerce and Portal nodes.
    1. Copy the SSL certificate for the WebSphere Commerce node to the Portal machine.
    2. Run ikeyman file from the WAS_installdir/bin directory on the WebSphere Portal machine. Import the SSL certificate into the WebSphere Portal JDK.
      1. On the WebSphere Portal node, do the following:
        • At a command prompt, type the following: cd to WAS_HOME/bin. Type: ikeyman. The IBM Key Management window displays.
        • Select Key Database File -> Open. Browse to the cacerts file:
          WAS_HOME/java/jre/lib/security/cacerts. 
          
          Select cacerts. Click OK. The Password Prompt dialog displays. Type the password and click OK.
        • In the key database content section, select Signer Certificates from the list. If wcepcertificate displays in the list, delete it.
        • Click Add. The Add CA's Certificate from File dialog displays. Browse to the location of the cert.arm file you extracted above. For example, c:\temp\cert.arm.
        • Click Open. Then click OK. The Enter a Label dialog displays. Type wcepcertificate in the label field. Click OK.
    3. Open the WAS_installdir/etc/DummyServerTrustFile.jks file (the default password is WebAS) on the WebSphere Portal machine.
    4. Import the SSL certificate into the DummyServerTrustFile.jks file by doing the following:
      1. From the Key Database File menu, select Open. Browse to the DummyServerTrustFile.jks file. By default this file is located in WAS_HOME/etc.
      2. Select the DummyServerTrustFile.jks file. Click Open, then click OK. The Password Prompt dialog displays. Type the password and click Open.
      3. In the Key database content section, select Signer Certificates from the list.
      4. If wcepcertificate displays in the list, delete it.
      5. Click Add. The Add CA's Certificate from File dialog displays. Click Browse and browse to the location of the cert.arm file you extracted above. For example, c:\temp\cert.arm. Click Open. Then click OK. The Enter a Label dialog displays.
      6. Type wcepcertificate in the label field. Click OK.
    5. Save your changes.
    6. Close the IBM Key Management program.
  12. Restart WebSphere Portal.

Feedback