Tib Admin Install

TIBCO Administrator™InstallationSoftware Release 5.6July 2008

Important InformationSOME 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 TIBCO ADMINISTRATOR INSTALLATION) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. 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, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now, TIBCO Adapter, TIBCO Administrator, TIBCO BusinessWorks, TIBCO ActiveMatrix BusinessWorks, TIBCO Designer, TIBCO Enterprise Message Service, TIBCO Rendezvous, TIBCO Repository, and TIBCO Runtime Agent are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and 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. 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.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 1999-2008 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viTIBCO Administrator Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

How to Contact TIBCO Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

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

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

Supported LDAP Servers, Databases and Web Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Supported LDAP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Supported Databases and Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Supported Web Browsers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installation Prerequisites on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Installation Prerequisites on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installing Releases with Higher Version Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installation Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Microsoft Windows Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11UNIX Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2 Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Install Using GUI Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Install Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Install and Create a Response File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Install with a Response File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Install in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Install in Silent Mode with a Response File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Product Dependency Checking During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Installing TIBCO Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Uninstalling TIBCO Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24To Uninstall TIBCO Administrator on Microsoft Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24To Uninstall TIBCO Administrator on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Appendix A Troubleshooting and FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

TIBCO Administrator Installation

iv | Contents

Port/Address in Use Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Dependency Resolution Fails on Some UNIX Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Console Install, Silent Install and Server Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Renaming Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

DISPLAY Variable on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

TIBCO Software Inc. End User License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Third Party Software License Agreements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39


| v

Preface

Topics

• Related Documentation, page vi

• Typographical Conventions, page viii

• How to Contact TIBCO Support, page x

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.


vi | Related Documentation

Related Documentation

This section lists documentation resources you may find useful.

TIBCO Administrator DocumentationThe following documents form the TIBCO Administrator documentation set:

• TIBCO Administrator Installation Read this manual for instructions on site preparation and installation.

• TIBCO Administrator User’s Guide Read this manual for instructions on using the product to manage users, resources, and applications inside an administration domain.

• TIBCO Administrator Server Configuration Guide Read this manual for instructions on using the administration server to manage projects and repositories, using command-line tools, performing conversions, and so on. The manual is written primarily for system administrators.

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

Other TIBCO Product DocumentationYou may find it useful to read the documentation for the following TIBCO products:

• TIBCO Runtime Agent™ software: Runtime Agent™ must be installed before installing TIBCO Administrator. Runtime Agent includes TIBCO libraries, third-party libraries, utilities, and other software used by TIBCO products.

• TIBCO Designer™ software: TIBCO Designer is installed as part of the TIBCO Runtime Agent installation. TIBCO Designer provides an easy to use GUI for design-time configuration of TIBCO applications. TIBCO Designer includes online help for each palette.

• TIBCO Hawk® software: This is a tool for monitoring and managing distributed applications and operating systems.

• TIBCO Rendezvous® software: Rendezvous® is installed as part of the TIBCO Runtime Agent installation. Rendezvous is the default message transport for an administration domain.

• TIBCO Enterprise Message Service™ software: Enterprise Message Service™ lets application programs send and receive messages using the Java Message


Preface | vii

Service (JMS) protocol. Enterprise Message Service can be set as the message transport for an administration domain.

• TIBCO ActiveMatrix BusinessWorks™ software: ActiveMatrix BusinessWorks™ is a scalable, extensible, and easy to use integration platform that allows you to develop integration projects. ActiveMatrix BusinessWorks includes a GUI for defining business processes and an engine that executes the process.

• TIBCO ActiveMartix Adapter™ software: Each TIBCO ActiveMartix Adapter product provides documentation that explains how to implement TIBCO ActiveMartix Adapter services, which can then be deployed from TIBCO Administrator.


viii | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin .

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand pathname

Key combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.


Preface | ix

Table 2 Syntax Typographical Conventions

Convention Use

[ ] An optional item in a command or code syntax.

For example:

MyCommand [optional_parameter] required_parameter

| A logical ’OR’ that separates multiple items of which only one may be chosen.

For example, you can select only one of the following parameters:

MyCommand para1 | param2 | param3

{ } A logical group of items in a command. Other syntax notations may appear within each logical group.

For example, the following command requires two parameters, which can be either the pair param1 and param2 , or the pair param3 and param4 .

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4 :

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters. The first parameter must be param1 . You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4 .

MyCommand param1 [param2] {param3 | param4}


x | How to Contact TIBCO Support

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows.

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you can request one.


http://www.tibco.com/services/support

https://support.tibco.com

| 1

Chapter 1 Installation Overview

This chapter introduces TIBCO Administrator installable components.

Topics

• Introduction, page 2

• Installing Releases with Higher Version Numbers, page 10

• Installation Registry, page 11

• Supported LDAP Servers, Databases and Web Browsers, page 4

• Installation Prerequisites on Microsoft Windows, page 6

• Installation Prerequisites on UNIX, page 8


2 | Chapter 1 Installation Overview

Introduction

TIBCO Administrator is dependent on TIBCO Runtime Agent. Before installing Administrator, you must first install TIBCO Runtime Agent. After TIBCO Administrator is installed, the installer utility prompts you to launch TIBCO Domain Utility to create the initial administration domain. The initial administration domain includes an administration server, a TIBCO Hawk agent and a domain repository.

When creating an administration domain you can specify the transport to use for domain communication, either TIBCO Rendezvous or TIBCO Enterprise Message Service. If you use Rendezvous, you can specify whether domain data is stored in a file or database. The default is a file based repository. If you select the database option, you are prompted later to provide database driver information and a database account that has write permissions to the database. If you specify TIBCO Enterprise Message Service as the transport, you must use a database for domain storage.

You can integrate an administration domain with an LDAP directory server. This allows you to use users and groups defined in the LDAP directory in TIBCO Administrator. If you want your initial administration domain to be integrated with an LDAP directory server, you should review the LDAP options explained in TIBCO Administrator User’s Guide.

TIBCO Administrator supports a variety of administration domain options.

• A machine can have multiple administration domains defined. Additional domains are defined later after the initial administration domain is defined. See TIBCO Runtime Agent Domain Utility User’s Guide for details.

• Other machines can be added to an administration domain. The machines are used to run applications that are part of the domain. Each machine that joins a domain must have TIBCO Runtime Agent installed. To add the machine to a domain, you run TIBCO Domain Utility on that machine and specify the domain to join. See TIBCO Runtime Agent Domain Utility User’s Guide for details.

• An administration domain can have many options defined. For example, for a Rendezvous based domain, you can define a secondary administration server and configure a domain to span across networks. See TIBCO Administrator Server Configuration Guide for information. These options can be set after the initial domain is created. See TIBCO Runtime Agent Domain Utility User’s Guide for details.

• For certain advanced configuration tasks, you can edit the tibcoadmin_domain.tra properties file that is created for your administration server. You can use it, for example, to inform the server that the configuration


Introduction | 3

file is using non-ASCII characters. See TIBCO Administrator Server Configuration Guide for details.



Supported LDAP Servers, Databases and Web Browsers

The following are supported on Microsoft Windows and Unix systems, where applicable.

Supported LDAP Servers• Sun Java System Directory Server 5.1 with Service Pack 3

• Sun Java System Directory Directory Server 5.2

• Microsoft Active Directory 2000

• Microsoft Active Directory 2003

• Microsoft Active Directory Application Mode (ADAM) 2003

• Novell eDirectory 8.7.3

• CA Directory Server

• Active Directory 2008

Supported Databases and DriversThe following databases are supported for administration domain data storage.

TheTIBCO provided drivers are deprecated. Third-party vendor-supplied drivers for Oracle, SQL Server, and DB2 are now supported. TIBCO recommends you to use these vendor-supplied drivers instead.


Supported LDAP Servers, Databases and Web Browsers | 5

• Oracle

— Database versions:

10g R1 (10.1.x.x)

10g R2 (10.2.x.x)

10g RAC

9i (9.2.x.x)

9i RAC

— Drivers:

DataDirect 3.7

Oracle Thin-driver

Oracle Thick-driver

• Microsoft SQL Server


2000

2005

— Drivers:

DataDirect 3.7

Microsoft JDBC driver

• IBM DB2 Universal Database


8.2 FixPak 3

9 (added)

— Drivers:

com.ibm.db2.jcc.DB2Driver 2.6 (Thin-driver)

Supported Web Browsers• Microsoft Internet Explorer 5.5 or higher

• Mozilla Suite 1.7.1 or higher

• Mozilla Firefox 1.x or higher



Installation Prerequisites on Microsoft Windows

You should have a minimum of 75 MB free to install the software. See Installer Disk Space Requirements in Temporary Area on page 11 for additional disk space requirements.

Supported Platforms

The following platforms are supported.

• Windows Server 2003 SP1 (x86)

• Windows Server 2003 SP1 (x86_64)

• Windows Server 2008 on (x86)

• Windows Server 2008 on (x86_64)

• Windows XP (x86)

• Windows Vista Business Edition (x86) with latest patches

Prerequisite Software

Before you install TIBCO Administrator 5.6, you must first install TIBCO Runtime Agent 5.6. If TIBCO Runtime Agent is not installed, the installer will inform you and exit.

Installer Account

You must have administrator privileges on the machine on which TIBCO Administrator software is installed.

Installing from Networked Drive

If you intend to install the product on a networked drive, you must change the user in the Services Configuration from Local System to a user that has permission to access the networked drive.

Only 32-bit installers are supported on Windows platforms.

You must use the 64-bit installer for TIBCO Administrator if you used the 64-bit installer for TIBCO Runtime Agent.


Installation Prerequisites on Microsoft Windows | 7

Memory Requirements for the Administration Server

The machine on which the Administration Server is installed should have a minimum of 1 gigabyte of system memory.

Special Note for Windows 2003

The heap size set in tibcoadmin_domain.tra (java.heap.size.max=512m) is set for a machine with 1GB of memory.

If you have less memory, we recommend lowering the heap size. The idea is to have the (heap size) plus (memory required by the operating system) less than the memory of the machine.

For example on Microsoft Windows, if you have 512MB of system memory, set the heap size to no more than 300MB because Windows itself requires about 200MB.

On Windows 2003, for machines that do not have service pack 1 installed, the installer creates the vpd property files in the user’s home directory rather than c:\windows. Because TIBCO Hawk agent only searches for .vpd property files under c:\windows, TIBCO Hawk agent cannot find the files and as a result, the administration domain is not updated with installed software.

To resolve this issue, upgrade Windows 2003 with service pack 1 prior to installing TIBCO software. Or, use the following procedure after installation to copy the vpd files to c:\windows each time TIBCO software is installed.

1. After installing TIBCO software, change directory to the user’s home directory. For example:cd C:\Documents and Settings\user-name

2. Copy the vpd files to c:/windows. For example:

copy vpd.* c:/windows



Installation Prerequisites on UNIX

You should have a minimum of 75 MB free to install the software. See Required Disk Space in Temporary Area on page 12 for additional disk space requirements.

Supported Platforms

The following platforms are supported:

• IBM (POWER)

— AIX 5.2 with patch 5200-04

— AIX 5.3

• HP-UX 11i (v2, v3) (IA-64/Itanium)

• HP-UX 11i (v1, v2, v3) (PA-RISC)

J2SE patches are required for all HP-UX platforms: http://www.hp.com/products1/unix/java/patches/index.html

• Red Hat (x86)

— Red Hat Enterprise Linux 4

— Red Hat Enterprise Linux 4.5

— Red Hat Enterprise Linux 5

— Red Hat Enterprise Linux 5.1

(also include all equivalent Oracle Enterprise Linux versions)

• SuSE (x86)

— SUSE Linux Enterprise 9

— SUSE Linux Enterprise 10 SP1

• Solaris (SPARC)

— Solaris 8

— Solaris 9

— Solaris 10

— Solaris 10 (x86)


Installation Prerequisites on UNIX | 9

Prerequisite Software

Before you install TIBCO Administrator 5.6, you must first install TIBCO Runtime Agent 5.6. If TIBCO Runtime Agent is not installed, the installer will inform you and exit.

Permissions

TIBCO 5.x products can be installed by a regular (non-root) user or by super-user (root). Different users can install the same product at different locations.

Product dependencies at install time are resolved at the user level through the installation registry maintained in the user's home directory. See Installation Registry on page 11 for more information.

Windows Environment

A window environment such as CDE (that is, X Windows) is required to run the installer in GUI mode. It is not required for a console installation.

Memory Requirements for the Administration Server

The machine on which the TIBCO Administrator is installed should have a minimum of 1 gigabyte of system memory.

You should use the 64-bit installer for TIBCO Administrator if you used the 64-bit installer for TIBCO Runtime Agent.

The installer works best when not using the native registry. On most UNIX platforms, the installer therefore does not use the native registry even for root user installations.

The heap size set in tibcoadmin_domain.tra (java.heap.size.max=512m) is set for a machine with 1GB of memory.

If you have less memory, we recommend lowering the heap size. The idea is not to have (heap size) + (memory required by the operating system) < the memory of the machine.



Installing Releases with Higher Version Numbers

TIBCO products use a three-digit release number that makes it possible to specify major, minor, and service pack release. For example, release 2.1.3 means major version 2, minor version 1, and service pack 3.

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

In that case, TIBCO Domain Utility is not launched, and you are not prompted to create an administration domain.

• If you are installing using a new major or minor release of a product that has already been installed, 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.6). The old installation is not removed, and must be uninstalled separately if you wish to remove it.

In that case, TIBCO Domain Utility is launched at the end of installation, and you are prompted to create an administration domain.

If you install a product and that product is already installed on your machine, you cannot choose a different location.


Installation Registry | 11

Installation Registry

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.

