Preparing to Install the Oracle Tuxedo Mainframe Adapter for SNA

The following sections provide information that you need to know before installing the Oracle Tuxedo Mainframe Adapter for SNA 12c Release 2 (12.2.2) product software:

•	Oracle Universal Installer (OUI)

•	Determining Your Configuration

•	Oracle Tuxedo Mainframe Adapter for SNA Components

•	Hardware and Software Prerequisites

•	Installing the Prerequisite Software

•	Oracle Installation Program

•	Installation Road Map

Oracle Universal Installer (OUI)

The Oracle Tuxedo Mainframe Adapter for SNA 12c Release 2 (12.2.2) product software installer is based on the Oracle Universal Installer (OUI). To install the Oracle Tuxedo Mainframe Adapter for SNA 12c Release 2 (12.2.2) product software on your host, you must know how to use OUI to install Oracle products. For more information, see Introduction to Oracle Universal Installer.

Modes of Installation

You can use OUI to install Oracle products in any of the three following modes:

•	Interactive:

Use OUI interactive mode to use the graphical user interface to walk through the installation, providing information in the installation dialogs when prompted. This method is most useful when installing a small number of products in different setups on a small number of hosts.

•

Silent:

Use OUI silent installation mode to bypass the graphical user interface and supply the necessary information in a response file. This method is most useful when installing the same product multiple times on multiple hosts. By using a response file, you can automate the installation of a product for which you know the installation parameters.

Installation Media

Note:

When you invoke runInstaller.sh (UNIX), you should invoke it from the directory where this command is present, or you must specify the complete path to runInstaller.sh (UNIX).

Special Instructions for UNIX Users

The following sections describe special instructions that apply when you are installing certain products on a UNIX system.

Failed to Connect to Server Error

If you receive an Xlib error or a "Failed to connect to Server" error when you are running OUI on the Solaris operating system, do the following:

1.	Define the following environment variable on the host computer where you are running OUI:

%setenv DISPLAY <machine name>:0.0

2.	Replace <machine name> with the name of the computer that will display OUI.

3.	On the computer that will display OUI, enter the following command, which allows other computers to display information on the computer monitor: %xhost +

4.	Rerun the runInstaller.sh script after you have set the DISPLAY environment variable.

Note:

You can run OUI without specifying the DISPLAY variable by running in silent mode using a response file.

Providing a UNIX Installer Location with Root Privileges

You must have root privileges to perform various UNIX installation operations. For example, you must have root privileges to be able to create the OUI inventory.

If you are installing OUI for the first time, you are prompted to run a shell script from another terminal window before proceeding with the installation. OUI prompts you to run root.sh after installation completes only if the script is required to run as root before configuration assistants are run. Otherwise, you are prompted to run root.sh as root later.

Note:

When running OUI in silent mode, if root.sh is required prior to configuration assistants, OUI skips configuration assistants during the installation. You must run root.sh as root and then run the skipped configuration assistants after the silent installation is complete.

To successfully run the required shell script:

1.	Leave the OUI window open and open another terminal window.

2.	In the new terminal window, use the substitute user command to log in with root privileges: su -root

3.	Change directory to the Oracle home into which you are currently installing your Oracle software product.

4.	Run the shell script ./root.sh.

5.	When the script is finished and you are returned to the command prompt, exit from the new terminal window and return to OUI to continue installation.

Note:

Do not exit the installation to run the shell script. Exiting the installation removes this script.

You are prompted to run the script only the first time you install.

Providing a UNIX Group Name

If you are installing a product on a UNIX system, the Installer also prompts you to provide the name of the group that owns the base directory.

You must choose a UNIX group name that has permissions to update, install, and remove Oracle software. Members of this group must have write permissions for the chosen base directory.

Only users who belong to this group are able to install or remove software on this host.

About Oracle Universal Installer Log Files

When you install or deinstall products using OUI, important information about each installation is saved not only in the inventory, but also in a series of log files, located in the following directory:

$ORACLE_HOME/cfgtoollogs

You can use these log files to troubleshoot installation problems. These files are also crucial for removing and configuring the various software components you install on your UNIX computer. OUI displays the name and location of the current session log file on the Install page. Each installation or configuration utility provides a separate folder containing the logs inside the $ORACLE_HOME/cfgtoollogs folder.

Note:

The logs used to remove products are different from the installActions<timestamp>.log generated during the install process. The installActions<timestamp>.log is easier to read and can be used to view the operations performed at installation time.

Oracle Internationalization

Installation Dialogs Language

OUI runs in the operating system language. OUI uses the language that Java detects, the system locale value, and sets that to the default language. OUI dialogs are displayed in this language if available. If specific OUI dialogs are not translated in the language of the operating system, these dialogs are shown in English.

OUI displays the translated GUI only if the variable NLS_ENABLED has been set to TRUE in the oraparam.ini file. If the NLS_ENABLED variable is set to FALSE, all text is shown in English.

Note:

The dialogs displayed for internationalization can only be customized parts; some of them are embedded in OUI.

Determining Your Configuration

