TRA_Installation

TIBCO Runtime Agent™

Installation GuideSoftware Release 5.1.3May 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiTIBCO Runtime Agent Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiOther Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

How to Contact TIBCO Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1 Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installer Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Installing Versions with Higher Version Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Installing in Non-Default Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Installing TIBCO Adapter 4.x or TIBCO BusinessWorks 2.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Uninstalling TIBCO Runtime Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Hotfix Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installation Registry and History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Microsoft Windows Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6UNIX Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Installation History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 Installation on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Installing on Windows 2000 and 2003 Terminal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Combining Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3 Installation on UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Installer Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Unpack the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Combining Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Post Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

TIBCO Runtime Agent Installation

iv | Contents

Chapter 4 Installation FAQs and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Speeding Up Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24How the Installer Searches for JVM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Speeding up JVM Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Benefits of Using Available JVM over Extracting Bundled JVM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25JVM Search Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Running Out of Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

DISPLAY Variable FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Installation on HP-UX 11.00 64 bit Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Setting Library Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Installation Crash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Installing as Root User Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Installation on Tru64 Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Cannot Install Dependent Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33


| v

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


vi | Tables


| vii

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, page viii

• How to Contact TIBCO Customer Support, page ix

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.


viii | Related Documentation

Related Documentation

This section lists documentation resources you may find useful.

TIBCO Runtime Agent DocumentationIn addition to this manual, TIBCO Runtime Agent software includes the following documents:

• TIBCO Runtime Agent Administrator’s Guide Read this guide for an overview about the TIBCO Runtime Agent components installed on your system.

• TIBCO Runtime Agent Release Notes Read the release notes for a list of new and changed features. This document also contains lists of known issues and closes issues for this release.

• TIBCO ActiveEnterprise Features, Migration and Compatibility Read this document for a summary of new features in release 5.1 and instructions on how to migrate 4.x projects to release 5.1.

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.


Preface | ix

How to Contact TIBCO Customer Support

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.


x | How to Contact TIBCO Customer Support


| 1

Chapter 1 Installation Overview

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

• Installer Overview, page 3

• Uninstalling TIBCO Runtime Agent, page 4

• Installation Registry and History, page 6

• Installation FAQs and Troubleshooting, page 23


2 | Chapter 1 Installation Overview

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.

• Java Runtime Agent (jre\<version> folder)

• TIBCO Rendezvous (tibrv folder)—Complete installation of TIBCO Rendezvous, as required by your installed TIBCO applications.

If you decide to perform a custom installation, and choose not to install one or more products or product components, you should review the list of required software for TIBCO Adapter SDK that is listed in the readme.txt file.


Installer Overview | 3

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.



• If a response file exists, and the installer is started with -options <responseFileName> as an argument, the installer uses the values specified by the user when the response file was generated.

Installing Versions with Higher Version NumbersTIBCO products use a three-digit release number which makes it possible to specify major, minor, and patch release. For example, release 2.1.3 uses major version 2, minor 1, and patch 3.

• If you are installing using a patch release (for example, 5.0.1 over 5.0.0), the installer will silently overwrite the existing version of the software. No interruptions to running software results.

• If you are installing using a major or minor release, the installer will create a new directory in the directory of the old installation that is named after the two-digit release number (e.g. 5.0). The old installation is not removed, and must be uninstalled separately if you wish to remove it.

Installing in Non-Default DirectoriesIt is recommended you install in the default directories. If you do, later installations and upgrade will work seamlessly.

Installing TIBCO Adapter 4.x or TIBCO BusinessWorks 2.xIf a TIBCO Adapter 4.x application or TIBCO BusinessWorks 2.x is installed after TIBCO Runtime Agent 5.1.3 is installed, you should choose the installation option to use the external TIBCO Rendezvous product installed by TIBCO Runtime Agent 5.1.3.

Uninstalling TIBCO Runtime AgentThe TIBCO Installation Manager allows you to:

• Display installed products

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.


Installer Overview | 5

• Display product components

• Display product dependencies and references

• Uninstall products and all references

