page viii How to Contact TIBCO Customer Support. Please see the readme. Contact information for TIBCO support is also listed.
Topics
• • Related Documentation. not all operating system platforms for a specific software version are released at the same time. However. page ix
TIBCO Runtime Agent Installation
. The preface lists the TIBCO Runtime Agent documentation set and other related TIBCO documentation.| vii
Preface
This software may be available on multiple operating systems.txt file for the availability of this software version on a specific operating system platform.

•
TIBCO Runtime Agent Installation
.viii
| Related Documentation
Related Documentation
This section lists documentation resources you may find useful.
TIBCO Runtime Agent Documentation
In addition to this manual. Each adapter includes the TIBCO Adapter Concepts Guide. Most adapters also include an Examples guide. 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. the following Adapter SDK documents are included in the <install-path>\tibco\tra\5. TIBCO Designer includes online help for each palette. You will therefore find TIBCO Adapter product documentation useful. You will therefore find the TIBCO Designer documentation useful. TIBCO Runtime Agent Release Notes Read the release notes for a list of new and changed features. TIBCO ActiveEnterprise Features. If you are using the TIBCO Runtime Agent and TIBCO Adapter SDK suite. This document also contains lists of known issues and closes issues for this release.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. a User’s Guide and Release Notes. Migration and Compatibility Read this document for a summary of new features in release 5.1 and instructions on how to migrate 4.
•
Other Documentation
• TIBCO Runtime Agent includes TIBCO Designer.x projects to release 5. TIBCO Designer is an easy to use graphical user interface for design-time configuration of TIBCO applications.1.

Preface ix
|
How to Contact TIBCO Customer Support
For comments or problems with this manual or the software it addresses.tibco. If you do not have a username. and information about getting started with TIBCO Product Support.jsp • If you already have a valid maintenance or support contract.
TIBCO Runtime Agent Installation
. visit this site: http://www. you can request one. • For an overview of TIBCO Support Services.com Entry to this site requires a username and password. visit this site: http://support.com/services/support/default. please contact TIBCO Support Services as follows.tibco.

page 23
TIBCO Runtime Agent Installation
. page 3 Uninstalling TIBCO Runtime Agent.|1
Chapter 1
Installation Overview
This chapter includes an overview of the installer program and introduces the TIBCO Runtime Agent product suite.
Topics
• • • • Installer Overview. page 6 Installation FAQs and Troubleshooting. and the files and folders where they are installed for the different platforms. The TIBCO Runtime Agent Administrator’s Guide contain a list of the products and product components installed by this installer. page 4 Installation Registry and History.

which includes all products and product components. you should review the list of required software for TIBCO Adapter SDK that is listed in the readme. TIBCO Runtime Agent (tra\<version> folder)—Contains the TIBCO Adapter SDK runtime libraries and other TIBCO libraries and tools. and other software that is required or useful during development of a TIBCO Adapter. This folder also includes the TIBCO Wrapper utility. as follows: • TIBCO Designer (designer\<version> folder)—GUI component used at design-time to configure TIBCO Adapter instances and TIBCO BusinessWorks processes. as required by your installed TIBCO applications.
TIBCO Runtime Agent Installation
. it is recommended you perform a typical installation. Third-party libraries (tpcl\<version> folder)—Contains third-party libraries.
•
•
• •
If you decide to perform a custom installation. 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 choose not to install one or more products or product components.2
| Chapter 1
Installation Overview
Introduction
Two installation packages are available for TIBCO Runtime Agent. For both installation packages. and more. see the TIBCO Runtime Agent readme. Java Runtime Agent (jre\<version> folder) TIBCO Rendezvous (tibrv folder)—Complete installation of TIBCO Rendezvous. a number of repository management utilities.txt in the tra\<version>\doc\tra folder.txt file. For a complete list.