You must consider configuration as you prepare to install the TMA SNA software. The normal TMA SNA environment includes two properly configured components: the Tuxedo Mainframe Adapter for SNA Gateway and the Communications Resource Manager (CRM). The type of network connectivity you are working with determines which type of CRM installation and configuration is required.

When the Tuxedo Mainframe Adapter for SNA Gateway and CRM are installed on the same machine with the CRM configured as a Tuxedo server, the installation is referred to as a local (combined) configuration. When these components are installed on different UNIX, or mainframe platforms, the installation is referred to as a distributed (or remote) configuration. The diagrams in the following sections show examples of the TMA SNA components in three types of configurations.

Local Configuration

Local configuration consists of the application, which is the Tuxedo Mainframe Adapter for SNA Gateway and the CRM with the necessary libraries needed to communicate with the stack on the same UNIX platform. This configuration uses the IBM proprietary SNA protocol for transactions with the mainframe via the stack. This configuration requires a one-to-one relationship between the local Tuxedo Mainframe Adapter for SNA Gateway and the CRM.

Figure 1‑1 Local Configuration

Distributed Configurations

In a distributed configuration, the CRM is installed on a different platform than the Tuxedo Mainframe Adapter for SNA Gateway and applications.

One type of distributed configuration separates applications and the Tuxedo Mainframe Adapter for SNA Gateway from the CRM by installing the CRM to the z/OS mainframe. This configuration eliminates the need for a third-party stack on the UNIX machine. This configuration requires a one-to-one relationship between the local Tuxedo Mainframe Adapter for SNA Gateway and the remote CRM.

Figure 1‑2 Distributed Configuration

Another type of distributed configuration separates applications and the Tuxedo Mainframe Adapter for SNA Gateway from the CRM on different UNIX-based platforms. This configuration uses Transmission Control Protocol/Internet Protocol (TCP/IP) connectivity between the TMA SNA Gateway and the CRM, as well as the SNA connectivity to the mainframe environment(s). This configuration provides the flexibility to deploy the ATMI platform separately from the CRM in installations that require the ATMI platform on an operating system other than the one on which the SNA stack is running. This configuration also requires a one-to-one relationship between the local Tuxedo Mainframe Adapter for SNA Gateway and the remote CRM.

Figure 1‑3 Alternate Distributed Configuration

Oracle Tuxedo Mainframe Adapter for SNA Components

Oracle Tuxedo Mainframe Adapter for SNA 12c Release 2 (12.2.2) contains the following components:

•	Oracle Tuxedo Mainframe Adapter for SNA Gateway

The component that contains the Oracle Tuxedo Mainframe Adapter for SNA Gateway files.

•	Oracle Tuxedo Mainframe Adapter for SNA CRM (Only supported on certain platforms)

The component that contains the Oracle Tuxedo Mainframe Adapter for SNA CRM files.

Hardware and Software Prerequisites

The Oracle Tuxedo Mainframe Adapter for SNA must be installed into an Oracle Home which has already installed Oracle Tuxedo 12c Release 2 (12.2.2) server component.

System Requirements

Oracle Tuxedo Mainframe Adapter for SNA 12c Release 2 (12.2.2) must be installed on a supported OS version for the given platform. Refer to Supported Oracle Tuxedo Mainframe Adapter for SNA Gateway Platforms for the supported platforms.

Software Requirements

Java Runtime Environment (JRE) 1.7 or 1.8 is required to install Oracle Tuxedo Mainframe Adapter for SNA. You need to install the required JRE and set the environment variable JAVA_HOME accordingly before installing Oracle Tuxedo Mainframe Adapter for SNA.

Temporary Storage Space Requirements

The Oracle Installation program uses a temporary directory in which it extracts the files from the archive that are needed to install Oracle Tuxedo Mainframe Adapter for SNA on the target system. During the installation process, your temporary directory must contain sufficient space to accommodate the compressed Java Runtime Environment (JRE) bundled with the installer and an uncompressed copy of the JRE that is expanded into the temporary directory. The installation program moves the JRE from the temporary directory to the Oracle Home directory at the end of the installation process. For information about the Oracle Home directory, see �$paratext>� on page 1‑11.

By default, the installation program uses the temporary directories shown in Table 1‑1.

 

Table 1‑1 Temporary Directories

Platform	Directory
UNIX	/tmp

To ensure there is adequate temporary space, you may want to allocate an alternate directory for use as a temporary directory for the installation. To do so, perform the appropriate step in Table 1‑2 and clean up files as more as possible in the temporary directory before starting the Oracle Installation program.

 

Table 1‑2 Perform This Step

On This Platform...	Perform This Step...
UNIX	Enter the following command at the shell prompt: export IATEMPDIR=tmpdirname Replace tmpdirname with the name of a temporary directory of your choice.

Requirements for Other Components

Whether your TMA SNA software is installed on UNIX, or a mainframe, make sure your system meets the appropriate requirements and that supporting software is operating correctly. The following sections describe mainframe and non-mainframe requirements, and verification of supporting software installations.

Note:

Because TMA SNA interacts with mainframe applications, involve your mainframe system support personnel early in the process of planning and installing your TMA SNA software. Different individuals may be responsible for Multiple Virtual System (MVS), Virtual Telecommunications Access Method (VTAM), Information Management System (IMS), and Customer Information Control System/Enterprise Systems Architecture (CICS TS). Make sure everyone is involved.

Mainframe Requirements

Whether the CRM component of TMA SNA is located on the mainframe environment or not, mainframe configurations affect how TMA SNA software functions. Prepare the mainframe to conduct operations within the Tuxedo Mainframe Adapter for SNA/ATMI platform environment by:

•	Establishing the VTAM configuration

•	Configuring the CICS TS Logical Unit (LU) by defining proper connections and sessions

•	Completing cross-platform definitions for non-mainframe CRM

•	Ensuring that APPC and transaction definitions exist for that environment, if using IMS or APPC/MVS

Refer to the Oracle Tuxedo Mainframe Adapter for SNA CRM Administration Guide for detailed information about these tasks.

Non-Mainframe Requirements

A non-mainframe environment is a UNIX machine running the TMA SNA software. The software is fully bidirectional, supporting the local system as either a client or server. This environment consists of the following components:

•	Hardware, defined as any workstation and network interface supported by the required software.

•

Operating system software and SNA protocol stacks (PU servers) if the CRM is not installed on the mainframe. (Refer to the Tuxedo Mainframe Adapter for SNA Release Notes for a complete listing.) Stack installation should also be completed and verified. Refer to vendor documentation for stack installation and verification information.

•	Tuxedo ATMI platform. Refer to the Oracle Tuxedo Mainframe Adapter for SNA Release Notes for information on platform support.

The Tuxedo ATMI platform is not required if you are installing only the CRM on Unix.

Installing the Prerequisite Software

The following software should be installed and configured prior to installing the TMA SNA software for UNIX:

1.	If you are installing the CRM on Unix:

a.	Install a supported SNA stack on the operating system where the CRM will be installed. Validate the stack software installation, running any sample applications provided by the vendor.

b.	Configure the supported SNA stack.

Refer to the Tuxedo Mainframe Adapter for SNA Release Notes for a list of supported SNA stacks.

Note:

Refer to the SNA stack vendor’s documentation on configuring your environment. A properly configured SNA protocol stack is required for the CRM to communicate with the mainframe application.

2.	Install and configure the Tuxedo ATMI platform. Validate the software installation by running the sample applications, such as simpapp or bankapp.

Refer to the corresponding product installation documentation for installation and configuration information. Some specific configuration tasks must be completed before you install TMA SNA.

3.	Shut down all domain administrative and gateway servers within an application domain prior to installing TMA SNA software, particularly the following:

•

GWTDOMAIN

•

GWADM

•

DMADM

Do not run the following commands until the installation is complete:

•

dmadmin

•

dmloadcf

•	dmunloadcf

Oracle Installation Program

The Oracle Tuxedo Mainframe Adapter for SNA software is distributed as an installer file, which also contains a copy of the Oracle Installation program. The Oracle Installation program is the Oracle standard tool for installing the Oracle Tuxedo Mainframe Adapter for SNA software on UNIX systems.

Cancelling Installation

Clicking the “Cancel” or the “close’ window button in GUI mode creates an incomplete Oracle Tuxedo Mainframe Adapter for SNA 12c Release 2 (12.2.2) installation. You will have to re-install Oracle Tuxedo Mainframe Adapter for SNA 12c Release 2 (12.2.2).

If you installed Oracle Tuxedo Mainframe Adapter for SNA 12c Release 2 (12.2.2) in a previous Tuxedo product directory, and you want to return to your original configuration, you must re-install your previous Oracle Tuxedo Mainframe Adapter for SNA version.

Install Types

An install type is a bundle of product software components related by function. Oracle Tuxedo Mainframe Adapter for SNA 12c Release 2 (12.2.2) offers the following install types:

•	Full Installation - consists of all the Oracle Tuxedo Mainframe Adapter for SNA 12c Release 2 (12.2.2) components.

•	Gateway Only Installation - consists of the following component:

•	Oracle Tuxedo Mainframe Adapter for SNA Gateway

•	Distributed CRM Installation - consists of the following component:

•	Oracle Tuxedo Mainframe Adapter for SNA CRM

Notes:

•	Install types are supported on certain platforms only.

•	The top component "Oracle Tuxedo Mainframe Adapter for SNA" and sub-component "Oracle Universal Installer" are installed for every install type.

In addition to selecting an install set during an Oracle Tuxedo Mainframe Adapter for SNA 12c Release 2 (12.2.2) installation, a user can further customize the installation by selecting (adding) or deselecting (deleting) one or more software components from the install set. Customizing is only possible for GUI-mode installation methods described in �$paratext>� on page 2‑1.

Installation Road Map

You are now ready to begin your installation. To install Oracle Tuxedo Mainframe Adapter for SNA 12c Release 2 (12.2.2), see one of the following sections:

•	�$paratext>� on page 2‑1

•	�$paratext>� on page 3‑1

If you want to uninstall your Oracle Tuxedo Mainframe Adapter for SNA software, see �$paratext>� on page 5‑1.