Академический Документы
Профессиональный Документы
Культура Документы
Installation Guide
Software Release 5.1.3
May 2004
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH
EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY
(OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE.
THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY
ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND
CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED
SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT,
THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING
DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE
TIBCO RUNTIME AGENT ADMINISTRATOR’S GUIDE). USE OF THIS DOCUMENT IS SUBJECT
TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE
ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright
laws and treaties. No part of this document may be reproduced in any form without the written
authorization of TIBCO Software Inc.
TIB, TIBCO, Information Bus, The Power of Now, TIBCO Adapter, TIBCO Rendezvous, TIBCO
Hawk, TIBCO IntegrationManager, TIBCO Enterprise, and TIBCO Runtime Agent are either
registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other
countries.
All other product and company names and marks mentioned in this document are the property of
their respective owners and are mentioned for identification purposes only.
This software may be available on multiple operating systems. However, not all operating system
platforms for a specific software version are released at the same time. Please see the readme.txt file
for the availability of this software version on a specific operating system platform.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL
ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE
CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO
SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)
AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
Copyright ©1997-2004 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
| iii
Contents
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
TIBCO Runtime Agent Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Other Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
How to Contact TIBCO Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Tables
Table 1 Microsoft Windows: disk space, executable name, platforms and service packs . . . . . . . . . . . . . 10
Table 2 UNIX Systems: disk space, package names, platforms, and patches . . . . . . . . . . . . . . . . . . . . . . 16
Table 3 Windows (JVM 1.3.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 4 Solaris (JVM 1.3.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 5 HP-UX (JVM 1.3.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 6 AIX (JVM 1.3.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 8 Tru64 (JVM 1.3.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 7 Linux (JVM 1.3.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Preface
The preface lists the TIBCO Runtime Agent documentation set and other related
TIBCO documentation. Contact information for TIBCO support is also listed.
Topics
Related Documentation
Other Documentation
• TIBCO Runtime Agent includes TIBCO Designer. You will therefore find the
TIBCO Designer documentation useful. TIBCO Designer is an easy to use
graphical user interface for design-time configuration of TIBCO applications.
TIBCO Designer includes online help for each palette.
• If you are using the TIBCO Runtime Agent and TIBCO Adapter SDK suite, the
following Adapter SDK documents are included in the
<install-path>\tibco\tra\5.1\doc\sdk folder:
— TIBCO Adapter SDK Concepts
— TIBCO Adapter SDK Programmer’s Guide
— TIBCO Adapter SDK Message Codes
— TIBCO Adapter SDK Release Notes
— TIBCO Adapter SDK C++ API Reference
— TIBCO Adapter SDK Java API Reference (HTML only)
• TIBCO Runtime Agent is a prerequisite for TIBCO Adapters. You will
therefore find TIBCO Adapter product documentation useful. Each adapter
includes the TIBCO Adapter Concepts Guide, a User’s Guide and Release Notes.
Most adapters also include an Examples guide.
For comments or problems with this manual or the software it addresses, please
contact TIBCO Support Services as follows.
• For an overview of TIBCO Support Services, and information about getting
started with TIBCO Product Support, visit this site:
http://www.tibco.com/services/support/default.jsp
• If you already have a valid maintenance or support contract, visit this site:
http://support.tibco.com
Entry to this site requires a username and password. If you do not have a
username, you can request one.
This chapter includes an overview of the installer program and introduces the
TIBCO Runtime Agent product suite.
The TIBCO Runtime Agent Administrator’s Guide contain a list of the products and
product components installed by this installer, and the files and folders where
they are installed for the different platforms.
Topics
Introduction
Two installation packages are available for TIBCO Runtime Agent. One includes
only TIBCO Runtime Agent software and the other contains TIBCO Runtime
Agent and the TIBCO Adapter SDK libraries with a number of tools, libraries, and
other software that is required or useful during development of a TIBCO Adapter.
For both installation packages, it is recommended you perform a typical
installation, which includes all products and product components, as follows:
• TIBCO Designer (designer\<version> folder)—GUI component used at
design-time to configure TIBCO Adapter instances and TIBCO BusinessWorks
processes.
• TIBCO Runtime Agent (tra\<version> folder)—Contains the TIBCO Adapter
SDK runtime libraries and other TIBCO libraries and tools. This folder also
includes the TIBCO Wrapper utility, a number of repository management
utilities, and more.
• Third-party libraries (tpcl\<version> folder)—Contains third-party libraries.
For a complete list, see the TIBCO Runtime Agent readme.txt in the
tra\<version>\doc\tra folder.
Installer Overview
The TIBCO Installer allows you to run in different modes. Each mode is
supported on all platforms.
• GUI mode
• Console mode
• Silent mode
GUI Mode
In GUI mode, the installer presents panels that allow you to make choices about
product selection, product location, and so on. GUI mode is the installer’s default
mode, it is used, for example, when you invoke the installer by double-clicking on
the icon in Microsoft Windows.
Console Mode
Console mode allows you to run the installer from the command line. This is
useful if your machine does not have a Windows environment.
When running in Console mode, you can move through the installation process
using the following keys:
• Enter key—Moves forward in the installer
• 2—Goes back to previous screen
• 3—Cancels the Installer and exists the installation or uninstallation
• 4—Redisplays the current screen.
Silent Mode
Silent mode either installs using the default settings or uses a response file that
was saved during an earlier installation. Silent mode installs without prompting
you for information.
• If no response file has been recorded earlier and you invoke the installer with
the -silent argument, the default installation parameters are used.
On Microsoft Windows, you will see two GUI screens in silent mode if you install
with -a -silent. You will see only one GUI screen if you install with
-is:silent -a -silent.
If you install a product and that product is already installed on your machine, you
cannot choose a different location. If you wish to install the product in a different
location, you must completely remove the product from the machine.
Hotfix Libraries
TIBCO Runtime Agent 5.x hotfix libraries, jars and other files are installed under
the hotfix folder. If you install a hotfix, you must ensure that the
<tra_home>/hotfix/bin location is specified before the <tra_home>/bin and
<tra_home>/lib in your PATH, CLASSPATH, SHLIB_PATH or LD_LIBRARY_PATH, .tra
file (if used) and so on. This allows your applications to use the hotfix files.
Do not edit, modify, rename, move, or remove any of the registry vpd files.
UNIX Platforms
If installation is performed by a regular user (non-root), the installation registry is
maintained in the following files in the user's home directory:
User_Home_Directory/vpd.properties
User_Home_Directory/vpd.properties.tibco.systemName
If installation is performed by super-user (root), the installation registry is
maintained as follows:
• On Solaris and HP-UX, in the root user’s home directory (which is /) as vpd
files.
• On Linux, in the /root directory as vpd files.
• On AIX, in the /usr/lib/objrepos directory as vpd files.
The installer can also use a JVM if the version it requires is available on your
system. In that case, the bundled JVM is not extracted and significantly less disk
space is required.
On UNIX platforms the following disk space is required in the temporary area:
• On Solaris, 50 MB of free disk space in /var/tmp.
• On HP-UX, 85 MB of free disk space in /var/tmp.
• On AIX, 30 MB of free disk space in /tmp.
• On Linux, 50 MB of free disk space in /tmp.
• On Tru64, 65 MB of free disk space in the user’s home directory.
If your system does not have sufficient free disk space in the above temporary
area, you can still run the installer with a different temporary area by using the
following option when starting the installer:
-is:tempdir /new_tmp
Installation History
The installer creates a file called TIBCOInstallationHistory.xml in the location
where the installation registry is created. Each time an installation or
uninstallation is performed, entries are appended to the file.
On Windows: SystemDrive:\WINNT\TIBCOInstallationHistory.xml
On UNIX: Users_Home_Directory/TIBCOInstallationHistory.xml
The file will be used by the installer in future releases.
Topics
Installation Prerequisites
Table 1 Microsoft Windows: disk space, executable name, platforms and service packs
Microsoft 2
Windows 2000
Microsoft
Windows XP
Professional
Microsoft
Windows 2003
Installer Account
You must have administrator privileges to install this product.
The best way to install the TIBCO Runtime Agent on Windows Terminal Server is
to use the Add/Remove Programs control panel applet. This automatically sets
your mode to Install during the installation and then back to Execute afterwards.
Alternatively, you can manually change your mode to Install before starting the
installation by typing the following at a command prompt:
C:\> change user /install
Installation Options
If you are upgrading TIBCO Runtime Agent, or reinstalling a clean version of the
software, you may uninstall the product first or let the installer take care of
performing the upgrade or reinstall.
If any files are currently locked, the installer places them in a temporary location
and performs the actual upgrade the next time you reboot.
You can either download the TIBCO Runtime Agent installation package or
install the components from a CD. The installer prompts you to accept the license
agreement, then to choose to perform a typical install or custom install.
• A typical install has minimal prompts and installs standard components in
default locations.
• A custom install prompts you to choose which components of the product
suite to install and installs only those components.
If you are installing for the first time, you can specify the installation directory
where the products in this product suite will be installed. On Microsoft Windows,
the default installation directory is <system_drive>:\tibco.
The following sections discuss different installer options.
If you specify this option, you will still see one GUI screen before the rest of
installation proceeds in silence.
Combining Options
You can combine the different available options. For example, to install in silent
mode using a response file, use:
C:\> TIB_tra-suite_5.1.3_w32.exe -a -options <responseFileName>
-silent
Topics
Installation Prerequisites
Your operating system must meet the minimum patch requirements listed next. In
the package name column, the trasdk string indicates that TIBCO Adapter SDK
is bundled with TIBCO Runtime Agent. See Installer Disk Space Requirements in
Temporary Area on page 7 for additional disk space requirements.
Table 2 UNIX Systems: disk space, package names, platforms, and patches
Disk
Space Package Name Platform Minimum Patch(es)
(MB)
198 TIB_tra-suite_5.1.3_s4_57.tar Sun Solaris Minimum patches for 8: 108940-33
7, 8, 9 108773-12 108652-37 109740-04
TIB_trasdk-suite_5.1.3_s4_57. 109742-04 109279-18 108921-13
206
tar
Minimum patches for 7:
107544-03 106980-17 106950-16
108376-33 106300-12 106327-11
106541-18 107081-40 107636-08
107226-18 108374-05 107656-07
107702-09 107153-01
Make sure you have the latest J2SE
cluster patches:
http://sunsolve.sun.com/pub-
cgi/show.pl?target=patches/J
2SE
236 TIB_tra-suite_5.1.3_h7_110.ta HP-UX 11.0, Minimum patch for 11.0, 11i: 27282
r
11i
Make sure you have the latest J2SE
245 TIB_trasdk-suite_5.1.3_h7_110 1.4.1 required patches:
.tar
http://www.hp.com/products1/
unix/java/patches/index.html
Table 2 UNIX Systems: disk space, package names, platforms, and patches
Disk
Space Package Name Platform Minimum Patch(es)
(MB)
271 TIB_tra-suite_5.1.3_h7_ia64.t HP-UX 11i The C++ API supports both 32-bit
ar
v2 for Intel and 64-bit modes. The Java API
286 TIB_trasdk-suite_5.1.3_h7_ia6 Itanium 2 supports only the 32-bit mode.
4.tar
Note that TIBCO Rendezvous SSL
is not supported for the C++ API
using the 64-bit mode.
213 TIB_trasdk-suite_5.1.3_rs_51.
tar
Installer Account
TIBCO 5.x products can be installed by a regular (non-root) user and super-user
(root). Different users can install the same product at different locations.
Product dependencies at install time are resolved at user level through the
installation registry maintained at user's home directory. See Installation Registry
and History on page 6 for more information.
Windows Environment
A GUI environment such as CDE (that is, X Windows) is required to run the
installer in GUI mode. It is not required for a console or silent installation.
See DISPLAY Variable FAQ on page 29 for information about installing on UNIX
systems.
Installation Options
If you are upgrading TIBCO Runtime Agent, or reinstalling a clean version of the
software, you may uninstall the product first, or let the installer take care of
performing the update or reinstall.
If any files are currently locked, the installer places them in a temporary location
and performs the actual update the next time you reboot.
After unpacking the software and accepting the license agreement, you can
choose to perform a typical install or custom install.
• A typical install has minimal prompts and installs standard components in
default locations.
• A custom install prompts you to choose which pieces of the product suite to
install and installs only those components.
If you are installing for the first time, you must specify the installation directory
where the products in this product suite will be installed. The default installation
directory depends on who performs the installation:
• For non-root users, the default installation directory is /<myhome>/tibco,
where <myhome> is the home directory of the user.
• For root users, the default installation directory is /opt/tibco.
% ./TRA.5.1.3-suite_s4_57.bin
The response file does not record selections at the component level. For example,
it will not remember whether you chose to install documentation for a product. It
does record all other selections, for example, which products you wished to
install.
Combining Options
You can combine the different available options. For example, to install in silent
mode using a response file, use:
TRA.5.1.3-suite_s4_57.bin -silent -options <responseFileName>
Topics
Speeding Up Installation
The installer for TIBCO 5.x products is java-based and requires a Java Virtual
Machine (JVM) to launch. If the installer can use a JVM already on your system,
installation is faster and uses less disk space. Otherwise, the installer extracts JVM
from the installation package. This section explains where the installer searches
for JVM, and how you can add a different location to the search path.
Every 5.x product installer is bundled with the appropriate platform-specific JVM
version. When launched, the installer first searches for the appropriate JVM
version on the target system.
• If the installer finds the required JVM version, it uses that JVM to launch itself.
• If the installer does not find the required JVM version, it extracts the bundled
JVM into a temporary space and uses that JVM to launch itself.
The installer only searches for the JVM version 1.3.1 it requires. If a different JVM
version exists in the system, or is passed in using the environment variable or
command-line option, the installer ignores that JVM and extracts the bundled
JVM.
Location Description
Environment Set in ControlPanel, not in command prompt)
JAVA_HOME
JDKHOME
JVM 1.3.1
Registry \HKEY_LOCAL_MACHINE\SOFTWARE\
JavaSoft\Java Runtime Environment\
1.3\JavaHome \HKEY_LOCAL_MACHINE\SOFTWARE\
JavaSoft\ Java DevelopmentKit\1.3\JavaHome
Location Description
Environment JAVA_HOME
JDKHOME
Path /usr/jre1.3.1
/usr/java1.3.1
/usr/jdk1.3.1
/opt/jre1.3.1
/opt/java1.3.1
/opt/jdk1.3.1
Location Description
Environment JAVA_HOME
JDKHOME
Path /opt/java1.3
/opt/java1.3/jre
Location Description
Environment JAVA_HOME
JDKHOME
Location Description
Path /usr/jdk_base
/usr/jdk_base
/usr/java131
/usr/java131
Location Description
Environment JAVA_HOME
JDKHOME
Path /usr/jre1.3
/usr/local/jre1.3
/opt/jre1.3
/opt/j2re1.3.1
Location Description
Environment JAVA_HOME
JAVAHOME
JDKHOME
Path /usr/jre131
/opt/jre131
/usr/jdk131/jre
/opt/jdk131
/opt/jdk131/jre
The installer calculates the disk space required in product home location, for the
selected components. The calculation is done before the actual installation
(copying of files to system) begins. The installer will proceed only if sufficient free
disk space is available in product home location.
However, if disk space is consumed by another process while the installer is
copying the files, and if the required disk space is thereby reduced, then the
installer may fail, then the installer may fail and will give a failure message.
Solution
While performing installation, avoid running other processes that consume disk
space in product home location.
Why and how should I set the DISPLAY variable on UNIX platforms for GUI
mode?
The installer on UNIX, must open an additional window, generally for graphics. It
uses the DISPLAY environment variable to tell it on what computer to open the
window. If the environment variable is not set, the installer will either wait or
abort after displaying:
InstallShield Wizard
Initializing InstallShield Wizard...
Preparing Java(tm) Virtual Machine...
...................................
...................................
........
The DISPLAY variable must be set to the IP address or name of the computer (on
which the installer graphics window are to be displayed), followed by a screen
address, which can be :0.0. For example:
# Bourne shell
DISPLAY=<ip_address>:0.0; export DISPLAY
# Korn shell
export DISPLAY=<ip_address>:0.0
# C-shell
setenv DISPLAY <ip_address>:0.0
For example, consider a scenario where you need to install the adapter on a
remote HP-UX machine (named itaska). Because you have a Solaris 5.6 machine
(named alaska) that has a video card and monitor installed, you can run an
X-Window application on it. So you decide to telnet to itaska from alaska.
When you telnet to itaska, you will not get access to itaska's monitor and will
be unable to display an X-Window application. That is why you must set the
DISPLAY variable, which instructs the X-Server to redirect all windows to the
computer set in the variable. Before doing so, the computer (specified in the
DISPLAY variable) must give permissions to share its monitor.
Installation Crash
Installation on a HP-UX 11.00 64 bit system may crash with the following error
message:
Pid nnn killed due to trashed stack.
Pid nnn was killed due to failure in writing the signal context.
This happens only on HP-UX 11.00 64 bit systems. It does not happen on HP-UX
11.00 32 bit system and HP-UX 11.11 (or 11.i) system.
To determine the OS version on your system, run:
uname -a
Resolution
HP-UX kernel patch PHKL_27282, resolves the above crash.
To determine if your system has the kernel patch, run:
/usr/sbin/swlist -l product PHKL_27282
or
what /stand/vmunix | grep PHKL_27282
If your system is an HP-UX 11.00 64 bit system and it does not have the patch, first
install HP-UX kernel patch PHKL_27282 and then proceed with the installation.
Installation of patch PHKL_27282, will reboot your system.
Resolution
Install as non-root user.
The following error message may appear when installing on the Tru64 platform:
^D@AA: is not an identifier
Resolution
Installation on Tru64 requires POSIX compliant Bourne Shell.
Before you start the installation, set the following environment variable:
BIN_SH=xpg4; export BIN_SH // Bourne shell
On HP-UX and AIX platforms, even though the correct version of TIBCO
Runtime Agent version is already installed on the system, installation of a
product that depends on TIBCO Runtime Agent may fail in the dependency
resolution.
The TIBCO product installer maintains the registry information in the
vpd.properties.tibco.systemName file. The value for systemName is determined
by InetAddress.getLocalHost().getHostName(). However, the method
getHostName(), returns different values based on the JRE versions used. For
example, on AIX, JRE 1.3.1 returns only systemName, whereas JRE 1.4.0 returns
systemName.domainName. Because of this, the installer is not able to load the correct
registry file.
Resolution
On UNIX platforms, the installer registry file vpd.properties.tibco.systemName
is located in the user's home directory.
Case 1: If the vpd.properties.tibco.systemName file exists:
$ cd user's_home_directory
$ ln -s vpd.properties.tibco.systemName
vpd.properties.tibco.systemName.domainName
For example:
$ cd ~
$ ln -s vpd.properties.tibco.upside
vpd.properties.tibco.upside.tibco.com
For example:
$ cd ~
$ ln -s vpd.properties.tibco.upside.tibco.com
vpd.properties.tibco.upside