• If no response file has been recorded earlier and you invoke the installer with the -silent argument. Console Mode Console mode allows you to run the installer from the command line. GUI mode is the installer’s default mode.
3—Cancels
4—Redisplays
Silent Mode Silent mode either installs using the default settings or uses a response file that was saved during an earlier installation. This is useful if your machine does not have a Windows environment. • • • GUI mode Console mode Silent mode
GUI Mode In GUI mode. it is used. and so on. product location. Each mode is supported on all platforms. the default installation parameters are used. when you invoke the installer by double-clicking on the icon in Microsoft Windows. the installer presents panels that allow you to make choices about product selection. Silent mode installs without prompting you for information. you can move through the installation process using the following keys: • • • •
Enter key—Moves 2—Goes
forward in the installer
back to previous screen the Installer and exists the installation or uninstallation the current screen. for example. When running in Console mode.
TIBCO Runtime Agent Installation
.Installer Overview 3
|
Installer Overview
The TIBCO Installer allows you to run in different modes.

x application or TIBCO BusinessWorks 2.
Installing TIBCO Adapter 4. No interruptions to running software results. 5. you must completely remove the product from the machine.x is installed after TIBCO Runtime Agent 5. and must be uninstalled separately if you wish to remove it. You will see only one GUI screen if you install with
-is:silent -a -silent. and patch 3.0). 5. For example.3.
•
If you install a product and that product is already installed on your machine.1.
On Microsoft Windows. later installations and upgrade will work seamlessly.
Installing Versions with Higher Version Numbers
TIBCO products use a three-digit release number which makes it possible to specify major. If you do.3 uses major version 2. If you are installing using a major or minor release.4
| Chapter 1
Installation Overview
•
If a response file exists. minor 1.x
If a TIBCO Adapter 4. • If you are installing using a patch release (for example.x or TIBCO BusinessWorks 2.1.3 is installed.1 over 5. minor.0. you cannot choose a different location. and the installer is started with -options <responseFileName> as an argument.1. release 2.
Installing in Non-Default Directories
It is recommended you install in the default directories. you will see two GUI screens in silent mode if you install with -a -silent.0.g. The old installation is not removed. the installer will create a new directory in the directory of the old installation that is named after the two-digit release number (e.
Uninstalling TIBCO Runtime Agent
The TIBCO Installation Manager allows you to: • Display installed products
TIBCO Runtime Agent Installation
.0). you should choose the installation option to use the external TIBCO Rendezvous product installed by TIBCO Runtime Agent 5. the installer will silently overwrite the existing version of the software. the installer uses the values specified by the user when the response file was generated. If you wish to install the product in a different location. and patch release.

jars and other files are installed under the hotfix folder.
Hotfix Libraries
TIBCO Runtime Agent 5. Instructions about uninstalling these products are listed in the uninstall window (after clicking the Uninstall button).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.
TIBCO Runtime Agent Installation
. Click the Uninstall button to remove the selected product. you must ensure that the <tra_home>/hotfix/bin location is specified before the <tra_home>/bin and <tra_home>/lib in your PATH.tra file (if used) and so on.x hotfix libraries. This allows your applications to use the hotfix files. Note that some products cannot be installed from the utility.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. SHLIB_PATH or LD_LIBRARY_PATH. CLASSPATH. Click the TIBCO Installation Manager help button for information about using the program. If you install a hotfix. .

move. Do not edit.properties. The installer requires 152MB of free space in the temp directory. in the /root directory as vpd files. typically SystemDrive:\Temp or SystemDrive:\Documents and Settings\<user_name>\Local Settings\Temp. which stands for Vital Product Database.tibco.systemName
If installation is performed by super-user (root). On Linux. On AIX.tibco. or remove any of the registry vpd files. This section explains where the registry files are located. The files have vpd as a prefix.properties SystemDrive:\WINNT\vpd.properties. modify.
Microsoft Windows Platforms
An installation registry is maintained in the SystemDrive:\WINNT folder. The following files represent the installation registry:
SystemDrive:\WINNT\vpd. the installation registry is maintained as follows: • • • On Solaris and HP-UX. in the /usr/lib/objrepos directory as vpd files.systemName
Installer Disk Space Requirements in Temporary Area The entire package is extracted into a temp folder.6
| Chapter 1
Installation Overview
Installation Registry and History
The installer maintains an installation registry. the installation registry is maintained in the following files in the user's home directory:
User_Home_Directory/vpd. The registry location depends on the platform.
UNIX Platforms
If installation is performed by a regular user (non-root). in the root user’s home directory (which is /) as vpd files.properties User_Home_Directory/vpd. rename.
TIBCO Runtime Agent Installation
.

The user's home directory must at least have 500 KB of free disk space. On Linux.x product.xml in the location where the installation registry is created. The size of the extracted JVM differs from platform to platform.xml On UNIX: Users_Home_Directory/TIBCOInstallationHistory.bin Disk Space Requirement in User's Home Directory On UNIX platforms when a regular (non-root) user installs a TIBCO 5.3-suite_s4_58. on Solaris: TRA.xml The file will be used by the installer in future releases.
TIBCO Runtime Agent Installation
.1. Each time an installation or uninstallation is performed.5. As more products are installed.
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. On UNIX platforms the following disk space is required in the temporary area: • • • • • On Solaris. 65 MB of free disk space in the user’s home directory. the bundled JVM is not extracted and significantly less disk space is required. For example.
-is:tempdir /new_tmp
Installation History
The installer creates a file called TIBCOInstallationHistory. entries are added into these vpd files. The installer can also use a JVM if the version it requires is available on your system. 50 MB of free disk space in /tmp.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. On HP-UX. 50 MB of free disk space in /var/tmp. On Tru64. In that case. On Windows: SystemDrive:\WINNT\TIBCOInstallationHistory. On AIX. 85 MB of free disk space in /var/tmp. 30 MB of free disk space in /tmp. entries are appended to the file. the installation registry (vpd files) is maintained in the user's home directory.

3_w32.3_w32.exe
Platforms Microsoft Windows NT Microsoft Windows 2000 Microsoft Windows XP Professional Microsoft Windows 2003
Service Pack 6 2
Installer Account You must have administrator privileges to install this product. platforms and service packs Disk Space 197 206 Executable Name
TIB_tra-suite_5.1. 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. Installing to a Networked Drive If you intend to install the product onto a networked drive. or consult Microsoft Windows online help. you must have permissions to write to that drive.10
| Chapter 2
Installation on Microsoft Windows
Installation Prerequisites
The following is a list of prerequisites for installing TIBCO Runtime Agent on Windows systems.exe TIB_trasdk-suite_5.
TIBCO Runtime Agent Installation
. The following table lists the executable name for each package.1. Table 1 Microsoft Windows: disk space. go to the machine so you can install locally. executable name. If you do not know how to do this.

This automatically sets your mode to Install during the installation and then back to Execute afterwards. type the following:
C:\> change user /query
TIBCO Runtime Agent Installation
. Windows Terminal Server must be running in remote admin mode. the installation registry is maintained in SystemDrive:\WINNT\. which allows them to run applications. log on as administrator in Install mode. Users are logged on by default in Execute mode. The best way to install the TIBCO Runtime Agent on Windows Terminal Server is to use the Add/Remove Programs control panel applet.Installation Prerequisites 11
|
Installing on Windows 2000 and 2003 Terminal Server
There are two modes in Windows Terminal Server: Execute and Install. TIBCO Runtime Agent is not supported if installed on a machine that is using Windows Terminal Server in application sharing mode. Alternatively. To install an adapter so that everyone can use it. 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. When the adapter is installed in the Install mode. not application sharing mode.

On Microsoft Windows.1.exe
Install Using Console Mode Console mode allows you to install the software in a non-windows environment.12
| Chapter 2
Installation on Microsoft Windows
Installation Options
If you are upgrading TIBCO Runtime Agent. If any files are currently locked.3_w32. then to choose to perform a typical install or custom install. you may uninstall the product first or let the installer take care of performing the upgrade or reinstall.
If you are installing for the first time. The following sections discuss different installer options. the installer places them in a temporary location and performs the actual upgrade the next time you reboot. The installer will prompt you for values.exe -a -is:javaconsole -console
Install Using Silent Mode With Default Values Silent mode allows you to install the software without prompts. A custom install prompts you to choose which components of the product suite to install and installs only those components. • • A typical install has minimal prompts and installs standard components in default locations. Install Using GUI Mode GUI mode allows you input values in panels.3_w32. or reinstalling a clean version of the software. Type the following at the command prompt:
TIBCO Runtime Agent Installation
. Type the following at the command prompt:
C:\> TIB_tra-suite_5. you can specify the installation directory where the products in this product suite will be installed. the default installation directory is <system_drive>:\tibco.1. The installer prompts you to accept the license agreement. Type the following at the command prompt:
C:\> TIB_tra-suite_5. You can either download the TIBCO Runtime Agent installation package or install the components from a CD.

For example. the response file determines the defaults that are presented. type the following at the command prompt:
C:\> TIB_tra-suite_5. to install in silent mode using a response file.3_w32.3_w32.Installation Options 13
|
C:\> TIB_tra-suite_5.1. use:
C:\> TIB_tra-suite_5.1.exe -is:silent -a -silent
If you specify this option.3_w32. Install Using a Response File You can use a previously generated response file for installation.exe -a -is:javaconsole -console -options-record <responseFileName>
TIBCO Runtime Agent Installation
. you will still see one GUI screen before the rest of installation proceeds in silence.exe -a -options <responseFileName> -silent
To install using Console mode and generate a response file. use:
C:\> TIB_tra-suite_5. the response file determines what will be installed.3_w32. For silent mode. For non-silent modes.exe -a -options C:\directory\<responseFileName>
Combining Options
You can combine the different available options.1. To install using a response file.1.

18
| Chapter 3
Installation on UNIX Systems
Installation Options
If you are upgrading TIBCO Runtime Agent. where <myhome> is the home directory of the user. the default installation directory is /opt/tibco. you can choose to perform a typical install or custom install. This example assumes the file is in the current directory and that you are installing on Solaris 8:
% tar -xvf TIB_tra-suite_5. at the shell prompt (shown here as %). you must specify the installation directory where the products in this product suite will be installed. Use one of the following modes to install the software.3_s4_57. For root users. 2. or reinstalling a clean version of the software. These instructions assume that a C-shell (csh) is being used in the terminal window. the installer places them in a temporary location and performs the actual update the next time you reboot.tar
The installer program is extracted into the current directory. 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 may uninstall the product first. The default installation directory depends on who performs the installation: • • For non-root users. the default installation directory is /<myhome>/tibco.
TIBCO Runtime Agent Installation
.1. To start installation: 1. or let the installer take care of performing the update or reinstall. which is named after the operating system you are using. If any files are currently locked. • • A typical install has minimal prompts and installs standard components in default locations. Locate and unpack the TIBCO Runtime Agent distribution file.
Unpack the Software
You can either download the TIBCO Runtime Agent installation package or install the components from a CD. Log in to the system and start a terminal window. After unpacking the software and accepting the license agreement.

bin -is:javaconsole -console
Install Using Silent Mode with Default Values Silent mode allows you to install the software without prompts using default values.1.Installation Options 19
|
Install Using GUI Mode GUI mode allows you input values in panels.1. which products you wished to install. The installer will prompt you for values.5.3-suite_s4_57.5. It does record all other selections.3-suite_s4_57.bin -options /dir/<responseFileName>
TIBCO Runtime Agent Installation
.5.5.bin
Install Using Console Mode Console mode allows you to install the software in a non windows environment. To install using a response file. for example.1.3-suite_s4_57.5.1.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). Type the following in a terminal window:
% . Type the following in a terminal window:
% .3-suite_s4_57. For example. the response file determines what will be installed. For silent mode. the response file determines the defaults that are presented. Install Using a Response File You can use a previously generated response file for installation./TRA.bin -options-record /dir/<responseFile>
The response file does not record selections at the component level./TRA.3-suite_s4_57. To install and generate a response file. Type the following in a terminal window:
% ./TRA. For non-silent modes. it will not remember whether you chose to install documentation for a product.1. type the following at the command prompt:
% TRA. type the following at the command prompt:
% TRA.

When launched.x product installer is bundled with the appropriate platform-specific JVM version. • • If the installer finds the required JVM version. If the installer does not find the required JVM version. the installer first searches for the appropriate JVM version on the target system. On each platform. export JAVA_HOME
UNIX Bourne or Korn shell: UNIX C-shell Microsoft Windows
setenv JAVA_HOME /opt/jre1.
How the Installer Searches for JVM
The installer by default searches for an appropriate JVM version in a set of standard locations.3. the installer extracts JVM from the installation package. and how you can add a different location to the search path. Choose Start->Settings->Control Panel->System-Environment->System Variable or User Variables 2. installation is faster and uses less disk space. it uses that JVM to launch itself.1.3. Add a JAVA_HOME variable and set its value NOTE: On Microsoft Windows.x products is java-based and requires a Java Virtual Machine (JVM) to launch. it extracts the bundled JVM into a temporary space and uses that JVM to launch itself. Otherwise. setting JAVA_HOME in a command prompt will not be effective.1 only.1
1.24
| Chapter 4
Installation FAQs and Troubleshooting
Speeding Up Installation
The installer for TIBCO 5.
Speeding up JVM Search
You 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.3. These standard locations are platform specific and are listed in JVM Search Locations on page 25. Every 5. If the installer can use a JVM already on your system. the installer searches for version for JVM 1. This section explains where the installer searches for JVM. for example:
JAVA_HOME=/opt/jre1.
TIBCO Runtime Agent Installation
.

