Zindagi

TIBCO Administrator™
Installation Guide
Software Release 5.1.3
May 2004
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH
EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY
(OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE.
THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY
ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND
CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED
SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT,
THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING
DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN
TIBCO BUSINESSWORKS CONCEPTS). USE OF THIS DOCUMENT IS SUBJECT TO THOSE
TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE
OF AND AN AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright
laws and treaties. No part of this document may be reproduced in any form without the written
authorization of TIBCO Software Inc.
TIB, TIBCO, Information Bus, The Power of Now, TIBCO Adapter, and TIBCO Designer are either
registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other
countries.
All other product and company names and marks mentioned in this document are the property of
their respective owners and are mentioned for identification purposes only.
This software may be available on multiple operating systems. However, not all operating system
platforms for a specific software version are released at the same time. Please see the readme.txt file
for the availability of this software version on a specific operating system platform.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL
ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE
CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO
SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)
AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
Copyright © 1999-2004 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
TIBCO Administrator Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Other Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
How to Contact TIBCO Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Installer Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Installable Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
A Note on Installing Releases with Higher Version Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
A Note on Upward Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Using the TIBCO Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Installer Startup Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Combining Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Installation Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Microsoft Windows Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
UNIX Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
TIBCO Administrator Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
TIBCO Administration Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
TIBCO Administration Domain Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Creating or Joining an Administration Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Server Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 1 Installation on Microsoft Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Running the Administration Server Under Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 2 Installing the Software on UNIX Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installing TIBCO Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Running the Administration Server Under UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
TIBCO Administrator Installation Guide

iv
| Contents
Chapter 3 Setting up an Administration Server with a Database Backend. . . . . . . . . . . . . . . . 25

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Creating the Database Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Size Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Running the Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Reserved Database Tables for Storing Repository Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Appendix A Troubleshooting and FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Port/Address in Use Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Security Option Unavailable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Installation on HPUX 11.00 64 bit Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Installation on AIX 4.3 Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Dependency Resolution Fails on Some UNIX Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Console/Silent Install and Server Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Renaming Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
DISPLAY Variable on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

|v
Preface
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.
TIBCO Administrator allows administrators and end users to manage user

authentication and authorization, configure deployments, manage and monitor
deployments, and view information about running processes and machines in a
TIBCO administration domain. TIBCO Administrator consists of the TIBCO
Administration Server and the browser-based TIBCO Administrator GUI.
This preface lists related documentation and contact information for TIBCO
Customer Support.
Topics
• Related Documentation, page vi

• How to Contact TIBCO Customer Support, page vii

vi
| Related Documentation
Related Documentation
This section lists documentation resources you may find useful.
TIBCO Administrator Documentation

The TIBCO Administrator documentation set consists of the following
documents:
• TIBCO Administrator User’s Guide: This manual explains how to use the TIBCO
Administrator GUI. The manual is included as online help for TIBCO
Administrator.
• TIBCO Administrator Server Configuration Guide: This manual explains how
system administrators can use the TIBCO Administration Server to manage
projects and repositories, use command-line tools, perform conversions, and
so on. This document is meant for system administrators only; it is not usually
relevant for users of the TIBCO Administrator GUI.
• TIBCO Administrator Installation Guide: This manual explains how to install
TIBCO Administrator on Microsoft Windows and UNIX systems and how to
configure the server and the TIBCO administration domain.
Other Product Documentation

The TIBCO Runtime Agent, which includes a set of libraries and TIBCO products,
is a prerequisite product for TIBCO Administrator.
TIBCO Runtime Agent Administrator’s Guide, TIBCO Runtime Agent Release Notes
and TIBCO Runtime Agent Installation provide information about TIBCO Runtime
Agent.

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

viii
| How to Contact TIBCO Customer Support

|1
Installer Overview
This chapter introduces TIBCO Administrator installable components and

explains how to use the installer.
Topics
• Introduction, page 2
• Using the TIBCO Installer, page 4
• Installation Registry, page 7
• TIBCO Administrator Installation Overview, page 9

