Connect -This product
allows DB2 clients to
access and join tables
between DB2 and other
databases, such as
DB2 Life Sciences
Data Connect -This
product allows DB2 to
support a federated
database environment and provides access to data commonly found in the Life Sciences industry, including: Excel spreadsheets, BLAST (Basic Local Aligned Search Tool), flat files, Documentum documents, and XML tagged files.
WebSphere Application Server -This Application Server is shipped with DB2 Universal Developer¡¯s Edition and allows developers to use Java as platform in a transaction processing environment.
The DB2 UDB Quick Beginnings manual for each platform provides operating system requirements for implementing DB2 distributed configurations.
DB2 Universal Database Clients
A DB2 client can be configured to establish communications with a DB2 server using various communication protocols. The supported protocols vary according to operating system:
TCP/IP -used in all environments
NetBIOS -used in Windows environments
APPC -used in IBM operating environments
Named Pipe -used in Windows environments
A DB2 client has a number of options for what client code needs to be installed, which will be depend on the requirements of the client. The options include:
DB2 Runtime Client
DB2 Administration Client
DB2 Application Development Client
DB2 Thin Client
Once a DB2 application has been developed, only the DB2 Runtime Client component needs to be installed on each workstation executing the application. Fig. 1-9 shows the relationship between the application, DB2 Runtime Client, and the DB2 database server. If the application and database are installed on the same system, the application is known as a local client. If the application is installed on a system other than the DB2 server, the application is known as a remote client.
Figure 1-9. DB2
Universal Database –
The Runtime Client provides functions other than the ability to communicate with a DB2 server or DB2 Connect server machine. For example, you can do any of the following:
Issue an interactive
SQL statement on a
remote client to access
data on a DB2 server or
DB2 Connect server.
Run applications that
were developed to
comply with the Open
(ODBC) standard or
applications that access
and manipulate data in
DB2 databases using
Connectivity (JDBC) or
If you need to graphically administer and monitor a DB2 database server, then you should install the DB2 Administration Client. It includes all the graphical DB2 administration tools in addition to all of the functionality of the DB2 Runtime Client.
If you need to develop applications, then you should install the DB2 Application Development Client. This is a collection of developer¡¯s tools that are designed to meet the needs of database application developers. The DB2 Application Development Client includes all of the graphical DB2 administration tools and the DB2 Runtime Client functionality.
The DB2 client product that you should install depends on your requirements and the operating system on the client machine. For example, if you have a database application developed for AIX, and you do not require the DB2 administration or application development tools, you should install the DB2 Runtime Client for AIX.
Some installations prefer having the DB2 Runtime Client reside remotely on another server. Remote workstations then need to access the DB2 Runtime Client code remotely, before getting access to DB2. Alternatively, DB2 can support a Java client, and with the use of the Type 4 JDBC driver, where the client code is accessed from the server. In this case, the DB2 Runtime Client code would not be required.
The DB2 Connect
product allows clients to access data stored on database servers that implement the Distributed Relational Database Architecture (DRDA). The target database server for a DB2 Connect installation is known as a DRDA Application Server.