For example. • If the JVM the uninstaller points to is removed at any time. on HP-UX. If a local JVM can be used.3. The installer only searches for the JVM version 1. if JVM was resolved through JVM search. you can still run the uninstaller using the -is:javahome option to point to a different JVM location.
JVM Search Locations
The following tables list the search locations for the different platforms.1 is about 80 MB. It can be sped up by setting an environment variable or by using a command line option.3.1 is installed for each of the five products in the suite.1
Benefits of Using Available JVM over Extracting Bundled JVM
• • • JVM search is quick. which saves both time and temporary disk space.1 it requires. JVM is not installed.
Windows suite installer Other installers
<exe> -a -is:javahome c:\java\JRE\1.3. a copy of JVM 1. If a different JVM version exists in the system. It is searched for in well-defined locations.3. or is passed in using the environment variable or command-line option. the uninstaller just points to this JVM and uses it later to launch itself. This results in an additional 400 MB of disk space used. If the bundled JVM is extracted and used for launching the installer. When the TIBCO Runtime Agent (TRA) suite is installed.1
<exe_or_bin> -is:javahome /opt/jre1. these 400 MB are not needed.
TIBCO Runtime Agent Installation
. In this case. This is a major benefit in terms of disk space. the size of JVM 1. Extraction of bundled JVM is avoided. and if the bundled JVM is used for launching the installer. the installer ignores that JVM and extracts the bundled JVM. then a copy of this JVM is installed for launching the uninstaller in the _jvm directory in the product location. However. Initial loading of installer is faster.3.Speeding Up Installation 25
|
•
Include a command line option For example:
-is:javahome
when launching the installer.

