Académique Documents
Professionnel Documents
Culture Documents
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 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi TIBCO Administrator Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii How to Contact TIBCO Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Installation Prerequisites on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Installation Prerequisites on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Installing Releases with Higher Version Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Installation Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Microsoft Windows Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 UNIX Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Installing TIBCO Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Uninstalling TIBCO Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 To Uninstall TIBCO Administrator on Microsoft Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 To Uninstall TIBCO Administrator on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
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
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.
Topics
Related Documentation, page vi Typographical Conventions, page viii How to Contact TIBCO Support, page x
vi
| Related Documentation
Related Documentation
This section lists documentation resources you may find useful.
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
code font
Use Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example: Use M y C o m m a n d to start the foo process.
Bold code font is used in the following ways: In procedures, to indicate what a user types. For example: Type a d m i n . 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, M y C o m m a n d is enabled: MyCommand [e n a b l e | 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: M y C o m m a n d 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
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 p a r a m 1 and p a r a m 2 , or the pair p a r a m 3 and p a r a m 4 .
MyCommand {param1 param2} | {param3 param4}
In the next example, the command requires two parameters. The first parameter can be either p a r a m 1 or p a r a m 2 and the second can be either p a r a m 3 or p a r a m 4 :
MyCommand {param1 | param2} {param3 | param4}
In the next example, the command can accept either two or three parameters. The first parameter must be p a r a m 1 . You can optionally include p a r a m 2 as the second parameter. And the last parameter is either p a r a m 3 or p a r a m 4 .
MyCommand param1 [param2] {param3 | param4}
|1
Chapter 1
Installation Overview
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
| 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 Users 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 Users 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 Users 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 Users Guide for details. For certain advanced configuration tasks, you can edit the t i b c o a d m i n _ domain. t r a 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.
| Chapter 1
Installation Overview
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 Database versions: 2000 2005 Drivers: DataDirect 3.7 Microsoft JDBC driver
IBM DB2 Universal Database Database versions: 8.2 FixPak 3 9 (added) Drivers: com.ibm.db2.jcc.DB2Driver 2.6 (Thin-driver)
| Chapter 1
Installation Overview
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. You must use the 64-bit installer for TIBCO Administrator if you used the 64-bit installer for TIBCO Runtime Agent. 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.
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. The heap size set in t i b c o a d m i n _ domain. t r a (j a v a . h e a p . s i z e . m a x = 5 1 2 m ) 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. Special Note for Windows 2003 On Windows 2003, for machines that do not have service pack 1 installed, the installer creates the vpd property files in the users home directory rather than c:\windows. Because TIBCO Hawk agent only searches for . v p d 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 users home directory. For example:
c d C : \ D o c u m e n t s a n d S e t t i n g s \ user-name
2. Copy the vpd files to c:/windows. For example: copy vpd.* c:/windows
| Chapter 1
Installation Overview
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. You should use the 64-bit installer for TIBCO Administrator if you used the 64-bit installer for TIBCO Runtime Agent. 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. 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 (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. The heap size set in t i b c o a d m i n _ domain. t r a (j a v a . h e a p . s i z e . m a x = 5 1 2 m ) 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.
10
| Chapter 1
Installation Overview
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 v p d as a prefix, which stands for Vital Product Database. Do not edit, modify, rename, move, or remove v p d files.
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.
Installer Disk Space Requirements in Temporary Area The entire package is extracted into a temporary folder, typically SystemDrive: \ T e m p or SystemDrive: \ D o c u m e n t s a n d S e t t i n g s \ user_name\ L o c a l 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/ v p d . p r o p e r t i e s User_Home_Directory/ v p d . p r o p e r t i e s . t i b c o . 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
TIBCO Administrator Installation
12
| Chapter 1
Installation Overview
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 p k g i n f o database. On HP-UX the installation registry is maintained in s w i n s t a l l database. On AIX the installation registry is maintained in / u s r / l i b / o b j r e p o s directory as two v p d files and in the i n s t a l l p database.
vpd
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 / v a r / t m p . On HP-UX, 85 MB of free disk space in / v a r / t m p . On AIX, 30 MB of free disk space in / t m p . On Linux, 50 MB of free disk space in / t m p .
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:
- i s : t e m p d i r / 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 v p d files) is maintained in the user's home directory. As more products are installed, entries are added into these v p d files. The user's home directory must at least have 500 KB of free disk space.
| 13
Chapter 2
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
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. 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. 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 - s i l e n t argument, default installation parameters are used. If a response file exists, and the installer is started with - o p t i o n s responseFile as an argument, the installer uses the values that were specified when the response file was generated.
Installation Options 15
16
| Chapter 2
18
| Chapter 2
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
TIBCO Administrator Installation
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.
20
| Chapter 2
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 Users 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.
22
| Chapter 2
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. It is recommended that you use a third-party vendor-supplied driver instead of the deprecated DataDirect drivers. 10. A summary dialog appears listing the choices you made. You can click the Back button to change a choice.
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. These services will be cofigured to automatically start at system boot time.
You can then access TIBCO Administrator, as discussed in TIBCO Administrator Users Guide.
24
| Chapter 2
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.
26
| Chapter 2
| 27
Appendix A
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
or A d d r e s s
in Use
If a message displays indicating P o r t i n U s e , 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 t c p _ t i m e _ w a i t _ i n t e r v a l . For example, on Solaris, place the following line at the end of the file / e t c / r c 2 . d / S 6 9 i n e t
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 / s b i n / r c 2 . d and is named S 0 0 8 n e t . i n i t . Find and kill the two TIBCO Rendezvous (rvd) processes.
On Unix platforms, the installer registry file is located in the user's home directory. Case 1: If v p d . p r o p e r t i e s . t i b c o . s y s t e m N a m e file exists
Example:
$ cd ~ $ ln -s vpd.properties.tibco.upside vpd.properties.tibco.upside.tibco.com
Example:
$ cd ~ $ ln -s vpd.properties.tibco.upside.tibco.com vpd.properties.tibco.upside
30
| Appendix A
32
| Appendix A
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 D I S P L A Y = ip_address: 0 . 0 ; e x p o r t D I S P L A Y # Korn shell e x p o r t D I S P L A Y = 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 i t a s k a ). Because you have a Solaris 5.6 machine (named a l a s k a ) 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 i t a s k a from alaska. When you telnet to i t a s k a , you will not get access to i t a s k a 's monitor and will be unable to display an X-window application. That is why you must set the D I S P L A Y 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 D I S P L A Y 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
| 33
34
| 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
| 37
38
| 39
Index
A
access information 3 ACL roles 3 administration domain unique name 9, 15 architecture TIBCO administration domain 2 authentication 3 authorization 3
J
joining a domain 4
M
machines 3
N C
components installation 5 TIBCO administration domain 2 creating a TIBCO domain 4 customer support ix name of domain 9, 15
P
prerequisites for TIBCO BusinessWorks 7 projects 3
D
domain name unique 9, 15
R
roles 3
I
installation components 5 prerequisites 7 procedure 8, 10, 14, 15 TIBCO domain products 4
S
security 3 authentication 3 authorization 3 roles 3 support, contacting ix
40
| Index
T
technical support ix TIBCO administration domain architecture 2 components 2 creating 4 joining 4 TIBCO Administration Server 2 TIBCO BusinessWorks components 5 installation 8, 10, 14, 15 installing components 5 prerequisites 7 TIBCO domain setup 4 TRA 2
U
user information 3