Verifying your migrated IBM Websphere Commerce Version 8 application

Now in the migration, you have a fully migrated development environment. Verify that your migrated assets are working as designed in your development environment.


  1. Start the HCL Commerce test server.
  2. Right-click the test server in the Servers view and select Publish. Wait for the application to finish publishing and to restart.
  3. Check the log file to ensure that no errors occurred during the development environment migration.
    1. Go to directory WCDE_installdir/logs/WCIM.
    2. Find the migration log file. The log file name is formatted as follows:
      wcim.component.date_time.log, for example, wcim.server.2009.
      The component that was migrated. For example, when you migrate HCL Commerce, the value is server.
      The date and time when the log is created (yyyy. mm. dd. hh. mm. ss) when the log was created.
      The year portion of the time stamp.
      The month portion of the time stamp.
      The day portion of the time stamp.
      The hour portion of the time stamp.
      The minutes portion of the time stamp.
      The seconds portion of the time stamp.
  4. Access your migrated store by entering the store URL into a browser. The following URL is an example of a store URL.
    • https://localhost/webapp/wcs/stores/servlet/en/auroraesite
  5. Optional: Enter the URL to launch the custom application:
    • http://localhost/webapp/wcs/stores/servlet/MyNewControllerCmd?input1=test@test&input2=10
    Where test@test is a valid HCL Commerce user ID.
  6. Complete a shopping flow.
  7. Open any of the following HCL Commerce tools and ensure that they function as expected.
    • https://localhost:8000/webapp/wcs/tools/servlet/ToolsLogon?XMLFile=common.mcLogon
    • https://localhost:8002/webapp/wcs/admin/servlet/ToolsLogon?XMLFile=adminconsole.AdminConsoleLogon
    • https://localhost:8004/webapp/wcs/orgadmin/servlet/ToolsLogon?XMLFile=buyerconsole.BuyAdminConsoleLogon
    • https://localhost:8000/lobtools
  8. Complete any additional testing on your custom application, including regression tests.