VPD files contain information about the TIBCO products installed on a machine. The VPD files are updated each time a TIBCO product is installed or uninstalled.

When you start TIBCO Administrator, TIBCO Hawk or TIBCO Domain Utility, the VPD files are checked for the list of installed software. For example, after you install a TIBCO product and start TIBCO Administrator, the Installed Software console in the TIBCO Administrator GUI is updated based on information in the VPD files.

Microsoft Windows PlatformsThe installation registry is maintained in the %SystemRoot% folder. The following files represent the installation registry:

%SystemRoot%\vpd.properties%SystemRoot%\vpd.properties.tibco.systemName

Installer Disk Space Requirements in Temporary Area

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

The installer requires 50 MB of free space in the temporary folder.

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 user1 performs the installation, and user2 attempts to start the TIBCO Hawk agent (that is required for TIBCO Administrator), user2 cannot view TIBCO Administrator. Linking the vpd files from the installer's home folder to the home

Do not edit, modify, rename, move, or remove vpd files.



folder of the person starting the TIBCO Hawk agent solves this.

If installation is performed by a super-user (root), the installation registry is maintained in the Native registry database:

• On Solaris the installation registry is maintained in the pkginfo database.

• On HP-UX the installation registry is maintained in swinstall database.

• On AIX the installation registry is maintained in /usr/lib/objrepos directory as two vpd files and in the installp database.

• On Linux the installation registry is maintained in the /root directory as two vpd files.

Required Disk Space 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 .

If your system does not have sufficient free disk space in the above temporary area, you can 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.

Required Disk Space in User's Home Directory

