| Oracle Procedural Gateway® for APPC Installation and Configuration Guide 10g Release 1 (10.1) for Microsoft Windows Part Number B13694-01 |
|
|
View PDF |
| Oracle Procedural Gateway® for APPC Installation and Configuration Guide 10g Release 1 (10.1) for Microsoft Windows Part Number B13694-01 |
|
|
View PDF |
This chapter outlines the steps needed to configure the Oracle Integrating Server for a gateway using TCP/IP for IMS Connect on your Microsoft Windows platform. It also provides the steps necessary to verify installation and configuration of the gateway and OLTP components. It contains the following sections:
Configuring the Oracle Procedural Gateway for APPC using TCP/IP support for IMS Connect involves working with the following components:
the Oracle Integrating Server
your Windows system
your network
the OLTP
This chapter requires you to input parameters unique to your system in order to properly configure the gateway and TCP/IP communications interface.
Refer to Appendix E, " Configuration Worksheet" for a worksheet listing the installation parameters you will need to know before you can complete the configuration process. Ask your network administrator to provide you with these unique parameter names before you begin.
There are three ways to establish the gateway-Oracle Integrating Server relationship when you are installing or upgrading/migrating the gateway:
Depending upon the location of your gateway and your Oracle Integrating Server, you may need to transfer some of the gateway administrative files to the location where your Oracle Integrating Server is installed.
Follow the instructions appropriate to your combination of the gateway-Oracle Integrating Server locations listed below.
You do not need to transfer files. Proceed to "Configuring the Oracle Integrating Server ".
Locate the gateway administrative files in the gateway %ORACLE_HOME%\pg4appc\admin directory. All files in this directory that have the suffix .sql, .pkh, and .pkb must be copied into a similarly-named directory in the Oracle Integrating Server's Oracle home directory.
Now locate the gateway demo files and subdirectories in the gateway %ORACLE_HOME%\pg4appc\demo directory. Copy the pgavsn.sql and pgaecho.sql files into a similarly named directory in the Oracle Integrating Server.
Copy the pgaims.sql file from the gateway Oracle home %ORACLE_HOME%\pg4appc\demo\IMS directory to your Oracle Integrating Server's Oracle home %ORACLE_HOME%\pg4appc\demo\IMS directory.
Optional Steps: If you want to run IVTNV and IVTNO, you will need to copy the ivtno.ctl, ivtnod.sql, ivtnv.ctl and ivtnvd.sql files into the Oracle Integrating Server's Oracle home %ORACLE_HOME%\pg4appc\demo\IMS directory as well. Make sure to generate the required TIPs and transfer them as well.
You must change your gateway's Oracle home to the Oracle Integrating Server's Oracle home directory.
For example, if your gateway's Oracle home is set as follows:
C:\> echo\%ORACLE_HOME% C:\oracle\pga\10.0
and your server's Oracle home is located in the '\oracle\pga\10.0' directory, then you need to do the following:
C:\> SET ORACLE_HOME=C:\oracle\pga\10.0
Now create the directories with the following commands:
C:\> cd %ORACLE_HOME% C:\> mkdir pg4appc C:\> mkdir pg4appc\admin C:\> mkdir pg4appc\demo C:\> mkdir pg4appc\demo\IMS
Use whatever file transfer mechanism is available on your system to copy all of the .sql, .pkh, and .pkb files from the gateway's Oracle home %ORACLE_HOME%\pg4appc\admin directory to the Oracle Integrating Server's Oracle home %ORACLE_HOME%\pg4appc\admin directory.
You may also transfer the demo files from the gateway directory to the Oracle Integrating Server directory. Copy the pgavsn.sql and pgaecho.sql files and directory recursively from the gateway Oracle home's %ORACLE_HOME%\pg4appc\demo directory to the Oracle Integrating Server's %ORACLE_HOME%\pg4appc\demo directory.
You may also copy the pgaims.sql file from the gateway Oracle home %ORACLE_HOME%\pg4appc\demo\IMS directory to the Oracle Integrating Server Oracle home %ORACLE_HOME%\pg4appc\demo\IMS directory.
Optional Steps: If you want to run IVTNV and IVTNO, you will need to copy the ivtno.ctl, ivtnod.sql, ivtnv.ctl and ivtnvd.sql files into the Oracle Integrating Server's Oracle home %ORACLE_HOME%\pg4appc\demo\IMS directory as well. Make sure to generate the required TIPs and transfer them as well.
Proceed with "Configuring the Oracle Integrating Server ". Following those steps, you may want to perform the Optional Configuration Steps to Permit Multiple Users,.
Follow these steps to configure your Oracle Integrating Server after installing the Oracle Procedural Gateway for APPC.
Ensure that the UTL_RAW PL/SQL package has been installed on the Oracle Integrating Server. All PGAU-generated TIP specifications use UTL_RAW, which provides routines for manipulating raw data.
Use SQL*Plus to connect to the Oracle Integrating Server as user SYS.
From SQL*Plus, enter the following command:
SQL> DESCRIBE UTL_RAW
The DESCRIBE statement produces output on your screen. If you browse through the output, you should see some functions, including a compare function. If you do not see this output, then continue the UTL_RAW installation by performing Step d below.
If the DESCRIBE statement indicates success, then your Oracle Integrating Server has UTL_RAW installed and you can proceed to Step 2.
Use SQL*Plus to connect to the Oracle Integrating Server as SYS.
From SQL*Plus, run the utlraw.sql and prvtrawb.plb scripts in the Oracle Integrating Server %ORACLE_HOME%\rdbms\admin directory, in the following order:
C:\> cd %ORACLE_HOME%\rdbms\admin SQL> @utlraw.sql SQL> @prvtrawb.sql
Ensure that the DBMS_OUTPUT standard PL/SQL package is enabled on your Oracle Integrating Server. The sample programs and installation verification programs on the distribution media use this standard package.
If necessary, use SQL*Plus to connect to the Oracle Integrating Server as user SYS.
Enter the following command:
SQL> DESCRIBE DBMS_OUTPUT
The DESCRIBE statement produces output on your screen. If you browse through that output, you should see some functions, including a put_line function.
If you do not see this output, then you must create the DBMS_OUTPUT package. Refer to the Oracle Database Application Developer's Guide for more information about creating the DBMS_OUTPUT package. After successful installation of the DBMS_OUTPUT package, issue the DESCRIBE statement.
If the DESCRIBE statement indicates success, then your Oracle Integrating Server has DBMS_OUTPUT created, and you can proceed to Step 3.
Install the UTL_PG PL/SQL package. All PGAU-generated TIP specifications use UTL_PG, which provides routines for performing numeric conversions to and from raw data.
If necessary, use SQL*Plus to connect to the Oracle Integrating Server as user SYS.
From SQL*Plus, run the utlpg.sql and prvtpgb.plb scripts in the Oracle Integrating Server's %ORACLE_HOME%\rdbms\admin directory, in the following order:
C:\> cd %ORACLE_HOME%\rdbms\admin SQL> @utlpg.sql SQL> @prvtpgb.plb
Install the Heterogeneous Services (HS) catalogs.
If necessary, use SQL*Plus to connect to the Oracle Integrating Server as user SYS.
Enter the following command:
SQL> DESCRIBE HS_FDS_CLASS
The DESCRIBE statement produces output on your screen. If the DESCRIBE statement indicates success, then heterogeneous services catalogs have been created on your Oracle Integrating Server and you can proceed to Step 5.
If the DESCRIBE statement does not indicate success, then you must create Heterogeneous Services catalogs and you must follow Step c below:
If it is necessary to create the Heterogeneous Services catalog, enter the following command:
C:\> cd %ORACLE_HOME%\rdbms\admin SQL> @caths.sql
Create a public database link to access the Oracle Procedural Gateway for APPC:
Use SQL*Plus to connect to the Oracle Integrating Server as user SYSTEM. You can use the following SQL*Plus sample whether the Oracle Integrating Server and the gateway are on the same system or on different systems. In the following sample, pgasrv is the tns_name_entry that will be assigned to the gateway when you modify the tnsnames.ora file later in this chapter.
SQL> CREATE PUBLIC DATABASE LINK PGA USING 'PGASRV'
Create the gateway administrator user PGAADMIN and install the PG DD.
Use SQL*Plus to connect to the Oracle Integrating Server as user SYSTEM.
From SQL*Plus, run the pgacr8au.sql script in the %ORACLE_HOME%\pg4appc\admin directory. This script creates the PGAADMIN user ID.
The initial password defined for PGAADMIN is PGAADMIN. Use the ALTER USER command to change the password. For further information about password issues, refer to the Oracle Database SQL Reference.
C:\> cd %ORACLE_HOME%\pg4appc\admin SQL> @pgacr8au.sql
Use SQL*Plus to connect to the Oracle Integrating Server as user PGAADMIN.
From SQL*Plus, run the pgddcr8.sql script in the %ORACLE_HOME%\pg4appc\admin directory. This script installs the PG DD.
C:\> cd %ORACLE_HOME%\pg4appc\admin SQL> @pgddcr8.sql
From SQL*Plus, connect to the Oracle Integrating Server as user SYS.
Grant execution privileges on DBMS_PIPE to PGAADMIN:
SQL> GRANT EXECUTE ON DBMS_PIPE TO PGAADMIN
Ensure that the pg4tcpmap package has been installed on your Oracle Integrating Server. Follow Steps a through c to test for proper installation of pg4tcpmap.
Refer to "Output for pg4tcpmap Tool" in Appendix B for a sample of the output from the pg4tcpmap tool, and refer to Chapter 6 of the Oracle Procedural Gateway for APPC User's Guide for details about the commands needed to run the tool.
Use SQL*Plus to connect to the Oracle Integrating Server as user SYSTEM.
Enter the following command:
SQL> select owner, table_name from dba_tables where table_name = 'PGA_TCP_IMSC', and owner = 'PGAADMIN'; SQL> column owner format a 10 SQL> column owner format a 18 SQL> column owner format a 14 SQL> select owner, index_name, table_name from dba_indexes where index_name = 'PGA_TCP_IMSC_IND';
Both select statements must produce one row each. Following is the result for the first select statement:
TABLE_NAME OWNER ------------------------------ ------------------------------ PGA_TCP_IMSC PGAADMIN
Following is the result of the second select statement:
OWNER INDEX_NAME TABLE_NAME UNIQUENESS ---------- ------------------ -------------- --------- PGAADMIN PGA_TCP_IMSC_IND PGA_TCP_IMSC UNIQUE
If the select statements produce the above output on your screen, then you can skip Step C. If the select statement produces no output or more than one row, then the result is not the same as the output described above, and it is necessary for you to perform Step c.
From SQL*Plus, run the pgaimsc.sql script in the Oracle Integrating Server's %ORACLE_HOME%\pg4appc\admin directory:
C:\> cd %ORACLE_HOME%\pg4appc\admin SQL> @pgaimsc.sql
Install the TIP trace access PL/SQL routines. These routines require that the DBMS_PIPES standard PL/SQL package is installed and that PGAADMIN has execute privileges on it. For more information on DBMS_PIPES, refer to the Oracle Database Application Developer's Guide.
If necessary, use SQL*Plus to connect to the Oracle Integrating Server as user PGAADMIN.
From SQL*Plus, run the pgatiptr.sql script in the %ORACLE_HOME%\pg4appc\admin directory. This script creates PL/SQL routines that can be called to read and purge trace information created by PGAU-generated TIP specifications. It also creates public synonyms for these routines. The script prompts you for the necessary user IDs and passwords.
C:\> cd %ORACLE_HOME%\pg4appc\admin SQL> @pgatiptr.sql
Install the GPGLOCAL package. This package is required for compilation and execution of all PGAU-generated TIP specifications. TIP developers should be granted execute privileges on GPGLOCAL (refer to "Optional Configuration Steps to Permit Multiple Users").
Use SQL*Plus to connect to the Oracle Integrating Server as user PGAADMIN.
From SQL*Plus, run the gpglocal.pkh script in the %ORACLE_HOME%\pg4appc\admin directory. This script compiles the GPGLOCAL package specification.
C:\> cd %ORACLE_HOME%\pg4appc\admin SQL> @gpglocal.pkh
From SQL*Plus, run the gpglocal.pkb script in the %ORACLE_HOME%\pg4appc\admin directory. This script compiles the GPGLOCAL package body.
C:\> cd %ORACLE_HOME%\pg4appc\admin SQL> @gpglocal.pkb
|
Note: Recompile TIPs when changing communication protocol from SNA to TCP/IP:If you have existing TIPs that were generated previously on a gateway using the SNA protocol and you want to utilize the new TCP/IP feature, then the TIPs will have to be regenerated by PGAU with mandatory NLS_LANGUAGE and Side Profile Settings. Specify the appropriate ASCII character set in the DEFINE TRANSACTION command. This is due to the fact that the gateway assumes that the appropriate user exit in IMS Connect is being used, which would translate between the appropriate ASCII and EBCDIC character sets. |
The following configuration steps are optional. Perform these steps if you want to allow users other than PGAADMIN to perform PG DD operations using PGAU.
Create public synonyms for the PG DD to allow other users to access the tables:
Create roles for accessing the PG DD, performing definitions of transactions, and generating TIP specifications. The PGAADMIN user can grant these roles to other users as necessary.
Use SQL*Plus to connect to the Oracle Integrating Server as user PGAADMIN.
From SQL*Plus, run the pgddcr8r.sql script in the %ORACLE_HOME%\pg4appc\admin directory. This script creates two roles, PGDDDEF and PGDDGEN. The PGDDDEF role provides SELECT, INSERT, UPDATE, and DELETE privileges against some of the PG DD tables, and select privileges against others, and allows execution of the PGAU DEFINE, GENERATE, REDEFINE, REPORT, and UNDEFINE statements. The PGDDGEN role provides select privileges against the PG DD tables, and allows execution of the PGAU GENERATE and REPORT statements only.
C:\> cd %ORACLE_HOME%\pg4appc\admin SQL> @pgddcr8r.sql
Grant access to PGA required packages.
TIP developers require access to the following PL/SQL packages, which are shipped with the Oracle Integrating Server:
Explicit grants to execute these packages must be made to TIP developers.
SQL scripts for performing these grants are provided in the %ORACLE_HOME%\pg4appc\admin directory. The pgddapub.sql script performs these grants for public access to the packages. The pgddadev.sql script performs the grants for private access to the packages by a single TIP developer. If you are going to use private grants, then you must run the pgddadev.sql script once for each TIP developer's user ID:
Use SQL*Plus to connect to the Oracle Integrating Server as user PGAADMIN.
From SQL*Plus, run the appropriate script (pgddapub.sql or pgddadev.sql) from the %ORACLE_HOME%\pg4appc\admin directory. The script performs the necessary grants as described earlier. You are prompted for the required user IDs, passwords, and database specification strings. If you are using private grants, then repeat this step for each user ID requiring access to the packages.
C:\> cd %ORACLE_HOME%\pg4appc\admin SQL> @pgddapub.sql
or
SQL> @pgddadev.sql
These grants can be private, as in the following example:
C:\> sqlplus SYS\pw@database_specification_string SQL> GRANT EXECUTE ON UTL_RAW TO tip_developer; SQL> GRANT EXECUTE ON UTL_PG TO tip_developer; SQL> GRANT EXECUTE ON DBMS_PIPE TO tip_developer; SQL> CONNECT PGAADMIN\pw@database_specification_string SQL> GRANT EXECUTE ON PGAADMIN.PURGE_TRACE TO tip_developer; SQL> GRANT EXECUTE ON PGAADMIN.READ_TRACE TO tip_developer; SQL> GRANT EXECUTE ON PGAADMIN.GPGLOCAL TO tip_developer; SQL> exit
Alternatively, these grants can be public, as in the following example:
C:\> sqlplus SYS\pw@database_specification_string SQL> GRANT EXECUTE ON UTL_RAW TO PUBLIC; SQL> GRANT EXECUTE ON UTL_PG TO PUBLIC; SQL> GRANT EXECUTE ON DBMS_PIPE to PUBLIC; SQL> CONNECT PGAADMIN\pw@database_specification_string SQL> GRANT EXECUTE ON PGAADMIN.PURGE_TRACE TO PUBLIC; SQL> GRANT EXECUTE ON PGAADMIN.READ_TRACE TO PUBLIC; SQL> GRANT EXECUTE ON PGAADMIN.GPGLOCAL TO PUBLIC; SQL> EXIT
You can use either private or public grants. Both are sufficient for using PGA. Public grants are easier and can be performed now. If you use private grants, then they must be issued each time a new TIP developer user ID is created.
If you are upgrading from a previous release of the gateway when the communication protocol was SNA, to the current gateway using TCP/IP, and if you want to upgrade your existing TIPs with new function and maintenance, then regenerate existing TIP specifications using the PGAU GENERATE statement.
Invoke PGAU in the directory path where the PGAU control files are generated and where TIPs are stored:
C:\> pgau PGAU> CONNECT PGAADMIN\pgaadmin@database_specification_string PGAU> GENERATE tranname PGAU> EXIT
For more information about the GENERATE command, refer to the PGAU GENERATE command section in Chapter 2 of the Oracle Procedural Gateway for APPC User's Guide.
Note that it is not necessary to define the PG DD entries again.
Invoke SQL*Plus in the same directory path where the newly-generated TIP specifications are stored.
C:\> sqlplus tip_owner\pw@database_specification_string SQL> @tipname.pkh SQL> @tipname.pkb SQL> exit
PGAU GENERATE produces the TIP in two output files: a specification and a body. You must compile both, first the specification and then the body.
For more information about the GENERATE command, refer to the PGAU GENERATE command section in Chapter 2, of the Oracle Procedural Gateway for APPC User's Guide.
You must now configure the TCP/IP for IMS Connect communication package profiles for TCP/IP connections.
Configure the profiles to define the TCP/IP conversations with the OLTP. Refer to Chapter 7, " Configuring the TCP/IP Communications Package for IMS Connect" for the appropriate instructions.
When you have finished configuring your communications package, return to the following section, Section 10.6, "Configuring the Gateway".
To configure the gateway, perform the following:
Tailor the gateway parameters.
There are a number of parameters specific to the Oracle Procedural Gateway for APPC when it is using TCP/IP for IMS Connect. These are supplied in the gateway parameter file, initsid.ora, which is in the %ORACLE_HOME%\pg4appc\admin directory. A sample gateway parameter file, initPGA.ora is provided in this subdirectory.
|
Note: In the initsid.ora file, substitute your gateway SID name for "sid " in this file name.
The initsid.ora file contains both APPC and TCP/IP parameters, separated by a description. You must modify the initsid.ora file by deleting the APPC parameters. Refer to Appendix B, " Gateway Initialization Parameters for TCP/IP Communication Protocol " for the valid TCP/IP parameters. |
The parameters fall into two categories:
gateway initialization parameters.
These parameters control the general operation of the gateway in the Oracle environment.
|
Important: Before performing the following step, refer to Appendix B, " Gateway Initialization Parameters for TCP/IP Communication Protocol " for information about tailoring gateway initialization and PGA parameters. Pay special attention to the information about using the PGA_CAPABILITY parameter. |
PGA parameters control the TCP/IP interface portion of the gateway. Use the SET gateway initialization parameter to specify PGA parameters. Oracle recommends that you group all SET commands for PGA parameters at the end of the initsid.ora file.
Gateway users who wish to employ the TCP/IP protocol do so by using the pg4tcpmap tool.
The pg4tcpmap tool resides on the gateway. Its function is to map the Side Profile Name to TCP/IP and IMS Connect attributes. You must run this tool before executing the PL/SQL gateway statements (such as %ORACLE_HOME%\pg4appc\demo\IMS\pgaims.sql).
In PGAINIT TIP, for example, the user must specify a Side Profile Name. The SNA protocol recognizes and utilizes the parameter. In this release of the gateway, the pg4tcpmap tool uses the original PGAINIT TIP format to map the relevant SNA parameters to TCP/IP. The pg4tcpmap tool inserts the values of these parameters into a table called PGA_TCP_IMSC.
Before executing pg4tcpmap, you must specify the ORACLE_HOME, Oracle SID and modify initsid.ora. Refer to Appendix B, " Gateway Initialization Parameters for TCP/IP Communication Protocol " in this guide and Chapter 6 in the Oracle Procedural Gateway for APPC User's Guide for complete information about the pg4tcpmap commands.
Chapter 6 of the Oracle Procedural Gateway for APPC User's Guide contains a list of the pg4tcpmap commands and instructions for using them, as well as a example of the table. Refer to "Problem Determination" in the Oracle Procedural Gateway for APPC User's Guide for information about the trace file for the executed pg4tcpmap tool.
To operate this tool execute the following command:
C:\> cd %ORACLE_HOME%\bin C:\> pg4tcpmap
Refer to "Output for pg4tcpmap Tool" for a sample of the pg4tcpmap output.
To verify the gateway installation and the OLTP configuration, perform the following procedures after installing the gateway.
|
Note: If your database link name is not "PGA," modify the demonstration .sql files to give them the particular database link name that you created in Step 5 of "Configuring the Oracle Integrating Server ". You must modify the following .sql files: |
To verify the gateway software installation using the database link PGA previously created, perform the following steps:
Using SQL*Plus, connect to your Oracle Integrating Server as user PGAADMIN.
Run %ORACLE_HOME%\pg4appc\demo\pgavsn.sql.
C:\> cd %ORACLE_HOME%\pg4appc\demo SQL> @pgavsn.sql
The server version number banner appears at your terminal. You will receive the following output:
Oracle Procedural Gateway for APPC (extension TCP/IP for IMS Connect). Version 10.0.1.2.0 Thu Feb 13 13:12:49 2003 Copyright (c) Oracle Corporation 1979, 2003. All rights reserved.
PL/SQL procedure successfully completed.
Run %ORACLE_HOME%\pg4appc\demo\pgaecho.sql.
C:\> cd %ORACLE_HOME%\pg4appc\demo SQL> @pgaecho.sql
You will receive the following output:
==> Congratulations, your installation was successful. <==
Use the following procedure to verify your OLTP configuration.
|
Attention: If you have not completed the file transfers detailed in "Preparing to Configure a Gateway Installation ", complete them now, before proceeding to the next step. |
Perform the following steps to verify the IMS/TM configuration. Be certain that you have installed and configured the IMS Connect and that it is up and running before you begin this procedure. Refer to the IBM IMS Connect Guide and Reference for information about how to perform the installation and configuration tasks.
To verify that the FLIP transaction is installed correctly, log on to your IMS/TM system and enter the following transaction (replacing FLIP with the transaction ID you chose for FLIP when you configured your IMS/TM system for the gateway):
FLIP THIS MESSAGE
The following output appears on your terminal:
EGASSEM SIHT PILF
|
Attention: If you have not completed the file transfers detailed in Section 10.2 "Preparing to Configure a Gateway Installation ", complete them now, before proceeding to the next step. |
From your Windows platform, modify the pgaims.sql file, which resides at %ORACLE_HOME%\pg4appc\demo\IMS\pgaims.sql. Customize the following three items used for accessing the gateway and the IMS/TM system, as described in the comments at the beginning of the file:
the IMS/TM transaction ID
the side profile name
the logmode entry name
Ensure that the TCP/IP communication protocol on your system has been started.
Using SQL*Plus, connect to your Oracle Integrating Server from PGAADMIN.
C:\> cd %ORACLE_HOME%\pg4appc\demo\IMS SQL> @pgaims.sql
The following message appears:
==> Congratulations, your gateway is communicating with IMS/TM <==
Your IMS/TM installation verification is now complete.
The following are optional steps that you can perform as necessary. Installation of the sample applications for your OLTP is recommended to help you to fully understand how the gateway works and how it interfaces with your OLTP.
Your Oracle Procedural Gateway for APPC featuring TCP/IP for IMS Connect contains sample PL/SQL procedures and OLTP transaction programs that demonstrate the gateway's capabilities.
|
Note: When you are calling a gateway that is using TCP/IP as the communication protocol, and you are using EBCDIC as the language in the control files, then you must change the language from EBCDIC to ASCII. Some examples of control files that may be in EBCDIC language are ivtno.ctl and ivtnv.ctl.For more information, refer to the %ORACLE_HOME%\pg4appc\demo\IMS\ivtno.ctl and %ORACLE_HOME%\pg4appc\demo\IMS\ivtnv.ctl files. |
Samples are provided for IMS/TM:
IMS inquiry using IVTNO and IVTNV sample transactions
Additional samples are added to the distribution media in later releases of the product. Wherever possible, the sample applications use the sample databases provided with the database products.
For this release, full documentation on installing and using the sample applications is available in the README.doc files in the following directory:
%ORACLE_HOME%\pg4appc\demo\IMS
