Configuring > Configuring DB2 server communications (TCP/IP) >
Configuring TCP/IP communications for a DB2 instance
This task describes how to configure TCP/IP communications
on your DB2® server using the DB2 Command Line Processor (CLP).
Communication protocols on the DB2 server
must be configured in order for your DB2 server
to accept inbound requests from remote DB2 clients.
Before you configure TCP/IP communications for a DB2 instance:
- Ensure that TCP/IP is functional on the DB2 server. TCP/IP must also be functional on
the DB2 client to establish
a connection.
- Identify either a Connection Service name and Connection
Port, or just a Connection Port.
- Connection Service Name and Connection Port
- The service name is used to update the Service name (svcename)
parameter in the database manager configuration file at the server.
When a Connection Service name is specified, the services file must
be updated with the same Service name, a port number, and the protocol.
The Service name is arbitrary but must be unique within the services
file. A sample value for the service name could be server1.
If you are using DB2 Enterprise
Server Edition in a partitioned format, ensure that the port number
does not conflict with the port numbers used by the Fast Communications
Manager (FCM).
The Connection port must be unique within the services
file. A sample value for the port number and protocol could be 3700/tcp.
- Connection Port
- The Service name (svcename) parameter in the database manager
configuration file at the server can be updated with a port number.
If this is the case, it is not necessary to update the services file.
If you are using DB2 Enterprise
Server Edition in a partitioned format, ensure that the port number
does not conflict with the port numbers used by the Fast Communications
Manager (FCM) or any other applications on the system. A sample value
for the port number could be 3700.
Most protocols are automatically detected and configured
when you set up DB2 using the DB2 Setup wizard. Perform the current
task if:
- You deselected the TCP/IP communication protocol when you set
up DB2 using the DB2 Setup wizard.
- You added the TCP/IP communication protocol to your network after
you set up DB2 using the DB2 Setup wizard.
- The TCP/IP communication protocol was not detected by the DB2 Setup wizard.
- You installed a DB2 product
using the db2_install command or the payload file
method.
To configure TCP/IP communications for a DB2 instance:
- Update the services file on
the server.
- Update the database manager
configuration file on the server.
- Set communication protocols
for a DB2 instance
[ Top of Page | Previous Page | Next Page | Contents ]