When a regular (non-root) user installs a TIBCO 5.x product on UNIX platforms, the installation registry (two 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.


| 13

Chapter 2 Installing the Software

This chapter explains how to install TIBCO Administrator and create the initial administration domain.

Topics

• Installation Options, page 14

• Installing TIBCO Administrator, page 17


14 | Chapter 2 Installing the Software

Installation Options

TIBCO Installer can run in GUI or console modes. Each mode is supported on all platforms.

• GUI mode presents panels that allow you to make choices about product selection, product location, and so on.

• Console mode allows you to run the installer from the command line. This is useful if your machine does not have a window environment or if you wish to install in silent mode. Silent mode installs without prompting you for information.

• You can create a response file in GUI or console mode, and then use the response file for subsequent installations.

— If no response file has been recorded earlier and you invoke the installer with the -silent argument, default installation parameters are used.

— If a response file exists, and the installer is started with -options responseFile as an argument, the installer uses the values that were specified when the response file was generated.

Install Using GUI ModeGUI mode allows you input values in panels. Type the following at the command prompt from the directory where you have downloaded the software. Note that version is the version number, for example 5.6.0. The .exe command is for Microsoft Windows and the .bin command is for Unix systems. The bin example uses the install package for Sun Solaris systems.

TIB_tibcoadmin-epe-simple_version_win_x86_32.exe TIB_tibcoadmin-epe-simple_version_sol8_sparc_32.bin

Install Using Console ModeThis example launches the installer in console (command line) mode. Messages and prompts are displayed in the console.

TIBCO Domain Utility is invoked after installation to create the initial administration domain only if you use GUI mode. Unless you are updating or reinstalling TIBCO Administrator, using GUI mode is highly recommended.


Installation Options | 15

TIB_tibcoadmin-epe-simple_version_win_x86_32.exe -is:javaconsole -console

TIB_tibcoadmin-epe-simple_version_sol8_sparc_32.bin -is:javaconsole -console

Install and Create a Response FileThe following example instructs the installer to automatically generate a response file for the product after the completion of the installation. The -console option launches the installer in non windows mode.

Note that there is no space between -options and -record .

TIB_tibcoadmin-epe-simple_version_win_x86_32.exe -is:javaconsole -console-options-record C:\dir\responseFile

TIB_tibcoadmin-epe-simple_version_sol8_sparc_32.bin -is:javaconsole -console-options-record /dir/responseFile

Install with a Response FileThe following example installs the software and uses a response file that specifies responses to installer prompts. The response file contains command-line options, one command per line, that set properties for the installation. You must provide the absolute path to the response file.

TIB_tibcoadmin-epe-simple_version_win_x86_32.exe -is:javaconsole -console-options C:\dir\responseFile

TIB_tibcoadmin-epe-simple_version_sol8_sparc_32.bin -is:javaconsole -console -options /dir/responseFile

Install in Silent ModeUse this option to install in silent mode, where the installation is performed with out user interaction. By default, a typical installation is performed when -silent is used.

TIB_tibcoadmin-epe-simple_version_win_x86_32.exe -is:silent -silent

TIB_tibcoadmin-epe-simple_version_sol8_sparc_32.bin -is:silent -silent



Install in Silent Mode with a Response FileYou can install in silent mode by including the absolute path to the response file.

TIB_tibcoadmin-epe-simple_version_win_x86_32.exe -is:silent -silent -options C:\dir\responseFile

TIB_tibcoadmin-epe-simple_version_sol8_sparc_32.bin -is:silent -silent -options /dir/responseFile

Product Dependency Checking During InstallationTIBCO 5.x products have dependencies on other TIBCO products. For example, TIBCO Administrator depends on TIBCO Runtime Agent. These product dependencies are enforced and bound during installation. Install time binding is done by substituting the values of various tags (such as %TIBCO_TRA_HOME% , %TIBCO_ADMIN_HOME% , %TIBCO_DOMAIN_HOME%) and updating properties in many properties files.

Since dependencies are enforced during installation, the installer can determine the version and location of all dependent products through the installation registry (vpd.properties.tibco.systemName). Version and location information is then substituted in many properties files, typically *.tra files. Moreover, many properties such as tibco.env.CUSTOM_PALETTE_PATH , tibco.env.CUSTOM_CP_EXT and tibco.env.CUSTOM_PATH are also updated during installation. Enforcing dependency checking and binding dependent products through file substitution during installation, allows out-of-the-box product functionality.


Installing TIBCO Administrator | 17

Installing TIBCO Administrator

After installing TIBCO Administrator, the installer starts TIBCO Domain Utility, which is used to create the initial administration domain. An administration domain can use TIBCO Rendezvous (the default) or TIBCO Enterprise Message Service as the message transport for components in the domain.

If you are using Enterprise Message Service as the transport for domain data, the Enterprise Message Service server should be running before creating the administration domain.

Follow these steps on Microsoft Windows and Unix systems:

1. Invoke the installer using GUI or console mode. See Installation Options on page 14.

2. After the Welcome and License Agreement screens, you are prompted to perform Typical or Custom installation. Custom installation allows you to install only the software, not the documentation. If you do so, online help will not display. A custom install also allows you to disallow installation of the MUI Pack, which provides support for using TIBCO Administrator in the Japanese language.

3. The installer displays the components that will be installed. After you confirm, the installation proceeds. See Installing Releases with Higher Version Numbers on page 10 for the installer behavior during upgrades.



4. After the software in installed, you are prompted to click the Next button to launch TIBCO Domain Utility and create the initial administration domain.

5. TIBCO Domain Utility prompts you to create a master or secondary administration server.

Select Master to create the primary administration server. A primary administration server must be defined for the administration domain before adding a secondary server to a different machine that is part of the domain. You can add a secondary server later, if needed, by invoking TIBCO Domain



Utility. Secondary servers are used only if TIBCO Rendezvous is used as the administration domain transport.

6. Click Next and provide information about the administration domain.

In Administration Domain, provide the name of the administration domain, which will also be the name of the server itself. Choose a name that clearly identifies the administration domain. Do not choose the name of the network domain. The name length must be less than 64 characters. You can use alphanumeric characters, hyphen (-), or under bar (_). Other special characters, including period or comma, are not allowed.

The Project Directory field provides the location where the server looks for the domain data store, for project files saved as single-file projects, and for deployment configuration files. A default location is given.

The name of the machine is provided in the Machine field and must not be changed.

Machines are grouped in the TIBCO Administrator GUI under the value provided in the Hawk Cluster field. If you change the default value, this machine displays in the TIBCO Administrator GUI under the value you provide. The cluster name must be enclosed within quotes if the name contains spaces.

The Encoding option is used for communication between the administration server and its clients. Choices are ISO8859 and UTF-8. This encoding is used for all primary and secondary servers in the administration domain.



The User and Group information retrieved from a corporate LDAP option allows you to integrate the administration domain with an LDAP directory server. Doing so allows the use of users and groups defined in the LDAP directory in TIBCO Administrator.

Keep Domain information stored in a Database selected if you want domain data and application repositories stored in a database.

Keep Local Application Data selected as the default if you want application repository data to be sent to target machines. See Deployment Choices on page 9 in TIBCO Administrator Server Configuration Guide for more information.

Click Show Advanced to choose the message transport for the administration domain as well as other advanced options. TIBCO Rendezvous is selected by default as the transport. You can change the default transport to TIBCO Enterprise Message Service. If you are using TIBCO Rendezvous, you can also change Rendezvous parameters from the defaults.

See TIBCO Runtime Agent Domain Utility User’s Guide for more information about these choices.

7. Click Next and in the dialog that displays, review the port numbers and shutdown password set for the Tomcat web server. In most cases, you should accept the defaults.

8. Click Next. Provide the domain administrator name and password. The name and password you provide is used to initially log into the domain using the TIBCO Administrator GUI. Click Configure Password Policy if the domain is



to have a password policy. The policy choices are explained in Password Policy on page 16 in TIBCO Administrator Server Configuration Guide.

9. Click Next. Unless you cleared Domain information stored in a Database in step 6, a database configuration panel appears. If so, specify the parameters for the database you wish to use and click Next. Otherwise, skip this step.



In the drop-down list at the top, you may choose the third-party vendor-supplied driver you specified when installing TIBCO Runtime Agent. See TIBCO Runtime Agent Installation for more information.

10. A summary dialog appears listing the choices you made. You can click the Back button to change a choice.

It is recommended that you use a third-party vendor-supplied driver instead of the deprecated DataDirect drivers.



11. Click Next. On Microsoft Windows, the following dialog appears indicating that the administration domain has been successfully created.

On Microsoft Windows, start the administration server and TIBCO Hawk agent services by navigating to the Services control panel, selecting each service and starting it. The start order is not important.

On Unix systems, from a command window, start the administration server:

% cd TIBCO_ADMIN_DOMAIN_HOME/domain-name/bin % tibcoadmin_domain-name

Start the TIBCO Hawk agent:

% cd TIBCO_TRA_DOMAIN_HOME/domain_name% hawkagent_domain-name

You can then access TIBCO Administrator, as discussed in TIBCO Administrator User’s Guide.

These services will be cofigured to automatically start at system boot time.



Uninstalling TIBCO Administrator

The TIBCO Installation Manager is used to uninstall TIBCO Administrator. The TIBCO Installation Manager displays all TIBCO software installed on your machine. Details about the selected TIBCO product are displayed in the right columns. 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.

The Installation Manager allows you to:

• Display installed products

• Display product components

• Display product dependencies and references

• Uninstall products and all references

To Uninstall TIBCO Administrator on Microsoft WindowsBefore uninstalling TIBCO Administrator, you must stop the administration server and TIBCO Hawk service for each domain that is running on the machine on which TIBCO Administrator is installed.

If the administration domain transport was configured to use a database, you should use TIBCO Domain Utility to delete the domain before uninstalling TIBCO Administrator. The procedure is explained in the TIBCO Runtime Agent Domain Utility User’s Guide.

1. Navigate to the Services panel:

a. Stop the TIBCO Administrator n.n domain-name server.

b. Stop the TIBCO Hawk Agent domain-name service.

2. Click Start > TIBCO > TIBCO Installation Manager

3. Click TIBCO Administrator Enterprise Edition, then click the Uninstall tab. Click Uninstall.

When you uninstall TIBCO Administrator, only files that were created during installation are uninstalled. Other files, such as files created as a result of a deployment are not uninstalled.


Uninstalling TIBCO Administrator | 25

To Uninstall TIBCO Administrator on UnixBefore uninstalling TIBCO Administrator, you must stop the administration server process and TIBCO Hawk process for each domain that is running on the machine on which TIBCO Administrator is installed.

If the administration domain transport was configured to use a database, you should use TIBCO Domain Utility to delete the domain before uninstalling TIBCO Administrator. The procedure is explained in TIBCO Runtime Agent Domain Utility User’s Guide.

1. Stop the TIBCO Administrator n.n domain-name server.

2. Stop the TIBCO Hawk Agent domain-name service.

3. In a command window invoke TIBCO_HOME/TibcoInstallationManager.bin

4. Click TIBCO Administrator Enterprise Edition, then click the Uninstall tab. Click Uninstall.


| 27

Appendix A Troubleshooting and FAQ

This appendix provides some troubleshooting information and answers to frequently asked questions.

Topics

• Port/Address in Use Message, page 28

• Console Install, Silent Install and Server Creation, page 30

• Renaming Installation Directory, page 31

• DISPLAY Variable on UNIX, page 32


28 | Appendix A Troubleshooting and FAQ

Port/Address in Use Message

You may get a Port in Use or Address in Use message for one of the following reasons:

• If a message displays indicating Port in Use , the port used by the TIBCO Hawk or TIBCO Repository Server servlet to communicate with Tomcat (the web server) is not available. Use TIBCO Domain Utility to change that port.

• If you stop and restart TIBCO Administrator under UNIX, an error results that indicates port 8080 is already in use. In that case, you have two choices to resolve the issue:

— Change the tcp_time_wait_interval . For example, on Solaris, place the following line at the end of the file /etc/rc2.d/S69inet

ndd -set /dev/tcp tcp_time_wait_interval 60000

Then wait for 60 seconds before you restart TIBCO Administrator.

On HP-UX, the file is in /sbin/rc2.d and is named S008net.init .

— Find and kill the two TIBCO Rendezvous (rvd) processes.


Dependency Resolution Fails on Some UNIX Platforms | 29

Dependency Resolution Fails on Some UNIX Platforms

On some platforms (HP-UX and AIX), even though the correct version of TRA is already installed in the system, installation of a product that depends on TRA will fail in the dependency resolution. This is considered a known issue.

TIBCO product installer maintains the registry information in the file vpd.properties.tibco.systemName . The value for systemName is determined by InetAddress.getLocalHost().getHostName() . However, the method getHostName() , returns different values based on the JRE versions used. For instance on AIX, JRE 1.3.1 returns only systemName , whereas JRE 1.4.0 returns systemName .domainName . Because of this, the installer is not always able to load the correct registry file.

On Unix platforms, the installer registry file vpd.properties.tibco.systemName is located in the user's home directory.

Case 1: If vpd.properties.tibco.systemName file exists

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

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 vpd.properties.tibco.systemName.domainName file exists

$ cd user's_home_directory

$ ln -s vpd.properties.tibco.systemName.domainName vpd.properties.tibco.systemName

Example:

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

where upside is systemName, and tibco.com is domainName



Console Install, Silent Install and Server Creation

When running the installer in console mode, TIBCO Domain Utility is not launched afterwards. How can the administration domain be created?

You can create an administration domain on Windows and Unix by launching the TIBCO Domain Utility: TIBCO_TRA_HOME/bin/domainutility


Renaming Installation Directory | 31

Renaming Installation Directory

Can the installation directory be renamed after installation?

If you rename the installation directory, unexplainable problems will result. Do not rename the directory.



DISPLAY Variable on UNIX

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 HPUX 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 use telnet to connect 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 HPUX itaska 11.00User:Password:itaska> export DISPLAY=alaska:0.0 # set display on alaskaitaska> TIB_designer-simple_5.0.1_h7_110.bin


TIBCO Software Inc. End User License Agreement | 33

TIBCO Software Inc. End User License AgreementREAD THIS END USER LICENSE AGREEMENT CAREFULLY. BY DOWNLOADING OR INSTALLING THE SOFTWARE, YOU AGREE TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS, DO NOT DOWNLOAD OR INSTALL THE SOFTWARE AND RETURN IT TO THE VENDOR FROM WHICH IT WAS PURCHASED.

Upon your acceptance as indicated above, the following shall govern your use of the Software except to the extent all or any portion of the Software (a) is subject to a separate written agreement, or (b) is provided by a third party under the terms set forth in an Addenda at the end of this Agreement, in which case the terms of such addenda shall control over inconsistent terms with regard to such portion(s).

License Grant. The Software is the property of TIBCO or its licensors and is protected by copyright and other laws. While TIBCO continues to own the Software, TIBCO hereby grants to Customer a limited, non-transferable, non-exclusive, license to use the Number of Units set forth in the Ordering Document, in machine-readable, object code form and solely for Customer's internal business use.

Restrictions. Customer agrees not to (a) make more copies than the Number of Units plus a reasonable number of backups; (b) provide access to the Software to anyone other than employees, contractors, or consultants under written contract with Customer agreeing to be bound by terms at least as protective of TIBCO as those in this End User License Agreement ("Authorized Users"); (c) sublicense, transfer, assign, distribute to any third party, pledge, lease, rent, or commercially share the Software or any of Customer's rights under this Agreement (for the purposes of the foregoing a change in control of Customer is deemed to be an assignment); (d) use the Software for purposes of providing a service bureau, including, without limitation, providing third-party hosting, or third-party application integration or application service provider-type services, or any similar services; (e) use the Software in connection with ultrahazardous activities, or any activity for which failure of the Software might result in death or serious bodily injury to Customer or a third party; or (f) directly or indirectly, in whole or in part, modify, translate, reverse engineer, decrypt, decompile, disassemble, make error corrections to, create derivative works based on, or otherwise attempt to discover the source code or underlying ideas or algorithms of the Software. Customer may engage in such conduct as is necessary to ensure the interoperability of the Software as required by law, provided that prior to commencing any decompilation or reverse engineering of any Software, Customer agrees to it shall observe strict obligations of confidentiality and provide TIBCO reasonable advance written notice and the opportunity to assist with and/or conduct such activity on Customer's behalf and at Customer's expense.

Beta and Evaluation Licenses. Notwithstanding the foregoing, if the Software is being provided for demonstration, beta testing, or evaluation purposes, then Customer agrees (a) to use the Software solely for such purposes, (b) that the Software will not be used or deployed in a production or development environment, and (c) that such use shall automatically terminate upon the earlier of thirty days from the date Customer receives the right to install the Software, or Customer's receipt of notice of termination from TIBCO.

Maintenance. Provided Customer has paid applicable support fees (not included with Software fees unless separately listed), TIBCO shall provide support for generally available Software ("Maintenance") on an annual basis commencing on the Purchase Date. Thereafter Maintenance will be automatically renewed for successive one (1) year terms at the then current rates. Customer shall designate at

TIBCO's support website https://support.tibco.com/esupport/newuser.html, the number of authorized contacts as permitted by TIBCO based on the level of Maintenance purchased (contacts are changeable upon 48-hours prior written notice to TIBCO). Each contact may contact TIBCO for problem resolution during TIBCO's published support hours corresponding to the level of Maintenance purchased.

Upon notice from a contact of a Software problem which can be reproduced at a TIBCO Maintenance facility, TIBCO shall use reasonable efforts to correct or circumvent the problem according to its published maintenance objectives. TIBCO reserves the right to make changes only to the most currently available version. TIBCO will use reasonable efforts to support the previously released version of the Software for a maximum of six months.

TIBCO shall have no obligation to provide Maintenance for the Software if (i) used on any computer system running other than the operating system software for which the Software is approved (as set forth in the Software documentation) and licensed hereunder, or (ii) if Customer has modified or authorized a third party to modify the Software. TIBCO shall have no obligation to modify any version of the Software to run with any new versions of any operating system, or any other third party software or hardware. If Customer purchases Maintenance for any Software, Customer must purchase the same level of Maintenance for all copies of the Software for which it is licensed.

Maintenance Fees for lapsed Maintenance or the changing of the level of Maintenance shall be mutually agreed upon between Customer and TIBCO. Upgrades, patches, enhancements, bug fixes, new versions and/or new releases of the Software provided from time to time under Maintenance shall be used only as replacements to existing copies, and shall not be deemed to increase the Number of Units, and use thereof shall be governed by the terms of this Agreement, except for the first paragraph of the Limited Warranty and any right of return or refund.

Services. Customer may request additional services ("Services") either in an Ordering Document, or by a separate mutually executed work order, statement of work or other work-request document incorporating the term of this End User License Agreement (each, a "Work Order"). Unless otherwise expressly agreed to in a Work Order, all Services and any work product therefrom shall be (a) performed on a time and materials basis, plus meals, lodging, travel, and other expenses reasonably incurred in connection therewith, (b) deemed accepted upon delivery, and (c) exclusively owned by TIBCO (except for Confidential Information of Customer), including all right, title and intellectual property or other right or interest therein. Each Work Order is intended to constitute an independent and distinct agreement of the parties, notwithstanding that each shall be construed to incorporate all applicable provisions of this End User License Agreement. Fees for Services shall be due and payable in United States dollars net 30 from the date of TIBCO's invoice.

Limited Warranty. If Customer obtained the Software directly from TIBCO, then TIBCO warrants that for a period of thirty (30) days from the Purchase Date: (i) the media on which the Software is furnished will be free of defects in materials and workmanship under normal use; and (ii) the Software will substantially conform to its Documentation. This limited warranty extends only to the original Customer hereunder. Customer's sole and exclusive remedy and the entire liability of TIBCO and its licensors under this limited warranty will be, at TIBCO's option, repair, replacement, or refund of the


https://support.tibco.com/esupport/newuser.html

34 | TIBCO Software Inc. End User License Agreement

Software and applicable Maintenance fees, in which event this End User License Agreement shall terminate upon refund thereof.

This warranty does not apply to any Software which (a) is licensed for beta, evaluation, testing or demonstration purposes for which TIBCO does not receive a license fee, (b) has been altered or modified, except by TIBCO, (c) has not been installed, operated, repaired, or maintained in accordance with instructions supplied by TIBCO, (d) has been subjected to abnormal physical or electrical stress, misuse, negligence, or accident, or (e) is used in violation of any other term of this End User License Agreement. Customer agrees to pay TIBCO for any Maintenance or Services provided by TIBCO related to a breach of the foregoing on a time, materials, travel, lodging and other reasonable expenses basis. If Customer obtained the Software from a TIBCO reseller or distributor, the terms of any warranty shall be as provided by such reseller or distributor, and TIBCO provides Customer no warranty with respect to such Software.

EXCEPT AS SPECIFIED IN THIS LIMITED WARRANTY, THE SOFTWARE, MAINTENANCE AND SERVICES ARE PROVIDED "AS IS", ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS, AND WARRANTIES INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTY OR CONDITION OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, SATISFACTORY QUALITY OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE, ARE HEREBY EXCLUDED TO THE EXTENT ALLOWED BY APPLICABLE LAW. CERTAIN THIRD PARTY SOFTWARE MAY BE PROVIDED TO CUSTOMER ALONG WITH CERTAIN TIBCO SOFTWARE AS AN ACCOMMODATION TO CUSTOMER. THIS THIRD PARTY SOFTWARE IS PROVIDED "AS IS". CUSTOMER MAY CHOOSE NOT TO USE THIRD PARTY SOFTWARE PROVIDED AS AN ACCOMMODATION BY TIBCO. NO WARRANTY IS MADE REGARDING THE RESULTS OF ANY SOFTWARE, MAINTENANCE OR SERVICES OR THAT THE SOFTWARE WILL OPERATE WITHOUT ERRORS, PROBLEMS OR INTERRUPTIONS, OR THAT ERRORS OR BUGS IN THE SOFTWARE WILL BE CORRECTED, OR THAT THE SOFTWARE'S FUNCTIONALITY, MAINTENANCE OR SERVICES WILL MEET CUSTOMER'S REQUIREMENTS. NO TIBCO DEALER, DISTRIBUTOR, AGENT OR EMPLOYEE IS AUTHORIZED TO MAKE ANY MODIFICATIONS, EXTENSIONS OR ADDITIONS TO THIS WARRANTY.

Indemnity. If Customer obtained the Software from TIBCO directly, then TIBCO agrees at its own expense to defend or, at its option, to settle, any claim or action brought against Customer to the extent it is based on a claim that the unmodified Software infringes any patent issued by the United States, Canada, Australia, Japan, or any member of the European Union, or any copyright, or any trade secret of a third party; and TIBCO will indemnify and hold Customer harmless from and against any damages, costs and fees reasonably incurred (including reasonable attorneys' fees) that are attributable to such claim or action and which are assessed against Customer in a final judgment; provided that TIBCO is promptly notified in writing of such claim, TIBCO has the exclusive right to control such defense and/or settlement, and Customer shall provide reasonable assistance (at TIBCO's expense) in the defense thereof. In no event shall Customer settle any claim, action or proceeding without TIBCO's prior written approval. In the event of any such claim, litigation or threat thereof, TIBCO, at its sole option and expense, shall (a) procure for Customer the right to continue to use the Software or (b) replace or modify the Software with functionally equivalent software. If such settlement or modification is not commercially reasonable (in the reasonable opinion of TIBCO), TIBCO may cancel this End User License Agreement upon sixty days prior written notice to Customer, and refund to Customer the unamortized portion of the license fees paid to TIBCO by Customer based on a five-year straight-line depreciation. This Section

states the entire liability of TIBCO with respect to the infringement of any intellectual property rights, and Customer hereby expressly waives any other liabilities or obligations of TIBCO with respect thereto. The foregoing indemnity shall not apply to the extent any infringement could have been avoided by use of the then-current release.

Limitation of Liability. EXCEPT AS PROVIDED UNDER INDEMNITY OR RESULTING FROM A BREACH OF CONFIDENTIALITY (THE "EXCLUDED MATTERS"), IN NO EVENT WILL EITHER PARTY OR TIBCO'S LICENSORS BE LIABLE FOR ANY LOST DATA, LOST REVENUE, LOST PROFITS, DAMAGE TO REPUTATION, BUSINESS INTERRUPTION, OR ANY OTHER INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, PUNITIVE, EXEMPLARY OR ANY SIMILAR TYPE DAMAGES ARISING OUT OF THIS AGREEMENT, THE USE OR THE INABILITY TO USE THE SOFTWARE, OR THE PROVISION OF ANY MAINTENANCE OR SERVICES, EVEN IF A PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. EXCEPT FOR THE EXCLUDED MATTERS, IN NO EVENT SHALL A PARTY BE LIABLE TO THE OTHER, WHETHER IN CONTRACT, TORT (INCLUDING ACTIVE OR PASSIVE NEGLIGENCE), BREACH OF WARRANTY, CLAIMS BY THIRD PARTIES OR OTHERWISE, EXCEED THE PRICE PAID BY CUSTOMER UNDER THE APPLICABLE ORDERING DOCUMENT.

THE FOREGOING LIMITATIONS SHALL APPLY EVEN IF THE ABOVE-STATED REMEDY OR LIMITED WARRANTY FAILS OF ITS ESSENTIAL PURPOSE. BECAUSE SOME STATES OR JURISDICTIONS DO NOT ALLOW LIMITATION OR EXCLUSION OF CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO CUSTOMER.

Confidentiality. "Confidential Information" means the terms of this End User License Agreement; all information marked by the disclosing party as proprietary or confidential; any provided software, related documentation or related performance test results derived by Customer; and any methods, concepts or processes utilized in provided software or related documentation. Confidential Information shall remain the sole property of the disclosing party and shall not be disclosed to any non-Authorized User of either TIBCO or Customer without the prior written consent of the disclosing party. If Confidential Information is communicated orally, such communication shall be confirmed as "Confidential" in writing within thirty days of such disclosure. The parties agree to protect the Confidential Information of the other in the same manner it protects the confidentiality of similar information and data of its own (and at all times exercising at least a reasonable degree of care). Except with respect to the Software, items will not be deemed Confidential Information if (i) available to the public other than by a breach of an agreement with TIBCO, (ii) rightfully received from a third party not in breach of any obligation of confidentiality, (iii) independently developed by one party without use of the Confidential Information of the other; (iv) known to the recipient at the time of disclosure (other than under a separate confidentiality obligation); or (v) produced in compliance with applicable law or court order, provided the other party is given reasonable notice of the same. Both parties agree to indemnify the other for any damages the other may sustain resulting from their unauthorized use and/or disclosure of the other's Confidential Information. Such damages shall include reasonable expenses incurred in seeking both legal and equitable remedies. To the extent required by law, at Customer's request, TIBCO shall provide Customer with the interface information needed to achieve interoperability between the Software and another independently created program, on payment of TIBCO's applicable fee. Customer agrees to observe obligations of confidentiality with respect to such information.


TIBCO Software Inc. End User License Agreement | 35

Export. Software, including technical data, is subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Customer agrees to comply strictly with all such regulations and agrees to obtain all necessary licenses to export, re-export, or import Software.

Government Use. If the Customer is an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the Software, or any related documentation of any kind, including technical data or manuals, is restricted in accordance with Federal Acquisition Regulation ("FAR") 12.212 for civilian agencies and Defense Federal Acquisition Regulation Supplement ("DFARS") 227.7202 for military agencies. The Software is commercial computer software and commercial computer software documentation. Use of the Software and related documentation by the Government is further restricted in accordance with the terms of this Agreement, and any modification thereto.

Orders. An Ordering Document shall be deemed accepted only by issuance of a TIBCO invoice and solely for purposes of administrative convenience. None of the terms of the Ordering Document (other than the Software product name, Number of Units, level of Maintenance, description of Services, and fees due in connection therewith) shall apply for any reason or purpose whatsoever, regardless of any statement on any Ordering Document to the contrary, unless countersigned by an officer of TIBCO. This Agreement constitutes the entire agreement between the parties with respect to the use of the Software, Maintenance and Services, and supersedes all proposals, oral or written, and all other representations, statements, negotiations and undertakings relating to the subject matter hereof. All orders of Software, Maintenance or Services by Customer to TIBCO shall be deemed to occur with or without reference to, under the terms of this End User License Agreement, unless expressly superseded by a signed written agreement between the parties. Neither the license to use the Software granted in this Agreement nor the obligation to pay the license fees set forth above are dependent upon the performance by any party of any Services or the supply of any other software program or product. Software shall be delivered electronically, and such delivery shall be deemed complete when the Software is made available for download by Customer.

Term and Termination. Maintenance or Services may be terminated: (a) by either party upon a default of the other, such default remaining uncured for fifteen days from written notice from the non-defaulting party; (b) upon the filing for bankruptcy or insolvency of the other party, (c) by either party upon prior written notice at least ninety (90) days prior to the end of any annual Maintenance term; or (d) by Customer (for Services), upon ten days prior written notice. Termination of Maintenance or Services shall not terminate this End User License Agreement. Customer may terminate this End User License Agreement in its entirety at any time by destroying all copies of the Software. Upon termination of this End User License Agreement in its entirety, for any reason, Customer must cease using and return or destroy all copies of the Software. Customer's obligation to pay accrued charges and any fees due as of the date of termination, as well as the sections entitled "Confidentiality", "Limited Warranty" and "Limitation of Liability" shall survive any such termination.

Authority. You hereby represent and warrant that you have full power and authority to accept the terms of this End User License Agreement on behalf of Customer, and that Customer agrees to be bound by this End User License Agreement.

General. Fees on the Ordering Document (all to be paid on the latter of thirty days from Invoice by TIBCO or the date set forth in the

Ordering Document) do not include sales, use, withholding, value-added or similar taxes, and Customer agrees to pay all sales, use, value-added, goods and services, consumption, withholding, excise and any other similar taxes or government charges, exclusive of TIBCO's income tax. Customer agree to pay all reasonable costs incurred (including reasonable attorneys' fees) in collecting past due amounts. Except as set forth in the Section entitled "Limited Warranty" all fees paid under or in connection with this End User License Agreement are non-refundable and no right of set-off exists. All payments of fees due shall be made in U.S. dollars, net 30 from Purchase Date, or, for any other amounts coming due hereafter, net 30 from TIBCO's invoice. A service charge of one and one-half percent per month will be applied to all invoices that are not paid on time. No delay in the performance of any obligation by either party, excepting all obligations to make payment, shall constitute a breach of this End User License Agreement to the extent caused by force majeure. Customer hereby grants TIBCO and its independent auditors the right to audit Customer's compliance with this End User License Agreement. If any portion of this End User License Agreement is found to be void or unenforceable, the remaining provisions shall remain in full force and effect. This End User License Agreement shall be governed by and construed in accordance with the laws of the State of California, United States of America, as if performed wholly within the state and without giving effect to the principles of conflict of law. The United Nations Convention on Contracts for the International Sale of Goods is excluded from application hereto. If any portion hereof is found to be void or unenforceable, the remaining provisions of this Agreement shall remain in full force and effect.

Definitions. In connection with this End User License Agreement the following capitalized terms shall have the following meaning: "CICS Region" means a subdivided mainframe address space managed by CICS for resource allocation, resource sharing, and transaction execution, of which the resource definitions include the TIBCO EMS Client for z/OS; "Connection" means for TIBCO SmartSockets and TIBCO SmartMQ, any network protocol link established with such Software (directly or indirectly) to any other entity, including but not limited to software, firmware or hardware; "Connected Processor" means a Processor that produces information or messages consumed by the relevant Software (excluding Processors on devices such as routers, switches, proxies, HTTP or application servers configured to substantially pass-through information or messages to TIBCO Software); "Customer" means the original purchaser or licensee of the Software and any permitted successors and assigns; "Developer" means a Named User of a TIBCO Software product for use only in Non-Production; "Documentation" means text material that accompanies the TIBCO Software on delivery; "Enterprise" means an unlimited Number of Units of the TIBCO Software set forth in an Ordering Document, deployed by Customer for a period of one (1) year (unless otherwise set forth in an Ordering Document) from the Effective Date (the "Enterprise Term"), at which time, the Number of Units then deployed in Production and Non-Production use by Customer becomes fixed and Customer may not thereafter deploy additional Units. During the Enterprise Term, Customer's right to deploy an unlimited Number of Units does not extend to any entity which acquires, is acquired by, merged into, or otherwise combined with Customer. Customer hereby agrees to provide TIBCO, within sixty (60) days after the end of the Enterprise Term, with written notice of the Number of Units deployed at the end of the Enterprise Term by License Type, Platform and Unit; "License Type" means the environment in which the TIBCO Software may be used (including without limitation, Production, Non-Production); "Managed Endpoints" means the number of processors running instances of TIBCO BusinessWorks™ that are being managed by TIBCO ActiveMatrix™ Policy Manager; "MSU" means Millions of Service Units per hour, based on the then current MSU rating established by IBM for IBM and IBM compatible hardware which is used for software pricing (not