for the selected components.28
| Chapter 4
Installation FAQs and Troubleshooting
Running Out of Disk Space
The installer calculates the disk space required in product home location. However. Solution While performing installation. then the installer may fail. The calculation is done before the actual installation (copying of files to system) begins.
TIBCO Runtime Agent Installation
. avoid running other processes that consume disk space in product home location. if disk space is consumed by another process while the installer is copying the files. then the installer may fail and will give a failure message. The installer will proceed only if sufficient free disk space is available in product home location. and if the required disk space is thereby reduced.

That is why you must set the DISPLAY variable. So you decide to telnet to itaska from alaska... export DISPLAY # Korn shell export DISPLAY=<ip_address>:0..0.bin
TIBCO Runtime Agent Installation
. followed by a screen address../TIB_tra-suite_5...3_h7_110..... When you telnet to itaska.. .... Preparing Java(tm) Virtual Machine........ the installer will either wait or abort after displaying:
InstallShield Wizard Initializing InstallShield Wizard. the computer (specified in the DISPLAY variable) must give permissions to share its monitor.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.. .... It uses the DISPLAY environment variable to tell it on what computer to open the window.... If the environment variable is not set.. which can be :0.......6 machine (named alaska) that has a video card and monitor installed. you can run an X-Window application on it...
alaska> xhost + # give permission for all to its share monitor alaska> telnet itaska Welcome to HP-UX itaska 11... must open an additional window..
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)....1.... For example:
# Bourne shell DISPLAY=<ip_address>:0.0
For example..00 User: Password: itaska> export DISPLAY=alaska:0..0 # set display on alaska itaska> ..0... generally for graphics... ... consider a scenario where you need to install the adapter on a remote HP-UX machine (named itaska). you will not get access to itaska's monitor and will be unable to display an X-Window application... which instructs the X-Server to redirect all windows to the computer set in the variable........ Because you have a Solaris 5... Before doing so...0 # C-shell setenv DISPLAY <ip_address>:0............

