|Oracle® Database Gateway for APPC Installation and Configuration Guide
11g Release 1 (11.1) for AIX 5L Based Systems (64-Bit), HP-UX PA-RISC (64-Bit), Solaris Operating System (SPARC 64-Bit), and Linux x86
|PDF · Mobi · ePub|
The hardware requirements for this release of the gateway on your platform are described in the following sections:
Refer to the Oracle Database Installation Guide and to the certification matrix on the OracleMetaLink for the most up-to-date list of certified hardware platforms and operating system version requirements to operate the gateway for your Linux, AIX-Based, HP-UX, or Solaris system. The OracleMetaLink Web site is available at:
The gateway processor requirements for your platform are as follows:
For Linux 32-bit: Intel Pentium-based processors
For AIX-Based Systems: IBM pSeries
For HP-UX: HP 9000 Series HP-UX that can run the required version of HP-UX
For Solaris: A Solaris Operating System (SPARC 64-bit) that can run the required version of Solaris with 64-bit architecture
For most installations, Oracle recommends a minimum of 256 MB of real memory for the system running the Oracle Database Gateway for APPC.
Number of concurrent gateway connections open by each user
Number of data items being transferred between the gateway and the remote transaction program
The Oracle Net protocol adapters that were included during the gateway installation
Additional factors, such as configured network buffer size
However, if you are using only the new TCP/IP support for IMS Connect feature, you will not need an SNA package. Your operating system comes with TCP/IP installed.
A CD-ROM drive is required for installation of the software.
Table 3-1 lists the disk space requirements for each platform:
The system software configuration described in this section is supported by Oracle, provided that the underlying system software products are supported by their respective vendors. Verify the latest support status with your system software vendors.
This section contains the following topics:
Refer to the Oracle Database Installation Guide and to the certification matrix on the OracleMetaLink for the most up-to-date list of certified operating system version requirements to operate the gateway for your Linux for Intel Pentium-based 32-bit systems, AIX-Based, HP-UX or Solaris system. The OracleMetaLink Web site is available at
Each operating system uses specific communications servers, as described in this section.
Note:If you choose to use TCP/IP support for IMS Connect as communication protocol, then you do not need to use an SNA communication package from the following list. Each operating system comes with a TCP/IP protocol automatically installed. If you choose to use the TCP/IP protocol, then you need to configure it to work properly with the gateway. Refer to Chapter 13, "Gateway Configuration Using TCP/IP Communication Protocol".
Communications protocols for Linux for Intel Pentium-based 32-bit System IBM Communications Server V126.96.36.199 for Linux or higher, or the TCP/IP communication software that comes with your operating system.
SNA Server for AIX version 6.01 or higher, or the TCP/IP communications software that comes with your operating system.
Oracle Net is automatically installed on the system where Oracle database is installed and on the system where the gateway is installed. Refer to Chapter 5, "Configuring Your Oracle Network" in this guide for detailed configuration information. Additionally, you might refer to the Oracle Database Net Services Administrator's Guide.
In addition to the other software requirements of the gateway and the platform being used, the following list outlines other requirements necessary on the IBM mainframe:
OLTP for SNA
The OLTP must support mapped APPC conversations. If the OLTP transaction programs to be executed through the gateway perform database updates, then the APPC verbs
SEND_ERR must be supported by the OLTP. These verbs implement APPC
All resources controlled by an OLTP that can be updated by transaction programs invoked through the gateway must be defined as recoverable resources to the OLTP and host system if
ROLLBACK capability is required for those resources. For example, a VSAM file updated by a CICS transaction must be defined to CICS as a recoverable file for
ROLLBACK to control the updates.
Note:For a list of known restrictions, read the "Known Restrictions" section before proceeding with the installation of the gateway.