Installing Oracle Tuxedo on OpenVMS

This chapter explains how to install and configure the Oracle Tuxedo system on your OpenVMS system.

The topics covered in this chapter include:

•	Preparing to Install Oracle Tuxedo

•	Installing Oracle Tuxedo

•	Setting Up Your Environment

Preparing to Install Oracle Tuxedo

Note:

Before you begin the installation process, you may wish to review the Polycenter product installation utility (PCSI). This utility is used to install Oracle Tuxedo and you should have a working knowledge of its operation.

Before installing Oracle Tuxedo, you must:

•	Verify that your machine meets the hardware and software requirements.

•	Verify that you (as the person installing Oracle Tuxedo) have the necessary user ID privileges and quotas.

The following sections provide procedures for verifying this information.

Verifying the Hardware and Software Configuration

Before you install Oracle Tuxedo, you must verify that the machine on which you wish to install Oracle Tuxedo meets the minimum hardware and software requirements.

Use the following procedure to verify your machine meets the requirements.

1.	Review the hardware and software configuration of the machine on which you wish to install Oracle Tuxedo.

2.	Compare your configuration with the hardware and software requirements. For more information, see Oracle Tuxedo 11g Release 1 (11.1.1.2.0) Platform Data Sheets.

3.	Verify that the machine on which you wish to install Oracle Tuxedo has at least 1 gigabytes of available disk space.

4.	Verify that the HP OpenVMS patch QXCM1001201953_4638493661-461_2012-04-17 has been applied to the operating system.

Note:

This image should be used on IA64 platforms running OpenVMS V8.4 with the VMS84I_UPDATE V6.0 kit installed. Please note that this fix will be available in the ACRTL TIMA kit. If you do not have the ACRTL TIMA kit, it is advised that you use this patch.

Any future update kit or ACRTL V0100 TIMA kit installation used in your customer environment, overrides this fix. You may have to request a new set of DECC$SHR* images to use this fix on top of the update or ACRTL V0100 TIMA kit.

Verifying the User ID Privileges and Quotas

The person installing Oracle Tuxedo must log on to the machine with the user ID privileges and quotas as listed in Table 2‑1

.

Table 2‑1 User ID Privileges and Quotas

User ID Privileges	User ID Quotas
CMKRNL	ASTLM: 400
SETPRV	BIOLM: 500
SYSLCK	DIOLM: 500
SYSNAM	ENGLM: 500
SYSGBL	FILLM: 500
PRMGBL	BYTLM: 5000000
DETACH	DGFLQUOTA: 30000
	PRCLM: 5
	TQELM: 500
	WSDEFAULT: 512
	WSEXTENT: 8192
	WSQUOTA: 1024

Use the following procedure to verify the user ID privileges.

1.	Open the user account file for editing.

2.	Enter the following line in the user account file.

set proc/priv=all

Installing Oracle Tuxedo

1.	Log on to the machine using the user ID that you verified in "Verifying the User ID Privileges and Quotas."

2.	Prepare your installation package (PCSI), for example put it under "src_dir" directory.

3.	Start the product installation utility (PCSI):

product install Tuxedo /source=src_dir/destination=dest_dir

where:

•	src_dir is the directory in which you put the installation package (PCSI).

•	dest_dir is the directory in where Oracle Tuxedo is installed. dest_dir must be a valid directory name.

4.	The PCSI utility will ask you about the type of installation you want to perform.

Select one of the following options:

1- Full Install

2- Server Install

3- Full Client Install

4- Jolt Client Install

5- ATMI Client Install

6- Customize ...

Note:

full (to install Oracle Tuxedo installation component packages)

server (to install all Oracle Tuxedo server package)

full client (to install only the Oracle Tuxedo all client packages)

jolt client (to install only the Oracle Tuxedo Jolt client)

atmi client (to install only the Oracle Tuxedo ATMI client)

5. The PCSI utility will install the required files. You can monitor the progress of the installation on the screen.

Setting Up Your Environment

Before you can use Oracle Tuxedo, you must set up your environment using a DCL script named postinstall. The DCL script performs the following tasks:

•	Installs any shared images that will be referenced by Oracle Tuxedo processes at run time

•	Sets all the logical names in either the group table or system table, depending on the options selected when the DCL script is run

•	Sets the environment for the vps_daemon process

•	Starts the vps_daemon if you have requested this process

Note:

This script must be run each time the machine is rebooted. The Oracle Tuxedo administrator may put the DCL script into the start-up environment so that when the machine is rebooted the script will be executed.

Logical Names

Before you can use Oracle Tuxedo, you must set several logical names. The OpenVMS operating system allows you to set logical names in either the group table or the system table.

Group Table

Setting logical names in the group table gives you the ability to run multiple versions of Oracle Tuxedo on the same platform. Subsequent versions of the Oracle Tuxedo system can be installed under different group tables.

To use this method requires that all users who want to invoke Oracle Tuxedo commands must be listed in the group table in which all the required logical names for Oracle Tuxedo reside.

System Table

Setting logical names in the system table allows you to give all users of a system access to Oracle Tuxedo. However, subsequent versions of Oracle Tuxedo cannot be installed simultaneously on the same machine.

vps_daemon Process

The vps_daemon process provides the basic infrastructure for Oracle Tuxedo client and server processes. Oracle Tuxedo client and server processes use the vps_daemon process to perform data exchange, synchronization, monitoring, and network communication functions. The vps_daemon process also allocates the resources needed for Oracle Tuxedo client and server processes to perform these functions.

The vps_daemon process requires that the logical name VPS_INITPATH point to a valid file containing the configuration parameters for the process. This file, vps_init.txt, is located in the udataobj directory and should not be modified. The parameters in this file are comparable to the IPC (Inter Process Communication) tunable parameters on the UNIX platform and to the IPC parameters on the Windows NT platform. The default parameters in vps_init.txt are capable of supporting approximately 50 Oracle Tuxedo servers and 200 Oracle Tuxedo clients.

If you want to change the default parameters (or perform other advanced configuration tasks), please consult Oracle Support.

Configuring Oracle Tuxedo

This section explains how to configure Oracle Tuxedo once you have finished installing it.

Configuration Instructions

Use the following procedure to complete the configuration process.

1.	Change the current directory to the dest_dir.bin directory, where dest_dir is the directory you specified during installation.

2.	On the command line, enter the following command.

set default device:[dest_dir.BIN]

where device is the device specification of your file system and dest_dir is the directory you specified during installation.

3.	On the command line, enter the following command:

@postinstall

4.	The DCL script will prompt you for information on configuring the Oracle Tuxedo system at the group level or at the system level.

5.	If this is not a workstation-only installation, the DCL script will prompt you for the tlisten password.

Note:

The DCL script will not echo the password but it will verify the password.

6.	The DCL script will prompt you to indicate if the script should start the vps_daemon process.

Note:

If you choose not to start the vps_daemon process, then you will have to manually start the process. The vps_daemon.exe file is located in the BIN directory of the Oracle Tuxedo installation directory.

7.	The DCL script will prompt you to configure LDAP settings for SSL support.

Note:

if you intend to use SSL encryption in your application, select 'Y' and enter the following LDAP configuration information.

•	LDAP Service Name: The URL of the LDAP server system

•	LDAP PortID: A port number for the URL of the LDAP server system

•	LDAP BaseObject: A base object for search in LDAP server

•	LDAP Filter File Location: The name of LDAP filter file, if the input is null, the default value of "$TUXDIR.udataobj.security]bea_ldap_filter.dat" is used

if you want to use command, epifregedt.exe, to register the LDAP Filter File Location manually, please pay attention its format. The following example shows the correct format and incorrect format:

correct format:

epifreg -u "filterFileLocation=file:////dka0/tuxedo11gR1/udataobj/security/bea_ldap_filter.dat"

epifreg -u "filterFileLocation=file:///dka0:[tuxedo11gR1.udataobj.security]bea_ldap_filter.dat"

incorrect format:

epifreg -u "filterFileLocation=file://dka0:[tuxedo11gR1.udataobj.security]bea_ldap_filter.dat"

Oracle Tuxedo should now be fully configured and ready to run.

Disable Multiple Kernel Thread for GWTDOMAIN

Disabling multiple kernel thread for GWTDOMAIN may improve overall performance. To disable multiple kernel threading, use the following command:

set image/flags=(NOMKTHREADS) GWTDOMAIN.EXE.