Configure TCP/IP to run WebSphere® Application
Server on IBM® i.
Before you begin
Before you configure TCP/IP settings, ensure that your user
profile has *IOSYSCFG special authority.
About this task
Use the Configure TCP/IP menu to access options that enable
you to configure TCP/IP.
Procedure
- On a Control Language (CL) command line, enter the Configure
TCP/IP (CFGTCP) command.
- Verify that your TCP/IP address and LOOPBACK
interface are active.
- On the Configure TCP/IP menu, select option 1
(Work with TCP/IP interfaces).
- Press F11 to display the interface
status.
- Verify that the TCP/IP address is active. If it is not
active, specify option 9 (Start).
- 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.
- Press F3 to return to the Configure
TCP/IP menu.
- Verify your TCP/IP host name.
- On the Configure TCP/IP menu, select option 12
(Change TCP/IP domain information).
- 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.
- Press F3 to return to the command
line.
- 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.
- 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:
- Enter the Configure TCP/IP (CFGTCP) command
on the CL command line.
- On the Configure TCP/IP menu, select Option 10 (Work
with TCP/IP host table entries).
- Configure the IBM i system
short name to the active IP address that was listed in step 2:
- Select Option 2 (Change) and type your
IP address in the Internet address field, then press Enter.
- In the Change TCP/IP Host Table Entry (CHGTCPHTE) menu, edit the Hostnames:
Name field to match the short name of your IBM i server, then press Enter.
Important: The *ADMIN instance of the HTTP server
does not start without a host name.
- 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 IBM i 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 IBM i 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 IBM i server, you receive
an UnknownHostException message.
What to do next
Go to Configuring an HTTP server instance on IBM i to continue the installation.