2 Installer Overview
|
Introduction
TIBCO products use TIBCO Administrator for different tasks. Because of this, you
have several choices for installing TIBCO Administrator:
• TIBCO Administrator Repository Edition without user and resource
management—Supports local or server-based access of project repositories,
and fault tolerance using multiple Administration Servers.
• TIBCO Administrator Repository Edition with user and resource
management—Supports local or server-based access of project repositories,
and fault tolerance using multiple Administration Servers.
In addition, allows you to create a TIBCO Administration Domain and
manage an Access Control List (ACL) for the domain, which determines
which user can access which project repository.
• TIBCO Administrator Enterprise Edition—Supports all functionality of
TIBCO Administrator Repository Edition with user and resource
management. In addition, deployment configuration and application
management components are automatically enabled and become available
from the TIBCO Administrator GUI if you purchased the Enterprise Edition
and chose to enable user and resource management.
Installable Components
During installation, the following components are installed:
• Tomcat (web server) 4.1.27
• TIBCO Administration Server running as a servlet under tomcat
• Optionally, TIBCO Administration Server user and resource management
component running under Tomcat.
• Optionally, TIBCO Administrator documentation. If you choose not to install
documentation, online help will not be available.
If you purchased the TIBCO Administrator Enterprise Edition, deployment

configuration and application management components are automatically
enabled and become available from the TIBCO Administrator GUI.

Introduction 3
|
Prerequisites
For a list of the required hardware and software, see the readme.txt for this
product.
Before you install TIBCO Administrator on a machine, you must install the
appropriate version of the TIBCO Runtime Agent (TRA). If TIBCO Runtime
Agent is not available, the installer will inform you and cannot continue.
A Note on Installing Releases with Higher Version Numbers

TIBCO products use a three-digit release number which makes it possible to
specify major, minor, and patch release. For example, release 2.1.3 means major
version 2, minor version 1, and patch 3.
• If you are installing using a patch 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, the TIBCO Domain Utility is not launched, and you are not
prompted to create a 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.1). The old installation is not removed, and must be uninstalled separately if
you wish to remove it.
In that case, the TIBCO Domain Utility is launched at the end of installation,
and you are prompted to create a domain or server.
If you install a product and that product is already installed on your machine, you
cannot choose a different location.
A Note on Upward Compatibility

If you install TRA 5.0.1 and TRA 5.1.3 on your machine, then install or re-install
TIBCO administrator 5.0.1, the tibcoadministrator.tra file must be changed.
Run the tramodify utility for the necessary changes.

|
Using the TIBCO Installer
The TIBCO Installer for ActiveEnterprise 5.1 products can run in different 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 make installation choices from the
command-line.
• Silent mode either installs using the default settings or uses a file that was
saved during an earlier installation.
If you wish to create an Administration Server only (and not include User and
Resource Management), you must run the installer in GUI mode.
You must invoke the installer from a command line if you wish to use one of the
options listed under Installer Startup Options on page 5.
GUI Mode
In GUI mode, the installer presents panels that allow you to make choices about
product selection, product location, and so on. When you invoke the installer by
double-clicking the icon, GUI mode is used.
Console Mode
Console mode allows you to run the installer from the command line. This is
useful if your machine does not have a windowing environment or if you wish to
install in silent mode.
Silent Mode
Silent mode installs without prompting you for information.
• If no response file has been recorded earlier and you invoke the installer with
the -silent argument, the default installation parameters are used.

Using the TIBCO Installer 5
|
• If a response file exists, and the installer is started with -options

<responseFileName> as an argument, the installer uses the values that were
specified by the user when the response file was generated.
The TIBCO Domain Utility is invoked only if you use GUI mode. Unless you are
doing an update or reinstall of TIBCO Administrator, using GUI mode is highly
recommended for TIBCO Administrator installation.
Installer Startup Options

When you start the installer from the command line, you can use the following
options:
-is:javaconsole Uses the console interface mode. Messages during installation are displayed on
-console the command line.
Examples:
TIB_tibcoadmin-simple_5.1.3_w32.exe -is:javaconsole -console
TIB_tibcoadmin-simple_5.1.3_s4_58_CC.bin -is:javaconsole -console
-options Specifies a response file to execute. A responses file contains command-line

<responseFile> options, one command per line, that set properties for the installation. You
generate the response file using -options-record, discussed next.
Examples:
TIB_tibcoadmin-simple_5.1.3_w32.exe -options C:\directory\<responseFileName>
TIB_tibcoadmin-simple_5.1.3_s4_58_CC.bin -options directory/<responseFileName>
-options-record Instructs the installer to automatically generate a response file for the product
<responseFile> after the completion of the installation
Examples:
TIB_tibcoadmin-simple_5.1.3_w32.exe -options-record C:\directory\<responseFileName>
TIB_tibcoadmin-simple_5.1.3_s4_58_CC.bin -options-record
directory/<responseFileName>
Note that there is no space between -options and -record.