To start the program:

• On Microsoft Windows:

Click Start>TIBCO>TIBCO Installation Manager

• On UNIX:

<install-path>/tibco/TibcoInstallationManager.bin

The TIBCO Installation Manager displays all TIBCO software installed on your machine. Details about the selected TIBCO product are displayed in the right rows. Click the Uninstall button to remove the selected product. Note that some products cannot be installed from the utility. Instructions about uninstalling these products are listed in the uninstall window (after clicking the Uninstall button).

Click the TIBCO Installation Manager help button for information about using the program.

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



Installation Registry and History

The installer maintains an installation registry. The registry location depends on the platform. This section explains where the registry files are located. The files have vpd as a prefix, which stands for Vital Product Database.

Microsoft Windows PlatformsAn installation registry is maintained in the SystemDrive:\WINNT folder. The following files represent the installation registry:

SystemDrive:\WINNT\vpd.propertiesSystemDrive:\WINNT\vpd.properties.tibco.systemName

Installer Disk Space Requirements in Temporary Area

The entire package is extracted into a temp folder, typically SystemDrive:\Temp or SystemDrive:\Documents and Settings\<user_name>\Local Settings\Temp.

The installer requires 152MB of free space in the temp directory.

UNIX PlatformsIf 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.propertiesUser_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.

Do not edit, modify, rename, move, or remove any of the registry vpd files.


Installation Registry and History | 7

Installer Disk Space Requirements in Temporary Area

The installer launcher first extracts the JVM in a temporary directory and uses this JVM to launch itself. The size of the extracted JVM differs from platform to platform.

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

where /new_tmp has sufficient free disk space.

For example, on Solaris: TRA.5.1.3-suite_s4_58.bin -is:tempdir /new_tmp

Disk Space Requirement in User's Home Directory

On UNIX platforms when a regular (non-root) user installs a TIBCO 5.x product, the installation registry (vpd files) is maintained in the user's home directory. As more products are installed, entries are added into these vpd files.

The user's home directory must at least have 500 KB of free disk space.

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

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.


| 9

Chapter 2 Installation on Microsoft Windows

This chapter explains how to install TIBCO Runtime Agent on Microsoft Windows platforms.

Topics

• Installation Prerequisites, page 10

• Installation Options, page 12


10 | Chapter 2 Installation on Microsoft Windows

Installation Prerequisites

The following is a list of prerequisites for installing TIBCO Runtime Agent on Windows systems. The following table lists the executable name for each package. The trasdk string indicates that TIBCO Adapter SDK is bundled with TRA software. See Installer Disk Space Requirements in Temporary Area on page 6 for additional disk space requirements.

Installer Account

You must have administrator privileges to install this product.

Installing to a Networked Drive

If you intend to install the product onto a networked drive, you must have permissions to write to that drive.

If you do not know how to do this, go to the machine so you can install locally, or consult Microsoft Windows online help.

Table 1 Microsoft Windows: disk space, executable name, platforms and service packs

Disk Space Executable Name Platforms Service Pack

197 TIB_tra-suite_5.1.3_w32.exe

206 TIB_trasdk-suite_5.1.3_w32.exe

Microsoft Windows NT

6

Microsoft Windows 2000

2

Microsoft Windows XP Professional

Microsoft Windows 2003


Installation Prerequisites | 11

Installing on Windows 2000 and 2003 Terminal ServerThere are two modes in Windows Terminal Server: Execute and Install. Users are logged on by default in Execute mode, which allows them to run applications. To install an adapter so that everyone can use it, log on as administrator in Install mode. When the adapter is installed in the Install mode, the installation registry is maintained in SystemDrive:\WINNT\.

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

Change back to Execute mode after installation is complete by typing:

C:\> change user /execute

To check your current mode, type the following:

C:\> change user /query

Windows Terminal Server must be running in remote admin mode, not application sharing mode. TIBCO Runtime Agent is not supported if installed on a machine that is using Windows Terminal Server in application sharing mode.



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.

