LOTUS CONNECTORS


Connectivity to DB2 on i5/OS
This section describes connectivity considerations between DB2 on a Windows workstation and DB2 Universal Database for iSeries (DB2 UDB for iSeries). None of the options described require the installation of software to the i5/OS.

When connecting to a DB2 UDB for iSeries server remotely, you must use DB2 Connect in order to specify i5/OS as the target DB2 database. The UDB Editions do not allow you to specify the target database operating system.

DB2 UDB for iSeries is part of the base operating system on the i5/OS and has support to be both a requester and server of remote DB2 requests. DB2 UDB for iSeries can be the target of DB2 connection requests from platforms such as NT, AIX, etc. It can also request DB2 connections to other DB2 databases in the network. DB2 UDB for iSeries supports both SNA and TCP/IP connections. See the "Connecting to Remote DB2 from i5/OS" section for more details.

Because DB2 UDB for iSeries is part of the base operating system, if you are running LEI native on the i5/OS you do not need to install additional DB2 software on the i5/OS. All DB2 databases being connected to, including the local DB2 UDB for iSeries database, must be registered in the Relational Database Directory (see WRKRDBDIRE).

You can also connect to DB2 on an i5/OS or mainframe using DDCS gateway.

Connecting to a DB2 Data Source on i5/OS

All connections originating from the i5/OS to DB2 databases (including the local DB2 UDB for iSeries), require that the target DB2 database be registered in the Relational Database Directory on the requesting i5/OS. Register DB2 data sources using the WRKRDBDIRE CL command. You can register your remote connections as either *SNA or *IP. If using SNA, communication configuration is required to connect to the remote database as described in the appropriate i5/OS documentation. If using *IP, provide the target IP address or remote location name and verify that the target database is active on the designated port. The default IP port for *DRDA is 446.

If the target database is another DB2 UDB for iSeries using a *IP connection, make sure that the DDM server job on the target i5/OS is listening for the connection request. This occurs by entering a STRTCPSVR *DDM command on the target i5/OS. The command starts the QRWTLSTN job on the i5/OS in QSYSWRK subsystem. This job monitors the DRDA port.

Note If you are connecting to a remote DB2 UDB for iSeries, the password in the Connection Document should be in uppercase characters.

Direct DB2 UDB for iSeries Connectivity

This section describes direct DB2 UDB for iSeries connectivity considerations.

One Server Connecting to DB2 UDB for iSeries
This configuration does not require the installation of software to the i5/OS system.

You can use an *IP connection. If you are using SNA as your connection protocol, bundled with Connect Personal Edition is an SNA server. Install the SNA server with the SNA over APPC option. It must be over APPC; i5/OS requires APPC for DB2 connectivity when using an SNA connection. Also, in this stand-alone environment, the SNA over APPC is self-sufficient; there is no general network need for APPC and SNA in the network.

Refer to the IBM DB2 Connect Personal Edition Quick Beginnings document (numbered S10J-8162-00) as a means to begin the installation. Use a user name and password that exist also on the DB2 UDB for iSeries. This will allow the installation to perform operations on the system without intervention.

Multiple Servers Connecting to DB2 UDB for iSeries
This configuration does not require any software installed to the i5/OS system.

This will install a gateway to DB2 UDB for iSeries. A gateway allows access to the DB2 UDB for iSeries data from multiple servers. This software is only necessary if you plan to have more than one server.

You can use an *IP connection. If using SNA as your connection protocol, the Connect Enterprise Edition does not come with bundled SNA software. You must install an SNA server, such as the Microsoft SNA server.

If the DB2 Connect Enterprise Edition is not installed on the machine, then a DB2 client such as DB2 Administration Client needs to be installed on the machine. This client is needed to perform the direct connection from the Domino server to DB2.

Server Connecting to DB2 UDB for iSeries with DDCS
A Distributed Database Connection Services (DDCS) and SNA server are required.

This configuration does not require the installation of software to the i5/OS system.

This configuration is for customers with an existing DDCS installation. This option only exists for customers who have DDCS already in house, because at this time only the latest DB2 Connect versions 6.1 and 7.1 software is available for purchase.

DDCS Single User or Gateway can be used to connect to DB2 UDB for iSeries. With DDCS, there is also a requirement for an SNA server over APPC. Therefore, you need SNA software such as Microsoft SNA.

If DDCS is not installed on the server machine, a DB2 Client such as DB2 Administration client must be installed on the server machine. This client is needed to perform the direct connection from the server to DB2 UDB for iSeries.