36 | TIBCO Software Inc. End User License Agreement

necessarily a direct indication of relative processor capacity) as set forth in IBM's generally available Large System Performance Reference; "Named User" means an identifiable individual, not necessarily named at the time of a license grant, designated by Customer to access the TIBCO Software, regardless of whether or not the individual is actively using the TIBCO Software at any given time; "Non-Production" means a non-operational environment into which the TIBCO Software may be installed, which is not processing live data, which is not running any operations of the Customer and which has not been deployed to permit any users to access live data. Non-Production environments include development, cold back-up, high availability, hot standby, and test environments; "Number of Units" means the cumulative number of copies of TIBCO Software licensed for use by type of Unit as set forth in this Agreement, or in an Ordering Document, and including, if applicable, as reported by Licensee upon expiration of a Project or Enterprise Term; "Ordering Document" means any purchase order or similar document or agreement requesting Software, Maintenance or Services; "Platform" means the operating system set forth in an Ordering Document; "Processor" means a central processing unit ("CPU") on which the TIBCO Software is licensed to run and which for the purposes of counting Processors on multicore chips, the number of Processors is the number of CPUs times the number of cores multiplied by .75.; "Processor Source Locked" means the number of connections to a single database made possible by (or licensed for) the relevant TIBCO Software regardless of how many Processors are used by the system or environment which is accessing the database; "Production" means an operational environment into which the licensed TIBCO Software has been installed, which is processing live data and which has been deployed so that the intended users of the environment are able to access the live data; "Project" means an unlimited Number of Units for the License Type listed in this Agreement, to be deployed by Customer solely in connection with the undertaking described under an Ordering Document for a period of one (1) year (unless otherwise set forth in this Agreement) from the Effective Date (the "Project Term"), at which time, the Number of Units then deployed in Production and Non-Production use by Customer becomes fixed and Customer may not thereafter deploy additional Units. During the Project Term, Customer's right to deploy an unlimited Number of Units does not extend to any entity which acquires, is acquired by, merged into, or otherwise combined with Customer. Customer hereby agrees to provide TIBCO, within sixty (60) days after the end of the Project Term, with written notice of the Number of Units deployed at the end of the Project Term by Unit and License Type. "Purchase Date" means the date of the Ordering Document is accepted by TIBCO; "Server Instance" means a computer with 1 CPUs (unless otherwise specified in the Agreement) performing common services for multiple other machines; "Software" means the most current generally available object code version (as of the Purchase Date) of the software products listed in an Ordering Document (except as provided for beta or evaluation licenses), in whole and in part, including its Documentation; "Third Party Software" means third-party software identified by its company and/or product name, the provision of which by TIBCO is made solely as an accommodation and in lieu of Customer purchasing a license to Third Party Software directly from the third party vendor; "Trading Partner" means an entity or individual with which the Licensee engages in electronic commerce by means of TIBCO Software in accordance with this Agreement; "Unit" means a license restriction describing the manner in which a copy (or multiple copies) of the TIBCO Software may be deployed (including, without limitation, Processor, Named User, Connected Processor, and Processor Source Locked) and is the mechanism used to determine the Number of Units licensed pursuant to an Ordering Document.