Install Using GUI Mode

GUI mode allows you input values in panels. Type the following at the command prompt:

C:\> TIB_tra-suite_5.1.3_w32.exe

Install Using Console Mode

Console mode allows you to install the software in a non-windows environment. The installer will prompt you for values. Type the following at the command prompt:

C:\> TIB_tra-suite_5.1.3_w32.exe -a -is:javaconsole -console

Install Using Silent Mode With Default Values

Silent mode allows you to install the software without prompts. Type the following at the command prompt:


Installation Options | 13

C:\> TIB_tra-suite_5.1.3_w32.exe -is:silent -a -silent

Install Using a Response File

You can use a previously generated response file for installation. For non-silent modes, the response file determines the defaults that are presented. For silent mode, the response file determines what will be installed.

To install using a response file, type the following at the command prompt: C:\> TIB_tra-suite_5.1.3_w32.exe -a -options

C:\directory\<responseFileName>

Combining OptionsYou 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

To install using Console mode and generate a response file, use: C:\> TIB_tra-suite_5.1.3_w32.exe -a -is:javaconsole -console -options-record <responseFileName>

If you specify this option, you will still see one GUI screen before the rest of installation proceeds in silence.


| 15

Chapter 3 Installation on UNIX Systems

This chapter explains how to install TRA on UNIX systems.

Topics

• Installation Prerequisites, page 16

• Installation Options, page 18


16 | Chapter 3 Installation on UNIX Systems

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 (MB)

Package Name Platform Minimum Patch(es)

198 TIB_tra-suite_5.1.3_s4_57.tar Sun Solaris 7, 8, 9

Minimum patches for 8: 108940-33 108773-12 108652-37 109740-04 109742-04 109279-18 108921-13

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/J2SE

Solaris font package requirements:

http://java.sun.com/j2se/1.4.1/font-requirements.html

206 TIB_trasdk-suite_5.1.3_s4_57.tar

236 TIB_tra-suite_5.1.3_h7_110.tar

HP-UX 11.0, 11i

Minimum patch for 11.0, 11i: 27282

Make sure you have the latest J2SE 1.4.1 required patches:

http://www.hp.com/products1/unix/java/patches/index.html

245 TIB_trasdk-suite_5.1.3_h7_110.tar


Installation Prerequisites | 17

Installer AccountTIBCO 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 EnvironmentA 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.

271 TIB_tra-suite_5.1.3_h7_ia64.tar

HP-UX 11i v2 for Intel Itanium 2

The C++ API supports both 32-bit and 64-bit modes. The Java API supports only the 32-bit mode.

Note that TIBCO Rendezvous SSL is not supported for the C++ API using the 64-bit mode.

286 TIB_trasdk-suite_5.1.3_h7_ia64.tar

190 TIB_trasdk-suite_5.1.3_alpha_51.tar

HP Tru 64 UNIX 5.1A

198 TIB_tra-suite_5.1.3_alpha_51.tar

204 TIB_tra-suite_5.1.3_rs_51.tar IBM AIX 5.1 Maintenance Level 5100-02

213 TIB_trasdk-suite_5.1.3_rs_51.tar

189 TIB_tra-suite_5.1.3_lnx86_24.tar

Linux AS 2.1

197 TIB_trasdk-suite_5.1.3_lnx86_24.tar

Table 2 UNIX Systems: disk space, package names, platforms, and patches

Disk Space (MB)

Package Name Platform Minimum Patch(es)

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.

Unpack the SoftwareYou can either download the TIBCO Runtime Agent installation package or install the components from a CD.

To start installation:

1. Log in to the system and start a terminal window. These instructions assume that a C-shell (csh) is being used in the terminal window.

2. Locate and unpack the TIBCO Runtime Agent distribution file, which is named after the operating system you are using, at the shell prompt (shown here as %). This example assumes the file is in the current directory and that you are installing on Solaris 8:

% tar -xvf TIB_tra-suite_5.1.3_s4_57.tar

The installer program is extracted into the current directory.

