This chapter guides you through the basic concepts and preinstallation steps for Oracle Procedural Gateway for WebSphere MQ. The following topics provide information about Oracle Procedural Gateway for WebSphere MQ, environment variables settings, and starting Oracle Universal Installer:
The preinstallation tasks for the Oracle Procedural Gateway for WebSphere MQ are divided into the following parts:
Perform the following steps to check for WebSphere MQ software:
Determine where the WebSphere MQ queue manager runs.
Local system
If the WebSphere MQ queue manager runs on the local systen, then the queue manager runs on the same system on which you intend to install the gateway product set.
Remote system
If the WebSphere MQ queue manager runs on a remote system, then the queue manager runs on a different system, and not the system where you intend to install the gateway product set.
Verify that the WebSphere MQ software is already installed. If the WebSphere MQ server software in installed on a different system than the gateway, then the WebSphere MQ client software must be installed on the gateway system.
Identify the name of the WebSphere MQ queue manager.
Identify the WebSphere MQ client channel definition.
If the queue manager resides on a different system than the gateway, then the WebSphere MQ client software is used to access the remote queue manager. A channel definition is required for this configuration.
Before installing Oracle Procedural Gateway for WebSphere MQ on UNIX platforms, set the the following environment variables:
ORACLE_HOME
ORACLE_SID
DISPLAY
TMP
Note:
Verify that the values that you assign to the environment variables, which are listed in this section, are less than 42 characters long. Longer values might generate errors such as ÒWord too longÓ during installation.ORACLE_HOME
is the root directory in which Oracle software is installed.
Oracle Procedural Gateway for WebSphere MQ cannot share the same Oracle home directory with other Oracle products. If you have installed other Oracle products, then Oracle Procedural Gateway for WebSphere MQ must be installed in a different ORACLE_HOME
directory. Refer to Preventing Conflicts Between ORACLE_HOME Directories.
Note:
Do not instal Oracle Procedural Gateway for WebSphere MQ in anORACLE_HOME
directory containing other Oracle products, including the database. Such an installation could overwrite shared components, causing the products to malfunction.To prevent a conflict between the software in an existing ORACLE_HOME
directory and Oracle Procedural Gateway for WebSphere MQ, you must remove all references to the existing ORACLE_HOME
directory. The following steps describe removing these references.
Unset your existing ORACLE_HOME
variable using one of the following commands.
Edit the following environment variables so that they do not use the existing ORACLE_HOME
value:
Table 4-1 Setting Environment Variables for a New ORACLE_HOME Directory
Environment Variable | Platforms |
---|---|
PATH |
AIX-based Systems, HP 9000 Series HP-UX, and Sun Solaris |
CLASSPATH |
AIX-based Systems, HP 9000 Series HP-UX, and Sun Solaris |
LD_LIBRARY_PATH |
Sun Solaris |
LIBPATH |
AIX-based Systems |
SHLIB_PATH |
HP 9000 Series HP-UX |
Note:
Verify that the C compiler is in your PATH before you start the installation.Set the ORACLE_HOME
environment variable by using one of the following commands:
Set the ORACLE_SID
environment variable by using one of the following commands:
Setting the DISPLAY environment variable enables you to run Oracle Universal Installer remotely from a local work station. On the system where you run Oracle Universal Installer, set the DISPLAY environment variable to specify the system name or IP address of your local workstation.
If you get an Xlib error when starting Oracle Universal Installer such as ÒFailed to connect to serverÓ, ÒConnection refused by serverÓ, or ÒCan't open displayÓ, then run the commands on your local workstations as follows:
C shell
prompt> xhost +server_name
Borne or Korn shell
prompt> xhost +server_name
During installation, Oracle Universal Installer uses a temporary directory for swap space. This directory must meet the "Hardware Requirements". The installation might fail if you do not have sufficient space. Oracle Universal Installer checks for the TMP environment variable to locate the temporary directory. If this environment variable does not exist, then the installer uses the /tmp
directory.
The following example demonstrates how to set the TMP environment variable.
Oracle Procedural Gateway for WebSphere MQ uses Oracle Universal Installer to configure environment variables and install components. Oracle Universal Installer guides you through each step of the installation process, so you can choose configuration options for a customized product.
Oracle Universal Installer includes features that perform the following tasks:
Explore and provide installation options for products
Detect preset environment variables and configuration settings
Set environment variables and configuration during installation
Uninstall products
Oracle Universal Installer creates the oraInventory
directory the first time it is run on your system. The oraInventory
directory keeps an inventory of the products that Oracle Universal Installer installs on your system as well as other installation information. If you have previously installed Oracle products, then you might already have an oraInventory
directory.
When a UNIX group name is specified, it grants that group the permission to write to the oraInventory
directory. If another group attempts to run Oracle Universal Installer, then they must have permission to write to the oraInventory
directory. If they do not have permission the installation fails.
The user running Oracle Universal Installer must have permission to write to the oraInventory
directory and all its files. This is required to run the installer.
The location of oraInventory
is defined in /etc/oratab/oraInst.loc
for HP 9000 Series HP-UX and AIX-Based Systems.
The location of oraInventory
is defined in /var/opt/oraInst.loc
for Sun Solaris.
The latest log file is oraInventory_location/logs/installActions.log
. Log file names of previous installation sessions are in the following format: installActions
datetime
.log
.
Do not delete or manually alter the oraInventory
directory or its contents. Doing this can prevent Oracle Universal Installer from locating products that you have installed on your system.
Perform the following steps to launch Oracle Universal Installer, which installs Oracle Procedural Gateway for WebSphere MQ:
Stop all Oracle processes and services (for example, the Oracle database).
Mount the installation CD-ROM.
The Oracle Product Installation CD-ROM is in RockRidge format. To begin installation, insert the CD.
To manually mount or unmount the CD-ROM, you must have root
privileges. Unmount the CD-ROM before removing it from the drive.
To manually mount the CD-ROM, perform the following tasks:
Insert the Oracle Procedural Gateway for WebSphere MQ CD-ROM into the CD-ROM drive.
Log in as the root
user.
Create the CD-ROM mount point directory.
prompt> mkdir mount_point
Mount the CD-ROM drive on the mount point directory and exit the root
account:
prompt> mount options device_name mount_point prompt> exit
The following examples show how to mount the CD-ROM manually on /cdrom
:
Platform | Command Example |
---|---|
AIX-Based Systems |
prompt> mkdir /cdrom
prompt> mount -o ro -V cdrfs device_name /mnt/cdrom
prompt> exit
|
HP 9000 Series HP-UX | Note: Add the following line to the /etc/pfs_fstab file:
/dev/dsk/c5t2d0./cdrom pfs-rrip xlat=unix 0 0 where /dev/dsk/c5t2d0 is the CD-ROM device file and pfs-rripxlat=unix 0 0 indicates the CD-ROM is in Rockridge extention. prompt> nohup /usr/sbin/pfs_mountd & prompt> nohup /usr/sbin/pfsd & Note: Insert the CD-ROM into the CD-ROM drive. prompt> /usr/sbin/pfs_mount /cdrom prompt> exit |
Sun Solaris |
prompt> mkdir /cdrom
prompt> mount -r -F hsfs device_name /cdrom
prompt> exit
|
Run Oracle Universal Installer from the CD-ROM.
root
user when you start Oracle Universal Installer. If you are, only the root
user will have permissions to manage Oracle Procedural Gateway for WebSphere MQ.Log in as the Oracle Procedural Gateway for WebSphere MQ user.
Start Oracle Universal Installer by entering:
prompt> mount_point/runInstaller
This launches Oracle Universal Installer using which you can install Oracle Procedural Gateway for WebSphere MQ.