9 Installing Oracle Database Gateway for Adabas

This chapter guides you through the installation procedure of Oracle Database Gateway for Adabas.

To install the gateway, follow these steps:

  1. Ensure that the system meets all of the hardware and software requirements specified in "System Requirements for Oracle Database Gateway for Adabas".

  2. Run the Oracle Universal Installer.

    See "Running the Oracle Universal Installer" for more information about running the Oracle Universal Installer.

    Oracle Universal Installer is a menu-driven utility that guides you through the installation of the gateway by prompting you with action items. The action items and the sequence in which they appear depend on your platform.

  3. Configure the gateway.

    Chapter 10, "Configuring Oracle Database Gateway for Adabas" provides information on how to configure the gateway.

9.1 Overview of Oracle Database Gateway for Adabas

Oracle Database Gateway for Adabas consists of the following components:

  • Oracle Studio for IMS, VSAM, and Adabas Gateways, a GUI-based tool that lets you configure the Oracle Servers in your system. Oracle Studio for IMS, VSAM, and Adabas Gateways runs on Windows and Linux platforms.

  • Oracle Connect for IMS, VSAM, and Adabas Gateways, which is natively located on the data server to provide standard, service-oriented integration to Adabas data. Oracle Connect for IMS, VSAM, and Adabas Gateways runs on z/OS platforms.

  • Oracle Database Gateway, which provides the capabilities, SQL mappings, data type conversions, and interface to the remote non-Oracle system. The gateway interacts with Heterogeneous Services to provide the transparent connectivity between Oracle and non-Oracle systems.

    The gateway must be installed on a Windows or UNIX computer. This can be the same system as the Oracle database server or a second, standalone system.

9.2 System Requirements for Oracle Database Gateway for Adabas

This section provides information about the hardware and software requirements for the gateway. It contains the following sections:

9.2.1 Hardware Requirements for Oracle Database Gateway for Adabas

Table 9-1 lists the hardware requirements for Oracle Database Gateway for Adabas on UNIX.

Table 9-1 Hardware Requirements for Oracle Database Gateway for Adabas

Requirement IBM AIX HP-UX 64-bit Itanium (Itanium) Sun Solaris (SPARC) 64-bit Linux x86 Linux x86 64-bit

Temporary disk space

700 MBFoot 1 

700 MB

700 MB

700 MB

700 MB

Disk space

1.5 GB

1.5 GB

750 MB

750 MB

750 MB

Physical memory

512 MB

512 MB

512 MB

512 MB

512 MB

Swap space

1 GB

1 GB

1 GB

1 GB

1 GB

Processor

IBM RS/6000 AIX-based system processor

HP chipset sx2000 processor for HP-UX 11i v2

Sun Solaris (SPARC) processor

Processor chips that adhere to the x86 32-bit architecture

Processor chips that adhere to the x86 64-bit architecture


Footnote 1 This temporary disk space requirement assumes you download the software. The temporary disk space is less than 300 MB if you install from CD or DVD media.

9.2.2 Software Requirements for Oracle Database Gateway for Adabas

Oracle Database Gateway for Adabas is supported on the UNIX operating systems specified in table Table 9-2.

Table 9-2 Software Requirements for Oracle Database Gateway for Adabas

Operating System Version

Linux x86 (32-bit)

  • Red Hat Enterprise Linux AS/ES 3.0 (Update 4 or later)

  • Red Hat Enterprise Linux 4.0

  • Enterprise Linux 4.0

Linux x86 64-bit

  • Red Hat Enterprise Linux AS/ES 3.0 (Update 4 or later)

  • Red Hat Enterprise Linux AS/ES 4.0 (Update 1 or later)

  • Enterprise Linux 4.0

Sun Solaris 64-bit

  • Solaris 9 (Update 6 or later)

  • Solaris 10

HP Itanium 64-bit

  • HP-UX 11i v2

  • HP-UX 11i v2

IBM AIX 5L 64-bit

Version 5.3, Maintenance Level 02 or later


9.3 Gateway Installation Configurations

You can install the gateway in either of the following configurations:

  • On the same computer as an existing Oracle database but in a different ORACLE_HOME directory.

  • On a system with no Oracle database.

  • On the same computer as the Oracle database and in the same ORACLE_HOME directory. Note that in this case, the Oracle database and the gateway must be at the same release level.

9.4 Gateway Installation Methods

You can choose different installation methods to install the gateway, as follows:

9.4.1 Interactive Installation Method

When you use the interactive method to install the gateway, Oracle Universal Installer displays a series of screens that enable you to specify all of the required information to install the gateway software.

9.4.2 Automated Installation Method Using Response Files

