Configuring DB2 Clients in a Three-Tier Environment
In this environment, the clients connect to a gateway with DB2 Connect Enterprise Edition installed. The gateway serves as a DRDA application requester to the host. In our example, we used the workstation of CLIENT1, with only the client application enabler installed, to connect to the host via the DB2 connect gateway of SERVER1.
Configure the Host
Refer to the Configure TCP/IP for DB2 UDB for OS/390 from the above section.
Configure DB2 Connect Gateway to Accept Incoming Clients
To accept incoming clients, the necessary protocols have to be started first. Normally, you configure these protocols with the installation of DB2 Connect. The most common protocol used is TCP/IP, so we document only the usage of TCP/IP between the client and the server. Protocols are started during the start of DB2. The following are automatically configured (if, during installation of DB2 Connect, you configured TCP/IP) for you to accept incoming clients.
You can always configure TCP/IP after installation of DB2 Connect by doing the following:
Configure the DB2 Client
From the DB2 client, you can use the Client Configuration Assistant or the command line processor to configure your access to the DB2 host subsystem: