Install > Installing WebSphere Commerce > Prepare to install WebSphere Commerce > Prerequisites for installing WebSphere Commerce


Networking prerequisites


AIX 5.3 and 6.1, Linux, and Solaris

  1. Verify the system has a resolvable fully qualified host name. For example...

    nslookup system1.mydomain.com

  2. Review settings in...

    /etc/hosts

    ...and verify configuration by running...

    ping hostname ping localhost

    If either command fails, correct the /etc/hosts file.

  3. The IP address on the system must resolve to a host name (including a domain).

    Verify the IP address is mapped to a fully qualified host name...

    nslookup IP_address

    The result should be a reply with the correct fully qualified host name of the system.

    Another command to determine fully-qualified DNS name, run: "uname -n"

  4. Ensure all nodes in the configuration can be reached from other computers in the network by pinging the fully qualified host name of each node in the configuration.

  5. Verify the system is DNS enabled so that there is a host name and domain present. Pure IP address environments are not supported by WebSphere Commerce.

  6. You must have both a name server and a search domain defined in...

    /etc/resolv.conf

  7. Verify there are no port conflicts in the planned configuration.

    To see in-use port numbers...

    netstat -an


Windows 2003 and 2008

  1. Verify the system has a resolvable fully qualified host name. For example...

    nslookup system1.mydomain.com

    Another command to determine fully-qualified DNS name, run: "uname -n"

  2. Verify the system is DNS enabled so that there is a host name and domain present. Pure IP address environments are not supported by WebSphere Commerce.

  3. Verify the IP address on the system resolves to a host name (including a domain)...

    nslookup IP_address

    The result should be a reply with the correct fully qualified host name of the system.

  4. Verify all nodes in the configuration can be reached from other computers in the network by pinging the fully qualified host name of each node in the configuration.

  5. Verify there are no port conflicts in the planned configuration.

  6. Verify the DNS suffix has been set on each node in the planned WebSphere Commerce configuration.

    1. Select...

        Start | Control Panel | System | Computer Name | Change

    2. In the Computer Name Changes dialog box, click More.

    3. Enter the DNS suffix in the Primary DNS suffix of this computer field and click OK.

    4. In the Computer Name Changes dialog box, click OK.

    5. Click OK to exit System Properties.

    6. Reboot the machine for the change to take effect.


IBM i 6.1 and 7.1

The system must have a resolvable fully qualified host name. The fully qualified host name is the host name combined with the domain name.

For example, if the host name is system1 and the domain is mydomain.com, the fully qualified host name is system1.mydomain.com. Issuing the following command from a command prompt session should return the IP address of the system:

nslookup fully_qualified_host_name

The result should be a reply with the correct IP address of the system.

The IP address on the system must resolve to a host name (including a domain).

Another command to determine fully-qualified DNS name, run: "uname -n"

To determine if the IP address is mapped to a fully qualified host name...

nslookup IP_address

The result should be a reply with the correct fully qualified host name of the system.

Ensure that all nodes in the configuration can be reached from other computers in the network by pinging the fully qualified host name of each node in the configuration.

Ensure that we will have no port conflicts in the planned configuration.


+

Search Tips   |   Advanced Search