00 64 bit system may crash with the following error message:
Pid nnn killed due to trashed stack.00 32 bit system and HP-UX 11. you need to manually set the SHLIB_PATH before you start TIBCO Administrator.
TIBCO Runtime Agent Installation
. To determine if your system has the kernel patch.i) system. first install HP-UX kernel patch PHKL_27282 and then proceed with the installation.00 64 bit systems.1/PA_RISC2. run:
uname -a
To determine the kernel bits on your system.00 64 bit system and it does not have the patch. It does not happen on HP-UX 11. Installation of patch PHKL_27282.30
| Chapter 4
Installation FAQs and Troubleshooting
Installation on HP-UX 11. run:
/usr/sbin/swlist -l product PHKL_27282
or
what /stand/vmunix | grep PHKL_27282
If your system is an HP-UX 11.4. as follows:
<TIBCO_HOME>/jre/1.00 64 bit Platform
Setting Library Path
On HP-UX. Pid nnn was killed due to failure in writing the signal context.11 (or 11. resolves the above crash.4.
This happens only on HP-UX 11. will reboot your system. To determine the OS version on your system. run:
getconf KERNEL_BITS
Resolution HP-UX kernel patch PHKL_27282.1/P A_RISC2.0:$SHLIB_PATH
Installation Crash
Installation on a HP-UX 11.0/hotspot:<TIBCO_HOME>/jre/1.

tibco. The value for systemName is determined by InetAddress. installation of a product that depends on TIBCO Runtime Agent may fail in the dependency resolution.systemName.properties.4.properties. the method getHostName().com is domainName. and tibco.properties.Cannot Install Dependent Product 33
|
Cannot Install Dependent Product
On HP-UX and AIX platforms.tibco.domainName file exists:
$ cd user's_home_directory $ ln -s vpd.properties. JRE 1. whereas JRE 1.systemName.tibco.systemName file exists:
$ cd user's_home_directory $ ln -s vpd.tibco.domainName
For example:
$ cd ~ $ ln -s vpd.properties.tibco.getHostName().properties.tibco. the installer is not able to load the correct registry file.tibco.tibco.com is domainName Case 2: If the vpd. returns different values based on the JRE versions used.upside.tibco.tibco. the installer registry file vpd.com
where upside is systemName.tibco.domainName. on AIX.properties.
TIBCO Runtime Agent Installation
.systemName file.com vpd.getLocalHost().1 returns only systemName.3.tibco. The TIBCO product installer maintains the registry information in the vpd.properties. Case 1: If the vpd.tibco.upside vpd.properties.systemName.systemName is located in the user's home directory.domainName vpd.upside. Because of this. However.properties.systemName vpd.systemName
For example:
$ cd ~ $ ln -s vpd. For example. even though the correct version of TIBCO Runtime Agent version is already installed on the system.0 returns systemName. and tibco.properties.properties.upside
where upside is systemName.tibco. Resolution On UNIX platforms.