By creating a response file and specifying this file when you start Oracle Universal Installer, you can automate some or all of the gateway installation steps. These automated installation methods are useful if you need to perform multiple installations on similarly configured systems or if the system where you want to install the software does not have X Window system software installed.

When you use a response file, you can run Oracle Universal Installer in the following modes, depending on whether you specify all of the required information or not:

  • Silent Mode: Oracle Universal Installer runs in silent mode if you use a response file that specifies all required information. None of the Oracle Universal Installer screens are displayed.

  • Suppressed Mode: Oracle Universal Installer runs in suppressed mode if you do not specify all required information in the response file. Oracle Universal Installer displays only the screens that prompt for the information that you did not specify.

See Appendix A, "Using Response Files for Non-Interactive Installation" for more information about this method and about how to complete an installation using response files.

9.5 Gateway Installation Considerations

This section contains information that you should consider before installing this product. It contains the following sections:

9.5.1 Release Notes

Read the release notes for the product before installing it. The release notes are available on the Oracle Database 11g Release 2 (11.2) installation media. The latest version of the release notes is also available on the Oracle Technology Network (OTN) Web site:

http://www.oracle.com/technetwork/indexes/documentation/index.html

9.5.2 Hardware and Software Certification

The platform-specific hardware and software requirements included in this installation guide were current at the time this guide was published. However, because new platforms and operating system software versions might be certified after this guide is published, review the certification matrix on the My Oracle Support Web site for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support Web site is available at the following Web site:

https://support.oracle.com

9.5.3 Multiple ORACLE_HOME Directories

This product supports multiple ORACLE_HOME directories. This means that you can install this release or previous releases of the software more than once on the same system, in different ORACLE_HOME directories.

9.5.3.1 Installing the Software on a System with an Existing Oracle Installation

You must install this product in a new ORACLE_HOME directory. You cannot install products from one release of the gateway into an ORACLE_HOME directory of a different release.

9.6 Upgrades

Upgrades are not supported for Oracle Database Gateways.

9.7 Accessing the Installation Software

You can access and install the gateway by using the following methods:

9.7.1 Downloading Oracle Software from the Oracle Technology Network Web Site

This section describes how to download the installation files and extract them on your hard disk. It contains the following topics:

9.7.1.1 Downloading the Installation Files

To download the installation files from the Oracle Technology Network:

  1. Use any browser to access the software download page on Oracle Technology Network

    http://www.oracle.com/technetwork/index.html

  2. Navigate to the download page for the product that you want to install.

  3. On the download page, identify the required disk space by adding the file sizes for each required file.

    The file sizes are listed next to the file names.

  4. Select a file system with enough free space to store and expand the archive files.

    In most cases, the available disk space must be at least twice the size of each compressed file.

  5. On the file system that you selected in step 4, create a parent directory for each product, for example, dg4adbs, to hold the installation directories.

  6. Download all of the installation archive files to the directory that you created in step 5.

  7. Verify that the files you downloaded are the same size as the corresponding files on OTN.

9.7.1.2 Extracting the Installation Files

To extract the installation files:

  1. If necessary, change directory to the directory that contains the downloaded installation archive files.

  2. To extract each file, enter the gunzip command.

    For example:

    $ gunzip filename.cpio.gz

    This command creates files with names similar to the following:

    filename.cpio

  3. To extract the installation files, enter the cpio command.

    For example:

    $ cpio -idmv < filename.cpio

    Note:

    Refer to the download page for information about the correct options to use with the cpio command. Some browsers extract files while downloading them, but leave the .gz file extension. If these steps do not work, remove the .gz extension from the files and repeat step 3.

    For each file, this command creates a subdirectory named Diskn, where n is either 1 or the disk number identified in the file name.

9.7.2 Copying the Gateway Software to a Hard Disk

Before installing the gateway, you might want to copy the software to the hard disk. This enables the installation process to run faster. Before copying the installation media content to the hard disk, you must mount the installation media.

9.7.2.1 Mounting the Installation Media

On most Sun Solaris operating systems, the disc mounts automatically when you insert it into the disc drive. If the disc does not mount automatically, perform the following steps to mount it:

  1. Enter the following command to switch user to root:

    $ su - root

  2. If necessary, enter a command similar to one of the following to eject the currently mounted disc, then remove the disc from the drive:

    On Sun Solaris (SPARC):

    # eject

    On IBM AIX:

    # umount /cdrom

    On HP-UX Itanium:

    # /usr/sbin/umount /SD_CDROM

    In these examples, /cdrom and /SD_CDROM are the mount point directories for the disc drive.

  3. Insert the appropriate disc into the disc drive.

  4. To verify that the disc mounted automatically, enter a command similar to the following, depending on your platform:

    Sun Solaris (SPARC):

    # ls /cdrom/cdrom0

  5. If this command fails to display the contents of the disc, enter a command similar to the following to mount it, depending on your platform:

    Sun Solaris (SPARC):

    # /usr/sbin/mount -r -F hsfs /dev/dsk/cxtydzs2 /cdrom

    In this example, /cdrom is the disc mount point directory and /dev/dsk/cxtydzs2 is the device name for the disc device, for example /dev/dsk/c0t2d0s2.

  6. If Oracle Universal Installer displays the Disk Location dialog box, enter the disk mount point directory path, for example:

    /mnt/cdrom

