Verifying instance creation

You can verify the creation of an instance by confirming the creation of instance-specific XML files and logs. Check these files to ensure that your instance was created successfully.


  1. Confirm that the instance was created.
    1. Check configuration information for the new WebSphere Commerce instance: WC_profiledir/installedApps/WC_instance_name_cell/WC_instance_name.ear/xml/config/wc-server.xml
    2. Check instance log files:
      • LinuxAIXWindowsWC_installdir/instances/instance_name/logs
      • For IBM i OS operating systemWC_userdir/instances/instance_name/logs
  2. LinuxAIXWindows If you are using IBM HTTP Server Web server, the following log file is produced during instance creation:
    • LinuxAIXWC_installdir/instances/instance_name/httplogs/error_log
    • WindowsWC_installdir/instances/instance_name/httplogs/error.log
    This file is not created until you start IBM HTTP Server.
  3. Ensure that there are no errors in the following log files:
    • createInstanceANT.err.log
    • createInstanceANT.log
    • LinuxAIXDB2Windows createdb.db2.log
    • messages.txt
    • trace.txt
    • For IBM i OS operating systemSchema.log
    • AIXWindowsFor IBM i OS operating systemsec_check.log
      Note: The sec_check.log file is created when the instance is started.
  4. Check that the following log file is created:
    • AIXWindowsWC_installdir/logs/WCSconfig.log
    • For IBM i OS operating systemWC_userdir/logs/WCSconfig.log
    • DB2WC_installdir/logs/reorgdb2.err.log
    WindowsNote: Errors in the trace.txt file like the following example can be safely ignored:
    date time java.lang.Class resolveRecord IdResGen
    The element with key "<acaction ACACTION_ID=10043
    	ACTION=BuyOrderApprovalSummaryView>" already exists
    	in the database therefore this record will not be updated.
  5. Optional: LinuxAIXDB2 The non-root user was assigned the DB2 instance owner privilege when you created your new instance. You can choose to remove it:
    1. Refer to your operating system documentation to remove the privilege from the non-root user.
    2. Edit the following file: non-root user home/.profile
      Remove the line below the following entry:
  6. Optional: To test multiple instances:
    1. Start the application server and web server of your instance.
    2. Test the following URLs:
      Original instance New instance
      • http://host1.domain
      • https://host1.domain
      • https://host1.domain:8000/accelerator
      • https://host1.domain:8002/adminconsole
      • https://host1.domain:8004/orgadminconsole
      • http://host2.domain
      • https://host2.domain
      • https://host2.domain:8000/accelerator
      • https://host2.domain:8002/adminconsole
      • https://host2.domain:8004/orgadminconsole