|
-silent Specifies to install in silent mode, where the installation is performed with no user
interaction. By default, a typical installation is performed. You can also pass in a
response file if you generated one earlier.
Examples:
TIB_tibcoadmin-simple_5.1.3_w32.exe -silent
TIB_tibcoadmin-simple_5.1.3_s4_58_CC.bin -silent
Combining Options
You can combine the different available options. For example, to install in silent
mode using a response file, use:
TIB_tibcoadmin-simple_5.1.3_w32.exe -options <responseFileName>
-silent
To install using console mode and generate a response file, use:

TIB_tibcoadmin-simple_5.1.3_w32.exe -is:javaconsole -console
-options-record <responseFileName>

Installation Registry 7
|
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.
Do not edit, modify, rename, move, or remove vpd files.
Microsoft Windows Platforms

ActiveEnterprise 5.1 products maintain the installation registry in the
SystemDrive:\WINNT folder. The following files represent the installation
registry:
SystemDrive:\WINNT\vpd.properties
SystemDrive:\WINNT\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 Platforms
If installation is performed by a regular user (non-root), the installation registry is
maintained in the following files in the user's home directory:
User_Home_Directory/vpd.properties
User_Home_Directory/vpd.properties.tibco.systemName
If installation was 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 HPUX 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
vpdfiles.

|
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 HPUX, 85 MB of free disk space in /var/tmp.
• On AIX, 30 MB of free disk space in /tmp.
• On Linux, 50 MB of free disk space in /tmp.
• On Tru64, 64 MB of free disk space in the tmp directory which is created in the
user’s home directory.
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.

TIBCO Administrator Installation Overview 9
|
TIBCO Administrator Installation Overview
The installer allows you to perform a typical or custom installation:

• Typical. Installs the server and includes documentation
• Custom. Allows you to choose the components you wish to install:
— Administration Server.
— Documentation. If you decide not to install documentation, online help
from the TIBCO Administrator GUI will also not be available.
If you do not install the documentation, online help will not work.
At the end of installation, you are prompted to click a Next button, which
launches the TIBCO Domain Utility for server setup. This happens for new
installations as well as upgrade installations (e.g. 5.0.0 to 5.1.0) but not for update
or reinstall (e.g. 5.1.0 to 5.1.1).
You may cancel the domain utility and launch it later to enable user and research
management.
If you wish to disable user and resource management (repository server only),
you must perform setup as part of installation. You cannot cancel and restart the
domain utility later.
The Domain Utility presents a number of server configuration choices. The

choices include the following:
• Master or secondary server
• Enable user and resource management or run Administration Server without
that functionality.
• User corporate LDAP for domain data store (or not)
• Use TIBCO Rendezvous, HTTP, or HTTPS for communication between the
server and its clients.
Each screen of the Domain Utility includes a Help button that provides in-depth
additional information.

|
TIBCO Administration Domain
This section gives some introductory information about the TIBCO

Administration domain.
This information is relevant only if you did not disable the user and resource
management component.
TIBCO Administration Domain Architecture

A TIBCO administration domain is a collection of users, machines, and TIBCO
software components. The administration domain is monitored and managed by
the TIBCO Administration Server. Components within an administration domain
can communicate with systems outside the domain, but the administration
domain is the administrative boundary of an enterprise integration project.
A TIBCO administration domain consists of these elements:
• TIBCO Administration Server—Each administration server manages one

and only one TIBCO Administration domain. However, secondary servers can
be added to manage the administration domain.
• Machines—Each TIBCO administration domain contains one or more
machines. A machine can be added to an administration domain explicitly. By
default, all machines within an administration domain are expected to be in
the same network subnet. You can, however, set up your system to use TIBCO
Rendezvous rvrd so the server can communicate with components on
different subnets. See Chapter 5, Advanced Topics of the TIBCO Administrator
Server Configuration Guide.
A machine may belong to multiple domains.
• User and Access Information—User, role, and authorization information is
specified with the TIBCO Administrator GUI and stored in the domain data
store. Optionally, Corporate LDAP may be used for authorization.
• Projects—Projects are created at design-time by the developer with the TIBCO
Designer GUI and describes the services configuration for an application. At
deployment time, the TIBCO Administrator deployment component creates
projects that describe the deployment configuration.
• Deployment Configuration—You can use TIBCO Administrator to upload
one or more Enterprise Archive files and configure a corresponding
application. Enterprise Archive files are created in TIBCO Designer and
contain project data. The application associates its component services with

TIBCO Administration Domain 11
|
the machines on which they will run. It contains information about the
processes to be run, alerts, and so on.
• Runtime Application—After you have deployed the application, you can
start, stop, and monitor the individual business process engines and adapter
instances.
The advantage of an administration domain is that the components of your
integration project automatically know about each other. They can be monitored
as a group. Security, that is, required authentication and authorization for both
processes and data stores, is shared across the administration domain. Fault
tolerant setups are also possible.
Creating or Joining an Administration Domain

When you install TIBCO Administrator and choose to enable User and Resource
Management, the domain utility allows you to create a master Administration
Server and corresponding administration domain. If a master server is already
running, you can also create a secondary server.
The Domain Utility is launched at the end of installation for new installations as
well as upgrade installations (e.g. 5.0.0 to 5.1.0) but not for update or reinstall (e.g.
5.1.0 to 5.1.1).
You can later create additional servers and domains for you machine using the
domain utility, though this potentially resource-intensive option should not be
undertaken lightly.
If you wish to add a machine to an administration domain, you can do so using
the TIBCO Domain Utility. If you wish to register software to the domain, you can
do so using the TIBCO Administrator GUI for the domain.
Security
The TIBCO Administration Server supports centralized authentication and
authorization. Using the TIBCO Administrator GUI, users with the appropriate
administrative privileges can define which users should have access to which part
of the system.
TIBCO Administrator supports authentication and authorization for both data
stores (project repositories) and application components (process engines or
adapters) in the administration domain.
• Authentication—The verification of the identity of a person or process.

|
• Authorization—Permission to view or execute. An administrator gives users

access rights to the functionality of the product they need. For example, users
need authorization to view, change, or start an application. The TIBCO
Administration Server controls that access.
For example, only authorized users may create new users and give them access
privileges. Only authorized users may start or stop process engines or adapters.
This fine-grained user authorization scheme allows administrators to customize
the system to a company’s needs.
TIBCO Administrator also supports roles to facilitate user management.

Server Configuration Overview 13
|
Server Configuration Overview
After you have completed installation, the installer prompts you to click the Next
button to launch the TIBCO Domain Utility. The domain utility offers a number of
server configuration choices:
• Install Master Server with user and resource management (and create an
administration domain).
• Install Secondary Server to run inside an already existing administration
domain.
• Install a Master Server without user and resource management (no
administration domain is created)
• Install a Secondary Server for a server that was installed without user and
resource management.
• Retrieve users from corporate LDAP.
Figure 1 gives an overview of the available options.
Each screen of the TIBCO Domain Utility includes a Help button in the bottom
left corner. Click that button for information about the choices available in that
screen.

|
Figure 1 Domain Utility Server Configuration Choices
Master or Secondary?
Domain or No Domain?
Master & Domain Master & Secondary Master & No Domain Secondary & No Domain
(optionally RV and (must match Master RV (optionally RV and (must match Master RV
Hawk parameters) & Hawk parameters) Hawk Parameters) & Hawk parameters)
Select domain Supply server Supply master

& provide credentionals name server name
LDAP?
Database?
Done Supply
LDAP
Database password
Supply
LDAP & password
Config Database
LDAP Done
Config
Database
Done
Config
No LDAP
Config
Database
Confirm
Done

| 15
Chapter 1 Installation on Microsoft Windows Systems
This chapter discusses installation on Microsoft Windows systems.
Topics
• Installation Prerequisites, page 16

• Installing the Software, page 17

16
| Chapter 1 Installation on Microsoft Windows Systems
Installation Prerequisites
The following is a list of prerequisites for installing TIBCO Administrator on

Windows systems. See Installer Disk Space Requirements in Temporary Area on
page 7 for additional disk space requirements.
Table 1 Supported platforms, package names, service packs and disk space for Microsoft Windows
Platform Executable Name Service Pack Disk Space

Microsoft TIB_tibcoadmin-simple_5.1.3_w32.exe 2 50 MB
Windows 2000
Microsoft TIB_tibcoadmin-simple_5.1.3_w32.exe 50 MB
Windows XP
Installer Account
You must have administrator privileges to install this product.
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.
Memory Requirements for the Administration Server

The machine on which the TIBCO Administration server is installed should have
a minimum of 1 gigabyte of system memory.
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 to lower the heap size. The idea is not to
have
(heap size) + (memory required by the operating system) < memory of the
machine.
For example on Microsoft Windows, if you have 500MB memory, set the heap size
to no more than 300 MB because Windows itself requires about 200MB.

Installing the Software 17
|
Installing the Software
To install TIBCO Administrator, follow these steps:

1. Invoke the installer using the mode of your choice. See Using the TIBCO
Installer on page 4.
You must use GUI mode (the default) if you wish to disable user and resource
management (standalone server, no administration domain).
2. After the Welcome, License Agreement, and Notice panels, you are prompted
whether you wish to perform Typical or Custom installation.
— If you choose Typical, the Administration Server and documentation
installed.
— If you choose Custom, you may choose to install only the server, or both the
server and documentation.
3. The installer will then inform you which components are selected. After you
confirm, installation proceeds. See A Note on Installing Releases with Higher
Version Numbers on page 3 for the installer behavior during upgrades.
4. When installation is complete, the last screen prompts you with a Next button,
which launches the TIBCO Domain Utility. You can use the utility to configure
servers.
The Domain Utility is launched for new installations as well as upgrade

installations (e.g. 5.0.0 to 5.1.0) but not for update or reinstall (e.g. 5.1.0 to 5.1.1).
You may cancel the first screen of the Domain Utility; however, configuring the
server as part of installation is highly recommended.
Otherwise, you can later invoke the domain utility from the Start > Programs>
tibco > TIBCO Runtime Agent and Adapter SDK 5.1 menu.
If you wish to install a server and disable user and resource management
(repository server only), you must perform setup as part of installation. You
cannot cancel and restart the domain utility later.

18
| Chapter 1 Installation on Microsoft Windows Systems
Running the Administration Server Under Microsoft Windows
To run the server under Microsoft Windows, you must first start the TIBCO
Administration Server and TIBCO Hawk Microagent services. You can do so in
one of two ways:
• Reboot your machine. The services are started automatically.
• In the Microsoft Windows Services control panel, select each service and start
it. The order is not important.
You can then access the TIBCO Administrator GUI, as discussed in the TIBCO
Administrator User’s Guide.

| 19
Chapter 2 Installing the Software on UNIX Systems
This chapter explains how to install TIBCO Administrator on UNIX systems.
Topics
• Installation Prerequisites, page 20

• Installing TIBCO Administrator, page 22
• Running the Administration Server Under UNIX, page 23
• TIBCO Administration Domain, page 10

20
| Chapter 2 Installing the Software on UNIX Systems
Installation Prerequisites
Your operating system must meet the minimum patch requirements listed in
readme.txt. See Required Disk Space in Temporary Area on page 8 for additional
disk space requirements.
Table 2 Supported platforms, package names, and required disk space for UNIX systems
Disk
Platform Package Names Space
(MB)
Sun Solaris 2.6. TIB_tibcoadmin-epe-simple_5.1.3_s4_57_CC.bin or 177
TIB_tibcoadmin-repo-simple_5.1.3_s4_57_CC.bin or
2.7, or 8
HP-UX 11, 11i TIB_tibcoadmin-epe-simple_5.1.3_h7_110_aCC.bin or 348

TIB_tibcoadmin-repo-simple_5.1.3_h7_110_aCC.bin
IBM AIX 5.1 TIB_tibcoadmin-epe-simple_5.1.3_rs_51_xlrc.bin or 186

TIB_tibcoadmin-epe-simple_5.1.3_rs_51_xlrc.bin
Linux 2.4 TIB_tibcoadmin-epe-simple_5.1.3_lnx86_24_glibc.bin or 213

TIB_tibcoadmin-repo-simple_5.1.3_lnx86_24_glibc.bin
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 7 for more information.
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.
Windows Environment
A window environment such as CDE (i.e. X Windows) is required to run the
installer in GUI mode. It is not required for a console installation.
You must use GUI mode (the default) if you wish to disable user and resource
management (standalone server, no administration domain).

Installation Prerequisites 21
|
Tru64 Shell Requirement

Installation on Tru64 requires a POSIX-compliant Bourne Shell. Before you start
the installation, set environment as follows:
BIN_SH=xpg4; export BIN_SH // Bourne shell
setenv BIN_SH xpg4 // C-shell
If BIN_SH is not properly specified, the installer will abort with this error: ^D@AA:
is not an identifier
Memory Requirements for the Administration Server

The machine on which the TIBCO Administration server is installed should have
a minimum of 1 gigabyte of system memory.
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 to lower the heap size. The idea is not to
have
(heap size) + (memory required by the operating system) < memory of the
machine.

22
Installing TIBCO Administrator
This section discusses an installation of TIBCO Administrator.

Follow these steps:
1. Invoke the installer using the mode of your choice. See Using the TIBCO
Installer on page 4.
2. After the Welcome and License Agreement screens, you are prompted
whether you wish to perform Typical or Custom installation. For this
installation, Custom installation only offers not install the documentation.
3. The installer will then inform you which components are selected. After you
confirm, installation proceeds. See A Note on Installing Releases with Higher
Version Numbers on page 3 for the installer behavior during upgrades.
4. When installation is complete, you are prompted to click the Next button,
which launches the TIBCO Domain Utility. You can use the utility to configure
your repository server or TIBCO administration domain. The choices
displayed depend on the selection you made. See the TIBCO Domain Utility
online help.
The Domain Utility is launched for new installations as well as upgrade

installations (e.g. 5.0.0 to 5.1.0) but not for update or reinstall (e.g. 5.1.0 to 5.1.1).
You may cancel the first screen of the Domain Utility; however, configuring the
server as part of installation is highly recommended.
Otherwise, you can later invoke the domain utility on UNIX:
1. Navigate to the <tra_home>/tibco/tra/5.1/bin directory.
2. Execute domainutility.
If you wish to install a server and disable user and resource management
(repository server only), you must perform setup as part of installation. You
cannot cancel and restart the domain utility later.

Running the Administration Server Under UNIX 23
|
Running the Administration Server Under UNIX
To start the TIBCO Administration Server, follow these steps:

1. First start the server by typing the following into a command-line prompt:
% cd <administrator_home>/administrator/5.1/bin
% tibcoadmin_<domain-name>
2. Then start the TIBCO Hawk Agent, which performs the TIBCO Administrator
monitoring functions, by typing:
% cd <tra_home>/tra/5.1/domain/<domain_name>
% hawkagent_<domain-name>

24

| 25
Chapter 3 Setting up an Administration Server with a

Database Backend
The administration server can store application repositories in a database if set up

to do so. This chapter gives some background information.
Files are the preferred format, however, databases are supported as well.
Note that database backend is supported only for application repositories, not for
the domain repository.
Topics
• Introduction, page 26
• Creating the Database Tables, page 27

26
| Chapter 3 Setting up an Administration Server with a Database Backend
Introduction
The TIBCO Administration Server stores application repositories in files by

default. Using files is recommended, however, some users prefer using a database
backend. In that case, you need to do two things:
• Specify values for the database properties in the tibcoadmin<domain>.tra file.
See the TIBCO Administrator Server Configuration File, or look at the comments
in the file itself.
• Set up the database. See Creating the Database Tables on page 27
This chapter explains how to configure the required database tables and set up a
JDBC-based TIBCO Administration Server server on Windows or UNIX
platforms. For some additional information, see Appendix A, A Note on Database
Backends, in the TIBCO Administrator Server Configuration Guide.

Creating the Database Tables 27
|
Creating the Database Tables
Setting up a remote JDBC-based repository server involves creating the database

tables and running the database initialization script for your database.
Size Considerations
When creating a new database for use with TIBCO Administrator, configure the
database size to conform to the expected size of the ActiveEnterprise data you
will store. Size varies depending on the number and complexity of the
applications that use the project repository.
For a typical installation, configure the database to allow at least 30-40 MB of data
storage. The transaction log size for the database should be at least 20 MB. If you
are using Sybase, configure the server to truncate the transaction log on
checkpoints.
Normally, multiple users share a single database connection with a single user
name and password, which are specified in the tibcoadmin.tra file.
Running the Scripts

The scripts drop any existing tables before creating new tables. When upgrading
between versions that use different schemas, the schemas are automatically
upgraded. Initialization is only necessary for new servers.
Warning. The database initialization programs are destructive.
Scripts are provided for each of the supported databases. They can be found in
<install_home>/administrator/5.1/bin:
ORACLE 8.1 RepoOracleInit

SQLSERVER 7.0 RepoSqlInit
DB2 6.0 RepoDb2Init
Sybase 11.9.5 RepoSybaseInit
See Chapter 7, Utilities, in the TIBCO Administrator Server Configuration Guide for
information on running the scripts. See Reserved Database Tables for Storing
Repository Information on page 28 for information on the tables created by each
script.