9.7.2.2 Copying the Oracle Database Gateway Software to a Hard Disk

To copy the contents of the disc to a hard disk:

  1. Create a directory on the hard disk to hold the Oracle software:

    $ mkdir Ora10g

  2. Change directory to the directory you created in step 1:

    $ cd Ora10g

  3. Create subdirectories for each installation disc with names similar to the following, where n is the disc number:

    $ mkdir Diskn

  4. Copy the contents of the mounted disc to the corresponding new subdirectory as follows:

    $ cp -R /directory_path Diskn

    In this example, n is the disc number and /directory_path is the installation media mount point directory. The mount point directory is /cdrom.

  5. If necessary, mount the next disc and repeat step 4.

9.8 Running the Oracle Universal Installer

Start the Installer and install the software, as follows:

  1. If you are installing the software from disc, then mount the disc if it is not already mounted.

    Some platforms automatically mount discs when you insert them into the drive.

  2. If necessary, log in as the Oracle software owner user (oracle) and set the DISPLAY environment variable.

  3. To start the Installer, enter the following commands where directory_path is the CD-ROM mount point directory or the path of the dg directory on the DVD-ROM.

    directory_path/runInstaller

  4. Follow the instruction displayed in the Installer window.

    Caution:

    The Oracle Universal Installer automatically installs the Oracle-supplied version of the Java Runtime Environment (JRE). This version is required to run Oracle Universal Installer and several Oracle assistants. Do not modify the JRE except by using a patch provided by Oracle Support Services.

    Table 9-3 describes the installation procedure for Oracle Database Gateway for Adabas.

    Note:

    • When the Installer prompts you to run a script with root privileges, enter a command similar to the following in a terminal where you are logged in as the root user, then click Continue or OK:

      # /script_path/script_name

    • On Tru64 UNIX, when prompted for the JDK home directory, specify the location of JDK 1.4.2 on your system.

      To determine the JDK home directory, enter the following command:

      # /usr/sbin/setld -i JAVA142 | more

      The default location is /usr/opt/java142.

    Table 9-3 The Oracle Universal Installer: Steps for Installing the Gateway

    Screen Response

    Oracle Universal Installer: Welcome

    Click Next.

    Oracle Universal Installer: Specify Home Details

    The Path field in the Specify Home Details screen is where you specify the destination for your installation. You need not edit the path specification in the Path field. The default setting for this field points to ORACLE_HOME. After you set the fields in the Specify Home Details screen as necessary, click Next to continue. After loading the necessary information from the installation, the Oracle Universal Installer displays the Available Products screen.

    Oracle Universal Installer: Available Product Components

    Select Oracle Database Gateway for Adabas 12.1.0.

    Click Next.

    Oracle Database Gateway for Adabas

    Oracle Connect for IMS, VSAM, and Adabas Gateways Host Name: Specify the host name of the system running Oracle Connect for IMS, VSAM, and Adabas Gateways on z/OS.

    Oracle Connect for IMS, VSAM, and Adabas Gateways Port number: Specify the port number Oracle Connect for IMS, VSAM, and Adabas Gateways listens on.Click Next to continue.

    Oracle Universal Installer: Summary

    The Installation Summary screen enables you to review a tree list of options and components for this installation.

    Click Install to display the Installation Status screen.

    Oracle Net Configuration Assistant: Welcome

    Click Cancel.

    Oracle Net Configuration Assistant:

    Click Yes.

    Oracle Universal Installer: Configuration Tools

    When Oracle Universal Installer confirms that the installation is complete, verify that the installation procedure was successful. To do this, read the contents of the installation log file, which is located in the following directory:

    [designated_inventory_location]\OraInventory\logs

    The default file name is InstallActionsYYYY-MM-DD_HH-mm-SS-AM/PM.log, where:

    YYYY is year

    MM is month

    DD is day

    HH is hour

    mm is minute

    SS is seconds

    AM/PM is daytime or evening

    Each of these variables in the log file name represents the date and time the product was installed.

    When you finish configuring, click Exit.

    Exit

    Click Exit.


    If you need additional information, click Help.

    If you encounter errors while installing or linking the software, then see Appendix B for information about troubleshooting.