Troubleshooting: Problems starting Configuration Manager

If you are unable to start the Configuration Manager, use the information in this topic to troubleshoot the problem.

  • Ensure that you have met all of the following prerequisites that apply to the operating system you are using:
    1. SolarisLinuxWindowsAIXReview the information in the following topic:
    2. If you are using a remote Configuration Manager client, it must be at the same level as the Configuration Manager server.
    3. If you plan to start the Configuration Manager from a remote Configuration Manager machine, disable the firewall on the Configuration Manager server machine.
    4. If your web server is remote from your WebSphere Commerce server, you must create a directory to hold the web server configuration files and log files:
      1. Although any directory name can be used, it is recommended that you create the following directory: WindowsWC_installdir\instances\instance_name. SolarisLinuxWC_installdir/instances/instance_name. AIXWC_installdir/instances/instance_name.For IBM i OS operating system/QIBM/UserData/CommerceServer70/instances/instance_name.
        Note: When creating your instance through the WebSphere Commerce instance creation wizard, the path must be entered in the Remote Configuration Directory field of the Web server panel.
        Where:
        instance_name
        This variable represents the name of the WebSphere Commerce instance with which you are working (for example, demo).
      2. Your FTP and NFS users must have write permissions for these locations.
    5. SolarisLinuxAIXThe systems on which you are starting the Configuration Manager server and the Configuration Manager client use a supported locale. Ensure that the locale of the non-root user with which you are starting the Configuration Manager server and the Configuration Manager client use a supported locale.
    6. SolarisLinuxWindowsAIXEnsure that you have started your WebSphere Commerce database server.
    7. SolarisLinuxWindowsAIXEnsure that the DB2 Fenced user group is assigned to the DB2 user ID.
    8. SolarisLinuxWindowsAIXEnsure that you apply the most recent WebSphere Commerce fix pack. See the swg27007361.
    9. SolarisLinuxAIXDB2 The non-root user must be added to the db2_instance_group on the client side. Verify that your non-root user is part of the DB2 instance group by running the following commands:
      id non-root-user
      The db2 instance group should be in the list. If not, run the following command to fix it:
      WC_installdir/bin/wcnonroot.sh
      If you are using a remote database, make sure that the non-root user is part of the db2 instance group on the WebSphere Commerce node.
    10. SolarisLinuxWindowsAIXDB2Ensure that the WebSphere Commerce non-root user is part of the DB2 user group
    11. WebSphere Commerce EnterpriseWebSphere Commerce ProfessionalWindowsOracleIf you want to use an Oracle database, ensure that Oracle HTTP service is stopped before you create your instance.
    12. For IBM i OS operating systemIf you want to configure your IBM i system to use a remote database instead of a local database, complete the following steps.
      1. Start the DDM TCP/IP server on the remote IBM i system by completing one of the following steps:
        • In the System i Navigator on your remote IBM i system, use the Network option.
        • Run the following command: STRTCPSVR SERVER(*DDM)
        Note: When using the DDM server and the native JDBC driver, the QCCSID system value must be a valid CCSID other than 65535.
      2. Ensure that the DDM server is running on your IBM i system. To do so, check for job QRWTLSTN in subsystem QSYSWRK.
      3. Ensure that there is an entry for the remote database where the schema for your instance will be created. To do so, on the IBM i system where WebSphere Commerce is installed, run the WRKRDBDIRE command.
      4. On the IBM i system where WebSphere Commerce is installed, run the following command:
        RUNJVA CLASS(com.ibm.db2.jdbc.app.DB2PackageCreator) PARM('database_name' 'user' 'password')
        Where:
        database_name
        The name of the database where the schema for the instance will be created. On this remote system, use the WRKRDBDIRE command and record the Relational Database value defined as *LOCAL.
        user
        A profile with authority to create new objects on the remote IBM i system.
        password
        The password associated with the user.

        The command opens a Java Shell Display. The following message displays after the command completes: Java program completed

      5. Create a user profile on the remote system. The user profile must have the same name as the WebSphere Commerce instance that you are creating. Configure the user profile so that the language settings match the language you intend to choose as the default language for your WebSphere Commerce instance.
        Note: The password for the user profile must be the same as on the *LOCAL system (the machine where WebSphere Commerce is installed). This is the password that will be entered in the Instance Logon Password field of the Schema page while using the Configuration Manager to configure your instance.
      6. Ensure that the user profile for the instance you just created has authority to access the *SQLPKG objects in library QGPL. To do so, run the following command:
        GRTOBJAUT OBJ(QGPL/*ALL) OBJTYPE(*SQLPKG) USER(instance_name) AUT(*CHANGE)
    13. For IBM i OS operating systemIf you configured your IBM i system to use a remote database, ensure that you have installed the Remote WebSphere Commerce Management Utilities on a Windows PC.
  • Follow these instructions for opening the Configuration Manager.