10 Configuring the Gateway

Enter the SID on the Worksheet

Enter the SID in Appendix E, "Configuration Worksheet".

A separate SID is required for each DRDA Server to be accessed. You might also have multiple SIDs for one DRDA Server to use different gateway parameter settings with that server. For information on configuring additional SIDs, refer to "Accessing Other DRDA Servers".

Step 1: Copy the gateway initialization

Sample gateway initialization files (initsid.ora) are shipped on the distribution CDEROM. These files are in the ORACLE_HOME\tg4drda\admin directory:

• initDB2.ora, for DB2/OS390 remote servers

• initDB2VM.ora, for DB2/VM remote servers

• initAS400.ora, for DB2/400 remote servers

• initDB2UDB.ora, for DB2/UDB remote servers

Copy one of these sample files into the same directory, renaming it with the name of your gateway SID. For example, if you chose your SID to be DRD1 in "Choosing a Gateway System Identifier (SID)", and if your remote server is DB2, then copy the initDB2.ora file and rename it initDRD1.ora.

Step 2: Determine settings for gateway initialization parameters

Your Configuration Worksheet in Appendix E should be complete. If not, review the incomplete entries and refer to the sections listed for more information. You need this information to tailor the gateway initialization file, initsid.ora.

Refer to Appendix C, "DRDAESpecific Parameters" for information on the DRDAEspecific initsid.ora parameters.

Step 3: Tailor the initsid.ora File

After you have copied the sample initialization file, you will need to tailor it to your installation. While many parameters can be left to their defaults, some parameters must be changed for correct operation of the gateway. Give attention to the following DRDA and HS parameters. Also, give attention to the security aspects of the initialization file. Chapter 13, "Security Considerations", contains details on encryption of passwords that would otherwise be embedded in the initialization file. See Appendix C for a description of each parameter:

• DRDA_CONNECT_PARM

• DRDA_PACKAGE_COLLID

• DRDA_PACKAGE_NAME

• DRDA_PACKAGE_OWNER

• DRDA_REMOTE_DB_NAME

• FDS_CLASS

• HS_DB_NAME

• HS_DB_DOMAIN

Binding the DRDA Gateway Package

The product requires a package to be bound on the DRDA Server. The gateway has an internal, stored procedure that must be used to create this package. The internal stored procedure is called from an Oracle integrating server. (Refer to "Configuring Oracle Net" of Chapter 9, "Oracle Net". Also refer to "Configuring the Oracle Integrating Server" of this chapter.) Before this package can be bound on the DRDA Server, the gateway initialization file must be correctly configured. Refer to Appendix C.

1. Log on to an Oracle integrating server

   Use either SQL*Plus or Server Manager:

   > sqlplus system/manager
   

2. Create a database link

   Create a database link with a user ID and with a password that has proper authority on the DRDA Server to create packages.

   SQL> CREATE PUBLIC DATABASE LINK dblink
   2 CONNECT TO userid IDENTIFIED BY password 
   3 USING 'tns_name_entry' 
   

   Note:

   The user ID that is creating the public database link must have the "CREATE PUBLIC DATABASE LINK" privilege.

   Refer to "Configuring the Oracle Integrating Server" later in this chapter.

3. Run the stored procedure GTW$_BIND_PKG

   SQL> exec GTW$_BIND_PKG@dblink; 
   SQL> COMMIT;
   

   This creates and commits the package. If any errors are reported, then correct the gateway initialization file parameters as needed.

Binding Packages on DB2/Universal Database (DB2/UDB)

If you are connecting to a DB2/UDB DRDA Server, then DB2/UDB requires that you create the ORACLE2PC table before binding the DRDA package. Other DRDA Servers enable you to bind the package before the ORACLE2PC table exists.

To create the ORACLE2PC table:

1. Log in to the system where DB2/UDB is running.

   Check that you have the ability to address the DB2/UDB instance where the ORACLE2PC table will reside.

2. Copy the following files.

   Copy from the ORACLE_HOME\tg4drda\install\db2udb directory:

   • o2pc.sql  (SQL script for creating the table)

   • o2pcg.sql (SQL script for granting package access to PUBLIC)

3. Connect to the database.

   Use the user ID that you will use for binding the package:

   $ db2 'CONNECT TO database USER userid USING password'
   

   Note:

   The user ID must have CONNECT, CREATETAB, and BINDADD authority to be able to connect to the database, to create the table, and to create the package.

   For more information, refer to "DB2/UDB (Universal Database)".

4. Create the ORACLE2PC table:

   $ db2 -tf o2pc.sql
   

5. Commit the transaction:

   $ db2 'COMMIT'
   

6. Optionally, verify that the table was created under the correct user ID:

   $ db2 'LIST TABLES FOR USER'
   $ db2 'COMMIT'
   

7. Disconnect from the session:

   $ db2 'DISCONNECT CURRENT'
   

Before Binding the DRDA Gateway Package

Check DRDA parameter settings and create your ORACLE2PC table before binding the DRDA gateway package.

Sample SQL scripts

SQL scripts are provided to perform steps such as creating the ORACLE2PC table, removing obsolete tables and views, using previous releases, and creating tables and views to provide data dictionary support. Use the correct subdirectory for your DRDA Server platform:

tg4drda\install\db2 for DB2/OS390

tg4drda\install\as400 for DB2/400

tg4drda\install\db2vm for DB2/VM

tg4drda\install\db2udb for DB2/UDB

These scripts must be run on the DRDA Server platform using a database native tool (such as SPUFI on DB2/OS390), because no tool is provided with the gateway to run these scripts. Note that when running these scripts, the user ID used must be suitably authorized.

Step 1: Create a database link

To access the DRDA Server, you must create a public database link. A public database link is the most common of database links. Refer to "Processing a Database Link" for information about creating database links. In the following example, the Oracle Database server and the gateway are on the same host.

CREATE PUBLIC DATABASE LINK DB2 USING 'tns_name_entry'

Step 2: Create synonyms and views

To facilitate accessing data using the gateway, define synonyms and views for the DRDA data tables. If needed, then perform GRANT statements to ensure that the synonyms and views are accessible to the correct groups of users. For more information, refer to "Using the Synonym Feature".