28
| Chapter 3 Setting up an Administration Server with a Database Backend
Reserved Database Tables for Storing Repository Information

A normalized set of tables for storing the repository instances must be created in
the database. The tables should be reserved for exclusive use by TIBCO
Repository. The table names are given next.
Table 3 Database Tables
Name Description DB2 Oracle SqlServer Sybase

Version Maintains schema version number Y Y Y Y
Instance Keeps a list of instances Y Y Y Y
Instance_Info Stores properties for each instance Y Y Y Y
Node_V5 Stores a list of nodes Y Y Y Y
Assoc_Entries_V5 Stores node data. (Up to 2000 bytes N Y Y Y

for Oracle)
Assoc_Big_Entries Stores node data that exceeds 2000 N Y N N

bytes for a single node
Assoc_Chunk_5 Stores node data in chunks of up to Y N N N

3600 bytes
Global Vars Stores Global Substitution Variable Y Y Y YS

names and values

| 29
Appendix A Troubleshooting and FAQ
This appendix provides some troubleshooting information and answers to

frequently asked questions.
Topics
• Port/Address in Use Message, page 30

• Security Option Unavailable, page 30
• Installation on HPUX 11.00 64 bit Platform, page 30
• Installation on AIX 4.3 Platform, page 31
• Console/Silent Install and Server Creation, page 32
• Renaming Installation Directory, page 33
• DISPLAY Variable on UNIX, page 34

30
| 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 that the HTTP Port is in use is displayed, the port used by the
TIBCO Administration Server or TIBCO Repository Server servlet to
communicate with Tomcat (the web server) was not available. Use the 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, put 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.
Security Option Unavailable

If you first install TIBCO Administrator without the security component, and
then wish to install the security component, you must uninstall TIBCO
Administrator completely, then perform a new installation of both pieces.
Installation on HPUX 11.00 64 bit Platform
Setting Library Path

On HP-UX, you need to manually set the SHLIB_PATH before you start TIBCO
Administrator, as follows:
<TIBCO_HOME>/jre/1.4.1/PA_RISC2.0/hotspot:<TIBCO_HOME>/jre/1.4.1/P
A_RISC2.0:$SHLIB_PATH
Error
Error Message Installation on a HPUX 11.00 64 bit system may crash with the following error
message:
Pid nnn killed due to trashed stack.
Pid nnn was killed due to failure in writing the signal context.

Troubleshooting and FAQ 31
|
This happens only on HPUX 11.00 64 bit systems. It does not happen on HPUX
11.00 32 bit system and HPUX 11.11 (or 11.i) system.
To determine the OS version on your system, run:
uname -a
To determine the kernel bits on your system, run:

getconf KERNEL_BITS
Resolution HPUX kernel patch PHKL_27282, resolves the above crash.

To determine if your system has the kernel patch, run:
/usr/sbin/swlist -l product PHKL_27282
or
what /stand/vmunix | grep PHKL_27282
If your system is an HPUX 11.00 64 bit system and it does not have the patch, first
install HPUX kernel patch PHKL_27282 and then proceed with the installation.
Installation of patch PHKL_27282, will reboot your system.
Installation on AIX 4.3 Platform

Error Message On the AIX 4.3 system, the installer may produce the following error message and
create a core file. This happens after the Finish button is clicked at the end of
installation or whenever an installation is aborted.
SIGABRT received at d0103df4 in /usr/lib/libpthreads.a.
Writing stack trace to ... OK.
The installation however, completes successfully.

This happens only on an AIX 4.3 system and not on AIX 5.0.x systems. To
determine the OS version on your system, run:
uname -a
Resolution Apply 5.0.0.4 xlC libraries as indicated by APAR IY14529 and proceed with the
installation.
Dependency Resolution Fails on Some UNIX Platforms