Special Product Provisions. TIBCO BusinessPartner: Customer may sublicense to third parties ("Partners") up to the total Number of Copies of TIBCO BusinessPartner, provided that for every such

sublicense, the Number of Copies Customer is licensed to use shall be reduced by the same number, and provided further that prior to delivery of TIBCO BusinessPartner to a Partner, such Partner agrees in writing (a) to be bound by terms and conditions at least as protective of TIBCO as the terms of this Agreement, (b) that TIBCO BusinessPartner be used solely to communicate with Customer's implementation of TIBCO BusinessConnect, and (c) for such Partner to direct all technical support and Maintenance questions directly to Customer. Customer agrees to keep records of the Partners to which it distributes TIBCO BusinessPartner, and to provide TIBCO the names thereof (with an address and contact name) within sixty days of the end of each quarter. Embedded/Bundled Products. Some TIBCO Software embeds or bundles other TIBCO Software (e.g., TIBCO InConcert bundles TIBCO Rendezvous). Use of such embedded or bundled TIBCO Software is solely to enable the functionality of the TIBCO Software licensed on the Cover Page, and may not be used or accessed by any other TIBCO Software, or for any other purpose. Open Source Software: If Customer uses Open Source software in conjunction with the TIBCO Software, Customer must ensure that its use does not: (i) create, or purport to create, obligations of use with respect to the TIBCO Software; or (ii) grant, or purport to grant, to any third party any rights to or immunities under TIBCO's intellectual property or proprietary rights in the TIBCO Software. You also may not combine the TIBCO Software with programs licensed under the GNU General Public License ("GPL") in any manner that could cause, or could be interpreted or asserted to cause, the TIBCO Software or any modifications thereto to become subject to the terms of the GPL.