Use one of the following modes to install the software.


Installation Options | 19

Install Using GUI Mode

GUI mode allows you input values in panels. Type the following in a terminal window:

% ./TRA.5.1.3-suite_s4_57.bin

Install Using Console Mode

Console mode allows you to install the software in a non windows environment. The installer will prompt you for values. Type the following in a terminal window:

% ./TRA.5.1.3-suite_s4_57.bin -is:javaconsole -console

Install Using Silent Mode with Default Values

Silent mode allows you to install the software without prompts using default values. Type the following in a terminal window:

% ./TRA.5.1.3-suite_s4_57.bin -silent

Install and Generate a Response File

You can generate a response file during installation which you can later use to invoke the installer with the selected values as default values (GUI mode) or as selected values (silent mode).

To install and generate a response file, type the following at the command prompt:

% TRA.5.1.3-suite_s4_57.bin -options-record /dir/<responseFile>

Install Using a Response File

You can use a previously generated response file for installation. For non-silent modes, the response file determines the defaults that are presented. For silent mode, the response file determines what will be installed.

To install using a response file, type the following at the command prompt: % TRA.5.1.3-suite_s4_57.bin -options /dir/<responseFileName>

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

To install using Console mode and generate a response file, use: TRA.5.1.3-suite_s4_57.bin -is:javaconsole -console -options-record <responseFileName>


Post Installation Requirements | 21

Post Installation Requirements

All UNIX Platforms

After installation on UNIX platforms, the root user must modify the permissions of the Hawk HMA (tibhawkhma).

cd $TIBCO_HAWK_HOME/bin/tibhawkhmachown root tibhawkhmachmod g+s tibhawkhma

HP Tru 64 UNIX 5.1A Platform

After installing TIBCO Runtime Agent on the HP Tru 64 UNIX 5.1A platform, you must create the following symbolic link:

> ln -s $TIBCO_RV_HOME/lib/libtibrvjsd.so $TIBCO_RV_HOME/lib/libtibrvjsd64.so


| 23

Chapter 4 Installation FAQs and Troubleshooting

This chapter lists answers to questions and potential issues.

Topics

• Speeding Up Installation, page 24

• Running Out of Disk Space, page 28

• DISPLAY Variable FAQ, page 29

• Installation on HP-UX 11.00 64 bit Platform, page 30

• Installation on Tru64 Platform, page 32

• Cannot Install Dependent Product, page 33


24 | Chapter 4 Installation FAQs and Troubleshooting

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.

How the Installer Searches for JVMThe installer by default searches for an appropriate JVM version in a set of standard locations. These standard locations are platform specific and are listed in JVM Search Locations on page 25. On each platform, the installer searches for version for JVM 1.3.1 only.

Speeding up JVM SearchYou can speed up the JVM search by taking one of these actions before you launch the installer:

• Set the environment variable JAVA_HOME or JDKHOME to the JVM home directory, for example:

UNIX Bourne or Korn shell:

JAVA_HOME=/opt/jre1.3.1; export JAVA_HOME

UNIX C-shell setenv JAVA_HOME /opt/jre1.3.1

Microsoft Windows

1. Choose Start->Settings->Control Panel->System-Environment->System Variable or User Variables

2. Add a JAVA_HOME variable and set its value

NOTE: On Microsoft Windows, setting JAVA_HOME in a command prompt will not be effective.


Speeding Up Installation | 25

• Include a command line option -is:javahome when launching the installer. For example:

Benefits of Using Available JVM over Extracting Bundled JVM • JVM search is quick. It is searched for in well-defined locations. It can be sped

up by setting an environment variable or by using a command line option.

• Extraction of bundled JVM is avoided, which saves both time and temporary disk space. Initial loading of installer is faster.

• If the bundled JVM is extracted and used for launching the installer, then a copy of this JVM is installed for launching the uninstaller in the _jvm directory in the product location.

However, if JVM was resolved through JVM search, the uninstaller just points to this JVM and uses it later to launch itself. In this case, JVM is not installed. This is a major benefit in terms of disk space.