Problem On some platforms (HPUX & 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.

32
Cause 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.
Resolution 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/Silent Install and Server Creation

Question When I run the installer in console mode, the domain utility is not launched
afterwards. How can I create my server or domain?
Answer You cannot create a standalone Administration Server (no user and resource
management) if you perform a console install. Instead, you must install in GUI
mode.
You can create an administration domain by launching the domain utility:
• Windows: Start > Programs > tibco > TIBCO Runtime Agent and Adapter
SDK 5.1 > Domain Utility.

Troubleshooting and FAQ 33
|
• UNIX: <tibco_home>tra/5.1/bin/domainutility
Renaming Installation Directory

Question Can I rename the installation directory after installation?
Answer If you rename the installation directory, unexplainable problems with

functionality will result. DO NOT rename the directory.

34
DISPLAY Variable on UNIX

Question Why and how should I set the DISPLAY variable on UNIX platforms for GUI
mode?
Answer The installer on UNIX, must open an additional window, generally for graphics. It
uses the DISPLAY environment variable to tell it on what computer to open the
window. If the environment variable is not set, the installer will either wait or
abort after displaying:
InstallShield Wizard
Initializing InstallShield Wizard...
Preparing Java(tm) Virtual Machine...
...................................
...................................
........
The DISPLAY variable must be set to the IP address or name of the computer (on
which the installer graphics window are to be displayed), followed by a screen
address, which can be :0.0. For example:
# Bourne shell
DISPLAY=<ip_address>:0.0; export DISPLAY
# Korn shell
export DISPLAY=<ip_address>:0.0
# C-shell
setenv DISPLAY <ip_address>:0.0
For example, consider a scenario where you need to install the adapter on a
remote 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 monitor

alaska> telnet itaska
Welcome to HPUX itaska 11.00
User:
Password:
itaska> export DISPLAY=alaska:0.0 # set display on alaska
itaska> TIB_designer-simple_5.0.1_h7_110.bin

Zindagi

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Zindagi

Diunggah oleh

Hak Cipta:

Format Tersedia

TIBCO Administrator™

Chapter 1 Installation on Microsoft Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 2 Installing the Software on UNIX Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

TIBCO Administrator Installation Guide

Chapter 3 Setting up an Administration Server with a Database Backend. . . . . . . . . . . . . . . . 25

Appendix A Troubleshooting and FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

TIBCO Administrator Installation Guide

This software may be available on multiple operating systems. However, not

TIBCO Administrator allows administrators and end users to manage user

• Related Documentation, page vi

TIBCO Administrator Installation Guide

This section lists documentation resources you may find useful.

TIBCO Administrator Documentation

Other Product Documentation

TIBCO Administrator Installation Guide

How to Contact TIBCO Customer Support

TIBCO Administrator Installation Guide

TIBCO Administrator Installation Guide

This chapter introduces TIBCO Administrator installable components and

TIBCO Administrator Installation Guide

If you purchased the TIBCO Administrator Enterprise Edition, deployment

TIBCO Administrator Installation Guide

A Note on Installing Releases with Higher Version Numbers

A Note on Upward Compatibility

TIBCO Administrator Installation Guide

Using the TIBCO Installer

TIBCO Administrator Installation Guide

• If a response file exists, and the installer is started with -options

Installer Startup Options

TIB_tibcoadmin-simple_5.1.3_w32.exe -is:javaconsole -console

TIB_tibcoadmin-simple_5.1.3_s4_58_CC.bin -is:javaconsole -console

-options Specifies a response file to execute. A responses file contains command-line

TIB_tibcoadmin-simple_5.1.3_w32.exe -options C:\directory\<responseFileName>

TIB_tibcoadmin-simple_5.1.3_s4_58_CC.bin -options directory/<responseFileName>

TIB_tibcoadmin-simple_5.1.3_w32.exe -options-record C:\directory\<responseFileName>

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

TIBCO Administrator Installation Guide

To install using console mode and generate a response file, use:

TIBCO Administrator Installation Guide

The installer maintains an installation registry. The registry location depends on

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

Microsoft Windows Platforms

Installer Disk Space Requirements in Temporary Area

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

If installation was performed by a super-user (root), the installation registry is

TIBCO Administrator Installation Guide

Required Disk Space in Temporary Area

where <new_tmp> has sufficient free disk space.

Required Disk Space in User's Home Directory

TIBCO Administrator Installation Guide

TIBCO Administrator Installation Overview

The installer allows you to perform a typical or custom installation:

The Domain Utility presents a number of server configuration choices. The

TIBCO Administrator Installation Guide

TIBCO Administration Domain

This section gives some introductory information about the TIBCO

TIBCO Administration Domain Architecture

• TIBCO Administration Server—Each administration server manages one

TIBCO Administrator Installation Guide

Creating or Joining an Administration Domain

TIBCO Administrator Installation Guide

• Authorization—Permission to view or execute. An administrator gives users

TIBCO Administrator Installation Guide