Version 5.5, April 2007


Third Party Software License Agreements | 37

Third Party Software License AgreementsThe following are the software licenses for the Third Party Software provided in connection with the software.

Apache Tomcat 5.5.25

Apache License

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, includingthe original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on

electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License.

Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License.

Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution.

You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License.


38 | Third Party Software License Agreements

You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions.

Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks.

This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty.

Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability.

In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability.

While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.


| 39

Index

A

access information 3ACL

roles 3administration domain

unique name 9, 15architecture

TIBCO administration domain 2authentication 3authorization 3

C

componentsinstallation 5TIBCO administration domain 2

creating a TIBCO domain 4customer support ix

D

domain nameunique 9, 15

I

installationcomponents 5prerequisites 7procedure 8, 10, 14, 15TIBCO domain products 4

J

joining a domain 4

M

machines 3

N

name of domain 9, 15

P

prerequisites for TIBCO BusinessWorks 7projects 3

R

roles 3

S

security 3authentication 3authorization 3roles 3

support, contacting ix


40 | Index

T

technical support ixTIBCO administration domain

architecture 2components 2creating 4joining 4

TIBCO Administration Server 2TIBCO BusinessWorks

components 5installation 8, 10, 14, 15installing components 5prerequisites 7

TIBCO domainsetup 4

TRA 2

U

user information 3


Tib Admin Install

Documents

Transcript of Tib Admin Install