For example, on HP-UX, the size of JVM 1.3.1 is about 80 MB. When the TIBCO Runtime Agent (TRA) suite is installed, and if the bundled JVM is used for launching the installer, a copy of JVM 1.3.1 is installed for each of the five products in the suite. This results in an additional 400 MB of disk space used. If a local JVM can be used, these 400 MB are not needed.

• If the JVM the uninstaller points to is removed at any time, you can still run the uninstaller using the -is:javahome option to point to a different JVM location.

JVM Search LocationsThe following tables list the search locations for the different platforms.

Windows suite installer

<exe> -a -is:javahome c:\java\JRE\1.3.1

Other installers <exe_or_bin> -is:javahome /opt/jre1.3.1

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.



Table 3 Windows (JVM 1.3.1)

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

Directory \Program Files\JavaSoft\JRE\1.3.1\JavaSoft\JRE\1.3.1 \Java\JRE\1.3.1

Table 4 Solaris (JVM 1.3.1)


Environment JAVA_HOMEJDKHOME

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

Table 5 HP-UX (JVM 1.3.1)


Environment JAVA_HOME

JDKHOME

Path /opt/java1.3

/opt/java1.3/jre

Table 6 AIX (JVM 1.3.1)


Environment JAVA_HOME JDKHOME


Speeding Up Installation | 27

Path /usr/jdk_base/usr/jdk_base /usr/java131 /usr/java131

Table 7 Linux (JVM 1.3.1)


Environment JAVA_HOME JDKHOME

Path /usr/jre1.3 /usr/local/jre1.3 /opt/jre1.3 /opt/j2re1.3.1

Table 8 Tru64 (JVM 1.3.1)


Environment JAVA_HOMEJAVAHOMEJDKHOME

Path /usr/jre131/opt/jre131/usr/jdk131/jre/opt/jdk131/opt/jdk131/jre

Table 6 AIX (JVM 1.3.1)




Running Out of Disk Space

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.


DISPLAY Variable FAQ | 29

DISPLAY Variable FAQ

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 WizardInitializing 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 shellDISPLAY=<ip_address>:0.0; export DISPLAY

# Korn shellexport DISPLAY=<ip_address>:0.0

# C-shellsetenv 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.

alaska> xhost + # give permission for all to its share monitoralaska> telnet itaskaWelcome to HP-UX itaska 11.00User:Password:itaska> export DISPLAY=alaska:0.0 # set display on alaskaitaska> ./TIB_tra-suite_5.1.3_h7_110.bin



Installation on HP-UX 11.00 64 bit Platform

Setting Library PathOn HP-UX, you need to manually set the SHLIB_PATH before you start TIBCO Administrator, as follows:

<TIBCO_HOME>/jre/1.4.1/PA_RISC2.0/hotspot:<TIBCO_HOME>/jre/1.4.1/PA_RISC2.0:$SHLIB_PATH

Installation CrashInstallation 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

To determine the kernel bits on your system, run:

getconf KERNEL_BITS

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.


Installation on HP-UX 11.00 64 bit Platform | 31

Installing as Root User ErrorWhen installing as root user on HP-UX, you may get the following error:

Assertion failed: so->so_hard_contents, file softobj.c, line 363

Resolution

Install as non-root user.



Installation on Tru64 Platform

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

setenv BIN_SH xpg4 // C-shell


Cannot Install Dependent Product | 33

Cannot Install Dependent Product

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

where upside is systemName, and tibco.com is domainName

Case 2: If the vpd.properties.tibco.systemName.domainName file exists:

$ cd user's_home_directory$ ln -s vpd.properties.tibco.systemName.domainName vpd.properties.tibco.systemName

For example:

$ cd ~$ ln -s vpd.properties.tibco.upside.tibco.com vpd.properties.tibco.upside

where upside is systemName, and tibco.com is domainName.


TRA_Installation

Documents

Transcript of TRA_Installation