Preparing to Install the Oracle Tuxedo Application Runtimes

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

•	Oracle Universal Installer (OUI)

•	Oracle Tuxedo Application Runtimes Web Distribution

•	Oracle Tuxedo Software Components

•	Hardware and Software Prerequisites

•	Oracle Installation Program

•	Installation Road Map

Oracle Universal Installer (OUI)

The Oracle Tuxedo Application Runtimes 12c Release 2 (12.2.2) product software installer is based on the Oracle Universal Installer (OUI). To install the Oracle Tuxedo Application Runtimes 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 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.

•

Console:

Use OUI console mode to bypass the graphical user interface and execute the Oracle Installation program with a console interactive interface. This method is intended for UNIX systems with non-graphical consoles.

•

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. 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.

Oracle Tuxedo Application Runtimes Web Distribution

An evaluation copy of Oracle Tuxedo Application Runtimes is available for download from the Oracle corporate Web site at http://www.oracle.com/technology/software/index.html.

Platform-specific installer files for the Oracle Tuxedo Application Runtimes product software are available for download from the Oracle corporate Web site.

Oracle Tuxedo Software Components

Included with the Oracle Tuxedo Application Runtimes 12c Release 2 (12.2.2) software distribution is the Oracle Tuxedo Application Runtimes administrative utilities and Oracle Tuxedo Application Runtimes sample applications (optionally installed).

The Oracle Tuxedo Application Runtimes 12c Release 2 (12.2.2) distribution contains the following components:

•	Oracle Tuxedo Application Runtime for CICS

•	Oracle Tuxedo Application Runtime for Batch

•	Oracle Tuxedo Application Runtime for IMS

Hardware and Software Prerequisites

The Oracle Tuxedo Application Runtimes must be installed into an Oracle Home which has already installed Oracle Tuxedo Server component.

System Requirements

The system requirements for Oracle Tuxedo Application Runtimes 12c Release 2 (12.2.2) are given in Table 1‑1.

 

Table 1‑1 The System Requirements for Oracle Tuxedo 12c Release 2 (12.2.2)

Component	Requirement
Platform*	Any platform identified in Supported Platforms.
Hard disk drive	As stated in the data sheet for the target platform in Supported Platforms.
Memory	As stated in the data sheet for the target platform in Supported Platforms.

Software Requirements

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

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 Application Runtimes on the target system. The amount of temporary storage space needed depends upon the target platform, as stated in the data sheets in Supported Platforms.

When you start OUI, it automatically copies specific executable files and link files into the default /tmp directory on the machine. If the machine is set to run cron jobs periodically (along with many other processes that may be running), these jobs attempt to clean up the default temporary directory, thereby deleting some files and causing OUI to fail.

To ensure there is adequate temporary space, you may want to allocate an alternate directory for use as a temporary directory for the installation. If there are any cron jobs or processes that are automatically run on the machines to clean up the temporary directories, ensure you set the TMP or TEMP environment variable to a different location (other than the default location) that is secure on the hard drive (meaning a location on which the cleanup jobs are not run). Also ensure that you have write permissions on this alternative TEMP directory. This must be done before you execute runInstaller.sh.

Note:

Specifying an alternative temporary directory location is not mandatory, and is required only if any cron jobs are set on the computers to clean up the /tmp directory.

Oracle Installation Program

The Oracle Tuxedo Application Runtimes 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 Application Runtimes software on UNIX systems.

Cancelling Installation

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

If you installed Oracle Tuxedo Application Runtimes 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 Application Runtimes version.

Install Types

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

•	Full Install - consists of all the Oracle Tuxedo Application Runtimes 12c Release 2 (12.2.2) components.

•	CICS Runtime Install - consists of the Oracle Tuxedo Application Runtime for CICS 12c Release 2 (12.2.2) component.

•	Batch Runtime Install - consists of the Oracle Tuxedo Application Runtime for Batch 12c Release 2 (12.2.2) component.

•	IMS Runtime Install - consists of the Oracle Tuxedo Application Runtime for IMS 12c Release 2 (12.2.2) component.

•	Custom Install

In addition to selecting an install set during an Oracle Tuxedo Application Runtimes 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 Installing Oracle Tuxedo Application Runtimes Using GUI-Mode Installation.

Installation Road Map

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

•	Installing Oracle Tuxedo Application Runtimes Using GUI-Mode Installation

•	Oracle Tuxedo Application Runtimes Console-Mode Installation

•	Installing Oracle Tuxedo Application Runtimes Using Silent Installation

If you want to uninstall your Oracle Tuxedo Application Runtimes software, see Performing Post-Installation Tasks.