Configure TCP/IP

Configure TCP/IP to run WebSphere Application Server on iSeries. Before you configure TCP/IP settings, ensure that your user profile has *IOSYSCFG special authority.

Overview

Procedure

1. On a Control Language (CL) command line, enter the Configure TCP/IP (CFGTCP) command.

2. Verify that your TCP/IP address and LOOPBACK interface are active.

   1. On the Configure TCP/IP menu, select option 1 (Work with TCP/IP interfaces).

   2. Press F11 to display the interface status.

   3. Verify that the TCP/IP address is active. If it is not active, specify option 9 (Start).

   4. Verify that the LOOPBACK interface at IP address 127.0.0.1 is active.

      If 127.0.0.1 is not active, specify option 9 (Start) next to the entry with IP address 127.0.0.1, then press Enter.

   5. Press F3 to return to the Configure TCP/IP menu.

3. Verify your TCP/IP host name.

   1. On the Configure TCP/IP menu, select option 12 (Change TCP/IP domain information).

   2. Verify that the TCP/IP host name is correct.

      If the host name is not correct, type the correct host name in the Host name field, then press Enter. If the host name is correct, press F3 to return to the Configure TCP/IP menu.

      The host name cannot be *NONE.

   3. Press F3 to return to the command line.

4. Start TCP/IP.

   If TCP/IP is not started or if you do not know if TCP/IP is started, enter the Start TCP/IP (STRTCP) command on the CL command line.

5. Verify that the server IP address is associated with the host name.

   Issue the following command on the CL command line:

   ping host_name

   The following sample output is from a successful ping command:

   Verifying connection to host system MYSYSTEM.MYCOMPANY.COM at address
       1.2.3.4.
     PING reply 1 from 1.2.3.4 took 0 ms. 256 bytes. TTL 64.
     PING reply 2 from 1.2.3.4 took 0 ms. 256 bytes. TTL 64.
     PING reply 3 from 1.2.3.4 took 0 ms. 256 bytes. TTL 64.
     PING reply 4 from 1.2.3.4 took 0 ms. 256 bytes. TTL 64.
     PING reply 5 from 1.2.3.4 took 0 ms. 256 bytes. TTL 64.
     Round-trip (in milliseconds) min/avg/max = 0/0/0
     Connection verification statistics: 5 of 5 successful (100 %).

   If the ping fails, follow these steps:

   1. Enter the Configure TCP/IP (CFGTCP) command on the CL command line.

   2. On the Configure TCP/IP menu, select Option 10 (Work with TCP/IP host table entries).

   3. Configure the iSeries system short name to the active IP address that was listed in step 2:

      1. Select Option 2 (Change) and type your IP address in the Internet address field, then press Enter.

      2. In the Change TCP/IP Host Table Entry (CHGTCPHTE) menu, edit the Hostnames: Name field to match the short name of your iSeries server, then press Enter.

   The *ADMIN instance of the HTTP server does not start without a host name.

6. Verify your system configuration.

   The IPTest Java utility is shipped with the WebSphere Application Server product and can be used to debug TCP/IP configuration problems. To run this utility, run the IPTest command from the QShell command line. The command file is in the app_server_root/bin directory:

   app_server_root/bin/IPTest 

Results

If TCP/IP has been configured successfully, the IPTest command output resembles the following example:

Local Address: 12.34.56.78
Local Name: MYSYSTEM.MYCOMPANY.COM
All addresses for MYSYSTEM.MYCOMPANY.COM:
12.34.56.78

The Local Address is the IP address for your iSeries server. This value must not be blank and must match the IP address verified in step 2. The Local Name is the domain-qualified host name for your iSeries server. If this value is blank, see the instructions in step 2. Press F3 to exit.

If a host name has not been configured for your iSeries server, you receive an UnknownHostException message.

What to do next

Related tasks