The following sections provide information that you need to know before installing the Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) product software:The Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) product software installer is based on the Oracle Universal Installer (OUI). To install the Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) 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.When you install Oracle Tuxedo Message Queue 12c Release 2 (12.1.3), an Oracle home is created. Oracle home is managed by OUI.To install Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) and create the Oracle home, do the following steps:
1. To remove an existing Oracle home, run OUI and click Deinstall Products. In the inventory dialog, select the home(s) you want to delete and click Remove. You can also use the REMOVE_HOMES variable in the command line or in a response file.[On UNIX] ./runInstaller -deinstall -silent ORACLE_HOME=<LOCATION_OF_ORACLE_HOME> "REMOVE_HOMES={<LOCATION_OF_ORACLE_HOME_TO_BE_REMOVED>}"In each case, the ORACLE_HOME name is taken first from the command line if it is specified, or from the response file if specified. If not specified, the following convention is used for the name:The ORACLE_HOME path is taken first from the command line if specified, or from the response file if specified. If not specified, the ORACLE_HOME environment variable is used.OUI supports the installation of several active Oracle homes on the same host as long as the products support this at run-time. Multiple versions of the same product or different products can run from different Oracle homes concurrently. Products installed in one home do not conflict or interact with products installed on another home. You can update software on any home at any time, assuming all Oracle applications, services, and processes installed on the target home are shut down. Processes from other homes may still be running.If the selected ORACLE_HOME has already installed Oracle Tuxedo Message Queue of the same version, the installer will show a warning.It is not allowed to install Oracle Tuxedo Message Queue of the same version or install related products on different ORACLE_HOME for windows platforms; otherwise, you will get an error box.
In UNIX, if you do not want to use the Central Inventory located in the directory specified by the inventory pointer file, you can use the -invPtrLoc flag to specify another inventory pointer file. The syntax is as follows:
Note: If the content of the oraInst.loc file is empty, OUI prompts you to create a new inventory.The logs directory contains the logs corresponding to all installations performed on a particular node. You can also find a copy of the installation log in the $ORACLE_HOME/cfgtoollogs directory.This file contains node list details, the local node name, and the CRS flag for the Oracle home. In a shared Oracle home, the local node information is not presented. This file also contains the following information:
• GUID — Unique global ID for the Oracle home
• ARU ID — Unique platform ID. The patching and patchset application depends on this ID.
• ARU ID DESCRIPTION — Platform descriptionThe information in oraclehomeproperties.xml overrides the information in inventory.xml. This file is located at:
You can set up the Central Inventory by using the -attachHome flag of Oracle Universal Installer. The syntax is as follows:After attaching the Oracle home, you can verify the success of the operation by verifying the contents of the log file located in the <central_inventory>/logs directory. You can also view the contents of the inventory.xml file under the <central-inventory>/ContentsXML directory to verify if the Oracle home is registered.You can detach an Oracle home from the Central Inventory. When you pass the flag, it updates the inventory.xml file presented in the Central Inventory. The syntax is as follows:If you are using a shared Oracle home, use the -cfs flag. This ensures that the local node information is not populated inside a shared Oracle home.If you want to disable the warning message that appears when you use the -removeallfiles flag, use the -nowarningonremovefiles flag. The syntax is as follows:
1. Locate the oraInst.loc file and get the Central Inventory location (inventory_loc parameter) from this file.
• For Solaris, it is located in the /va/opt/oracle folder.
• For Linux, it is located in the /etc folder.
3. Remove the oraInst.loc file by executing the following command with root privileges:
• Solaris: rm /va/opt/oracle/oraInst.loc
• Linux: rm /etc/oraInst.loc
• If you attempt to perform silent installation on a UNIX computer where no Oracle products have been installed, OUI uses the default inventory location, and then prompts you to run the oraInstRoot.sh script with root privileges upon successful installation.
• The script is saved in the _*Central Inventory - oraInventory *_ directory. This script sets up the Central Inventory on a clean host. You can override the default location by setting it in INVENTORY_LOCATION.
• This location is ignored if a Central Inventory already exists and is pointed to /var/opt/oracle/oraInst.loc (or /etc/oraInst.loc for Linux, AIX, and Sequent).
1. At the command prompt, use the cd command to change to the directory that contains the Oracle Universal Installer executable file (setup.exe or runInstaller.sh) for your installation.
Note: The values that are given as <value_required> must be specified for silent installation to be successful.For values given as <value_unspecified>, you can optionally specify a value, where <value> can be one of the following types listed in below table.
TRUE or FALSE (case insensitive)
• If you specify Forced, no dialog appears during installation. The value is automatically used. You cannot change the value.
• If you specify Default, the dialog appears during installation with the value as the default. You can choose another value if desired.
• Comments begin with a "#" (hash or pound) symbol. They contain information about the type of the variable, state whether the variable appears in dialog, and describe the function of the variable. A variable and a value are associated with a comment.For Oracle Tuxedo Message Queue specific response file parameters, see “Required Variables in Oracle Tuxedo Message Queue Response File”.You should specify the absolute path in the INCLUDE statement for each response file to be included. If you wish to specify a relative path, note that the location is relative to the current working directory (the location of the oraparam.ini file).The location of the source of the products to be installed. The default generated value for this parameter is a path relative to the location of the runInstaller file oraparam.ini. Relative paths are necessary for shared response files used by multiple users over a network. Since people may be mapping to different drives, absolute paths will not work for shared response files.
• You must enter a value for FROM_LOCATION for a complete silent installation. You may want to use the command line to set this parameter. If the location is a relative path, remember that the path should be relative to the location of the oraparam.ini file.
• Make sure that /var/opt/oracle/oraInst.loc (or /etc/oraInst.loc for Linux, AIX, and Sequent) exists. The response file for UNIX has a public variable, setunixinstallgroup, which only becomes effective when it is the first OUI installation and the oraInst.loc file is not already present at the location mentioned above.Used in multiple-CD installations. It includes the label of the compact disk where the file products.jar exists. You can find the label in the disk.label file in the same directory as products.jar.If there are more than two disks, more variables will be added as LOCATION_FOR_DISK3, and so on.
• OUI looks for the Location_For_Disk{DiskNumber} variable in the response file and uses that location.
• If the variable does not have a value or does not have the required files, it looks for the components under ../../Disk{DiskNumber}/stage (from products.jar).Set this boolean variable to TRUE if you want to restart the system without user confirmation. This is the force value for restarting the system.Set this boolean variable to TRUE if the installer needs to go to the File Locations page for another installation or to another response file if you are performing a silent installation.Set this boolean variable to TRUE to allow users to invoke another installation session even if the current installation session fails. This variable is used only if NEXT_SESSION variable is set to TRUE.Use this string variable to enter the complete path of the response file for the next session if you want to automatically begin another silent installation when the current installation is complete. If you specify only a file name, the Installer looks for the response file in the <TEMP>/orainstall directory. This variable is only used if NEXT_SESSION is set to TRUE; otherwise, OUI ignores the value of this variable.The location where products are to be installed. You must enter a value for ORACLE_HOME for a complete silent installation.The name of the current Oracle home. You must enter a value for ORACLE_HOME_NAME for a complete silent installation.The location page, which appears in a custom installation type, can be suppressed by setting this value to FALSE. If you set the value to FALSE, you are prevented from specifying alternate directories. If there are products with installed directories which can be changed, you may want to set the value to TRUE.Set SHOW_CUSTOM_TREE_PAGE to TRUE if the custom tree page in the installer must be shown. In the Custom Tree page, dependencies can be selected or deselected. This page appears only during custom installation type.Set to TRUE if you need to show the confirmation when exiting the installer.Set to TRUE if you must show the Optional Configuration Tools page in the installer. The Optional Configuration Tools page shows a list of optional configuration tools that are part of this installation and the status of each tool, including detailed information on why the tool has failed.Set to TRUE if you need to show the Confirmation dialog asking to run the root.sh script in the installer. This variable is valid only on UNIX platforms.Set to TRUE if the initial splash screen in the installer needs to be shown.Set to TRUE if you need to show the Welcome page on the installer.Set this parameter to TRUE if you want the release notes for this installation to be shown at the end of the installation. A dialog box lists the available release notes. Note that the SHOW_END_SESSION parameter must be set to TRUE before you can use this parameter.The name of the component (products), and the version as a string list. You must enter a value for TOPLEVEL_COMPONENT.For example, RDBMS 11.1. may be represented as {"oracle.rdbms","11.1.0.0.0"}.Set to FALSE if you want to hide the deinstall confirmation dialog box during silent deinstallation.Set this parameter to FALSE if you want to hide the deinstallation progress dialog box during silent deinstallation.
• The DEPENDENCY_LIST variable is only generated when dependencies are present and if the dependency is not a required one.While all the required configuration tools are launched by the installer, you can control the optional configuration tools you would want to launch by specifying the tool internal names in the OPTIONAL_CONFIG_TOOLS section.
Note: The OPTIONAL_CONFIG_TOOLS variable is only generated when at least one optional configuration tool is available.You can also call the Net Configuration Assistant or the Database Configuration Assistant at the end of a database installation in silent mode. For example, to launch the Net Configuration Assistant in silent mode, you can pass the parameter s_responseFileName="netca.rsp".You can specify both the Auto-launch optional tools and User-launch optional tools in a string list.Suppress the configuration tool by mentioning only the tools that you want to run as part of the OPTIONAL_CONFIG_TOOLS variable added for each component. You should use the configuration tool internal names.For example, if oracle.server has Tool1 and Tool2 and you want to run only Tool1 in the response file, you can specify it as follows:
Note: You must enter a value for INSTALL_TYPE.
Note: The SELECTED_LANGUAGES variable is only generated when more than one language is available.
Note: If you attempt to perform a silent installation on a UNIX computer where no Oracle products have been installed, you will receive an error message. Before you can perform a silent installation on such a computer, you must first run the oraInstRoot.sh script, which is saved in the /oraInventory directory. You must run this script with root privileges. This enables OUI to set up the Central Inventory on a clean host.On Windows: setup.exe -responseFile <filename> <optional_parameters>On UNIX: ./runInstaller -responseFile <filename> <optional_parameters>
Note: You must specify the complete responseFile path. If you do not, OUI assumes the location to be relative to the oraparam.ini file associated with the launched OUI.For Windows, when you execute setup -help, a new command window appears, with the "Preparing to launch..." message. A moment later, help information appears in that window.Optional parameters you can use with the -responseFile flag are:
• -nowelcome — Used flag with the -responseFile flag to suppress the Welcome dialog that appears during installation.
• -silent — Used with the -responseFile flag to run OUI in complete silent mode. Note that the Welcome dialog is suppressed automatically.
• In a file named silentInstall<timestamp>.log for hosts without an Oracle inventory. This file is generated in the /tmp directory (UNIX) and the directory specified by the TEMP variable (Windows).
Note: Using the -nowelcome option with the -silent option is unnecessary since the Welcome screen does not appear when you use the -silent option.
Note: The "session:" tag is optional and is used mainly to remove any possible ambiguity.
•
Note: You can use the -noConsole flag on Windows to suppress the display of console messages.
Note: On Windows, when you start the installer from a shared drive, you need to map the shared drive and then invoke the installer from the shared drive. When you invoke runInstaller (UNIX) or setup.exe (Windows), you should invoke it from the directory where this command is present, or you must specify the complete path to runInstaller (UNIX) or setup.exe (Windows).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:
2. Replace <machine name> with the name of the computer that will display OUI.
4.
Note: You can run OUI without specifying the DISPLAY variable by running in silent mode using a response file.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.
2.
4. Run the shell script ./root.sh.
Note:
• For Windows platforms, launch OUI from the Start menu by selecting Start, Installation Products, Oracle Universal Installer.
• For UNIX platforms, from the command line, run the script called runInstaller from the directory where it is stored by default at the same level as the first Oracle home created on that host.
2. Click Deinstall Products on the Welcome screen.
3. Select the product(s) you want to remove from the Contents tab of the Inventory panel and click Remove. You can also remove Oracle homes in the same manner. After you have removed an Oracle home, you can reuse its name and location to install other products.
Note: You can also remove products by using the OUI Installed Products button as long as you perform this action before selecting products to install.setup.exe -deinstall -silent (on Windows)./runInstaller -deinstall -silent (on UNIX)If you want to hide the inventory dialog box during a deinstallation, you can specify the products to be removed in the response file DEINSTALL_LIST parameter; specify Oracle homes to be removed with the REMOVE_HOMES variable.As with other response file parameters, you can also specify the DEINSTALL_LIST parameter on the OUI command line. For example, on a UNIX machine, enter:To remove Oracle homes from the inventory, use the REMOVE_HOMES variable.
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.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.An evaluation copy of Oracle Tuxedo Message Queue is available for download from the Oracle corporate Web site at http://www.oracle.com/technology/software/index.html.The Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) software distribution contains the following components:
• The Oracle Tuxedo Message Queue software must be installed on each server machine that will participate in an Oracle Tuxedo Message Queue application, also known as a Tuxedo domain. An Oracle Tuxedo Message Queue application is a business software program, built upon the Tuxedo system, which is defined and controlled by a single configuration file known as the UBBCONFIG file. The Tuxedo configuration file is described in reference page UBBCONFIG(5) in Oracle Tuxedo File Formats, Data Descriptions, MIBs, and System Processes Reference.An Oracle Tuxedo Message Queue application consists of many Tuxedo system processes, one or more application client processes, one or more application server processes, and one or more computer machines connected over a network. In a multi-machine Oracle Tuxedo Message Queue application running different releases of the Oracle Tuxedo Message Queue software, the master machine—designated via the MASTER parameter in the RESOURCES section of the UBBCONFIG file—must run the highest release of the Oracle Tuxedo Message Queue software in the application. For more information about Oracle Tuxedo Message Queue applications, see Oracle Tuxedo Message Queue Product Overview.The system requirements for Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) are given in Table 1‑1.
Table 1‑1 The System Requirements for Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) To install Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) on an existing Oracle Tuxedo version, you must select full installation in Oracle Tuxedo 12c Release 2 (12.1.3) installation.The Oracle Installation program uses a temporary directory in which it extracts the files from the archive that are needed to install Oracle Tuxedo Message Queue 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 “Oracle Home Directory”.The amount of temporary storage space needed depends upon the target platform, as stated in the data sheets in “Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) Platform Data Sheets”.When you start OUI, it automatically copies some executable files and link files into the default /tmp directory (C:\Documents and Settings\<user ID>\Local Settings\Temp on Microsoft Windows) 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.
Note: This procedure is the same as the Oracle Tuxedo 12c Release 2 (12.1.3) installation.For more information about configuring IPC resource, see "IPC Resource Configuration on a UNIX System" and "Performing Post-Installation Tasks" in Installing the Oracle Tuxedo System.This procedure is the same as the Oracle Tuxedo 12c Release 2 (12.1.3) installation.For more information about configuring IPC resource, see "IPC Resource Configuration on a UNIX System" and "Performing Post-Installation Tasks" in Installing the Oracle Tuxedo System.
•
• Clicking the “Cancel” or the “close’ window button in GUI mode creates an incomplete Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) installation. You will have to re-install Oracle Tuxedo Message Queue 12c Release 2 (12.1.3).You can either install Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) in a previous Tuxedo product directory, or install the Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) to a new Oracle Home product directory.An install type is a bundle of product software components related by function. Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) offers the following install types:During the installation of Oracle Tuxedo Message Queue 12c Release 2 (12.1.3), you are prompted to choose an existing Oracle Home directory or specify a path for a new Oracle Home directory. If you choose to create a new directory, the Oracle Tuxedo Message Queue installer program automatically creates the directory for you.You are now ready to begin your installation. To install Oracle Tuxedo Message Queue 12c Release 2 (12.1.3), see one of the following sections: