Install > Installing WebSphere Commerce > Installing WebSphere Commerce using the custom installation > Create a WCS instance


Before creating or modifying an instance with Configuration Manager


  1. Install fixes mentioned in the README file.

  2. Apply the most recent WebSphere Commerce fix pack.

  3. To run from a remote Configuration Manager machine, disable any firewalls.

  4. Verify the non-root user is part of the db2 instance group...

    id non_root_user

    The db2 instance group should be in the list. If not, to fix, run...

    WC_INSTALL/bin/wcnonroot.sh

    For remote databases, verify the non-root user is part of the db2 instance group on the WebSphere Commerce node.

  5. To use an Oracle database, ensure that Oracle's HTTP service is stopped before you create the instance.

  6. For remote Web servers, create a directory on the Web server to hold configuration and log files...

    IBM recommends...

    WC_INSTALL\instances\instance
    WC_USER/instances/instance

    When creating the instance using the instance creation wizard, on the Web server panel, enter the PATH in the field...

    Remote Configuration Directory

    FTP and NFS users must have write permissions for these locations.

  7. Install the Remote WebSphere Commerce Management Utilities on a Windows PC.

  8. Verify that you meet the prerequisites for starting Configuration Manager.

  9. Open Configuration Manager.

You should only modify the following Web server properties, as well as any WebSphere Commerce related properties, through the Configuration Manager GUI (and not through the Web server GUI nor the WebSphere Application Server Administrative Console):

This will ensure that all configuration files, not just the Web server configuration files, are updated properly with the correct information.


See


+

Search Tips   |   Advanced Search