Tib RV Installation
Tib RV Installation
ii
|
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 Rendezvous 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, Rendezvous, TIBCO Rendezvous and Messaging Appliance 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 19972010 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information
| iii
Contents
Chapter 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Before You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Directory Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Platform-Specific Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Chapter 2 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Before You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Running rvd with Increased Scheduling Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Size and Time to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Installing Several Instances on One File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Mount the Distribution Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Select the Installation Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Run the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Older Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Review the Administrators Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
iv
| Contents
Windows Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Review the Administrators Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 4 VMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Log In as SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Check TCP/IP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Obtain the Installation Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 ZIP Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 File Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Mount the Distribution Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Check Storage Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Install the Rendezvous Product Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Verify Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Daemon Privilege and Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 OPER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 ALTPRI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Starting the Rendezvous Daemon at Boot Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Parameters for rvd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Byte Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Total Non-Paged Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Page File Quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 29 29 30 30
User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Review the Administrators Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 C++ Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Rebuilding the C++ Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Additional Information for VMS Programmers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Compile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Chapter 5 IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Run the Installation Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Post-Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Check the AAREADME File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Review the Administrators Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Contents v
Destination Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Installer Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Installer Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Install TIBCO Rendezvous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Install in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Install in Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Install in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Uninstalling the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Uninstall in GUI Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Uninstall in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
vi
| Contents
| vii
Figures
Figure 1
viii
| Figures
| ix
Tables
Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11
General Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Syntax Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Distribution Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Installation Procedure by Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 UNIX Installation Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Microsoft Windows Distribution Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 VMS Distribution Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 VMS Distribution Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 VMS Installation Size (in blocks) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 IBM i Distribution Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Universal UninstallerCommand Line Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
| Tables
| xi
xii
| xiii
Preface
This manual describes installation of TIBCO Rendezvous software. It is part of the documentation set for Rendezvous Software Release 8.3.0.
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
Manual Organization, page xiv Related Documentation, page xv Typographical Conventions, page xvii How to Contact TIBCO Customer Support, page xx
xiv
| Manual Organization
Manual Organization
This book includes one chapter for each group of related operating system platforms.
Preface xv
Related Documentation
This section lists documentation resources you may find useful.
xvi
| Related Documentation
TIBCO Rendezvous Administration Begins with a checklist of action items for system and network administrators. This book describes the mechanics of Rendezvous licensing, network details, plus a chapter for each component of the Rendezvous software suite. Readers should have TIBCO Rendezvous Concepts at hand for reference. TIBCO Rendezvous Configuration Tools Detailed descriptions of each Java class and method in the Rendezvous configuration API, plus a command line tool that can generate and apply XML documents representing component configurations. Readers should already be familiar with the Java programming language, as well as the material in TIBCO Rendezvous Administration. TIBCO Rendezvous Installation Includes step-by-step instructions for installing Rendezvous software on various operating system platforms. TIBCO Rendezvous Release Notes Lists new features, changes in functionality, deprecated features, migration and compatibility information, closed issues and known issues.
Preface xvii
Typographical Conventions
The following typographical conventions are used in this manual. Table 1 General Typographical Conventions Convention
TIBCO_HOME TIBRV_HOME
Use All TIBCO products are installed under the same directory. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco. TIBCO Rendezvous installs into a version-specific directory inside TIBCO_HOME. This directory is referenced in documentation as TIBRV_HOME. The value of TIBRV_HOME depends on the operating system. For example on Windows systems, the default value is C:\tibco\rv\8.3.0.
code font
Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example: Use MyCommand to start the foo process.
Bold code font is used in the following ways: In procedures, to indicate what a user types. For example: Type admin. In large code samples, to indicate the parts of the sample that are of particular interest. In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled:
MyCommand [enable | disable]
italic font
Italic font is used in the following ways: To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts. To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal. To indicate a variable in a command or code syntax that you must replace. For example: MyCommand pathname
Table 1 General Typographical Conventions (Contd) Convention Key combinations Use 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.
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
Preface xix
Use A logical group of items in a command. Other syntax notations may appear within each logical group. For example, the following command requires two parameters, which can be either the pair param1 and param2, or the pair param3 and param4.
MyCommand {param1 param2} | {param3 param4}
In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4:
MyCommand {param1 | param2} {param3 | param4}
In the next example, the command can accept either two or three parameters. The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4.
MyCommand param1 [param2] {param3 | param4}
xx
|1
Chapter 1
Introduction
This manual contains step-by step instructions for installing TIBCO Rendezvous software, release 8.3.0.
Topics
Before You Install, page 2 Platform-Specific Installation Procedures, page 4
| Chapter 1
Introduction
Directory Structure 3
Directory Structure
When you install Rendezvous software, the installation directory contains these subdirectories: Table 3 Distribution Directories Subdirectory
bin
Status Required to develop or run Rendezvous programs. Contents: executable files, shared libraries (DLL files).
Required to develop Rendezvous programs. Required to develop Rendezvous programs. Optional on-line documentation (PDF and HTML). Optional source code for example programs.
| Chapter 1
Introduction
|5
Chapter 2
UNIX
Topics
Before You Install, page 6 Mount the Distribution Media, page 7 Select the Installation Package, page 8 Run the Installer, page 10 Review the Administrators Checklist, page 11
| Chapter 2
UNIX
| Chapter 2
UNIX
Table 5 UNIX Installation Directories (Sheet 1 of 2) OS General Information The following UNIX installer packages include both 32-bit and 64-bit components, except as noted below. AIX 5.2, 5.3, 6.1 Free BSD 6.2 IBM RS/6000 Intel
aix52_power fbsd6_x86
Hardware
Notes
32-bit and 64-bit components. 32-bit components only. Uses an older version of the universal installer. Does not support RVDM. Does not support Java.
macosx104_power
Table 5 UNIX Installation Directories (Sheet 2 of 2) OS Novell SUSE Linux Enterprise 10 SP1 Red Hat Enterprise Linux 4, 5 (AS, ES) Red Hat Enterprise Linux 5 (Advanced Platform, Classic) Red Hat Enterprise Linux 4 (AS, ES) IA64 (Itanium)
linux24gl23_ia64
Notes
linux26gl23_x86
Does not support RVDM. Requires older installer. 64-bit components only.
Solaris 10
Solaris 9
Does not support RVDM. Does not support port reuse. Does not support Java. Requires older installer. 64-bit components only.
10
| Chapter 2
UNIX
Older Installer
1. Change working directory to the directory you selected in step 1. For example:
$ cd
CD_mount_point/TRU6451/ALPHA
(Some operating systems translate the name of this program into upper case INSTALL.) The Rendezvous installation program copies the required files. To abort the installation at any time, press the interrupt key, (on most platforms, Control-c). The Rendezvous installation process prompts you to answer questions about the installation. Default answers appear inside brackets. To select the default answer, press the Return key. When answering installation questions: it is equivalent to type yes or y; it is equivalent to type no or n; upper and lower case are equivalent. Several UNIX platforms include their own installation facilities (for example, Solaris). The Rendezvous installation program cooperates with some of the these facilities, and transfers control to them, if you desire. 3. Add the directory $TIBRV_DIR/lib to the library path environment variable. You can find the name of this variable in the installer output.
12
| Chapter 2
UNIX
| 13
Chapter 3
Microsoft Windows
The Rendezvous installation procedures for all Windows platforms are identical. Images in this chapter might not exactly match the images on your screen.
Topics
Mount the Distribution Media, page 14 Select and Run the Installer, page 15 Check the README File, page 16 Windows Registry, page 17 Review the Administrators Checklist, page 18
14
| Chapter 3
Microsoft Windows
Installer Package
TIB_rv_8.3.0_win_x86_vc8.zip
Notes For developers using Visual Studio 2005 (VC8) and Visual Studio 2008 (VC9).
For developers using Visual Studio 2005 (VC8) and Visual Studio 2008 (VC9).
16
| Chapter 3
Microsoft Windows
Windows Registry 17
Windows Registry
You can arrange for Rendezvous components to run automatically by registering them as Microsoft Windows services. See Register Windows Services on page 8 in TIBCO Rendezvous Administration Windows Services on page 413 in TIBCO Rendezvous Administration.
18
| Chapter 3
Microsoft Windows
| 19
Chapter 4
VMS
Follow these instructions to install Rendezvous software on VMS platforms. Installation on VMS platforms uses the VMSINSTAL utility, which is described in the OpenVMS system management documentation. VMS does not support the PGM variant.
Topics
Log In as SYSTEM, page 20 Check TCP/IP Services, page 21 Obtain the Installation Package, page 22 Mount the Distribution Media, page 23 Install the Rendezvous Product Software, page 25 Verify Installation, page 26 Daemon Privilege and Priority, page 27 Starting the Rendezvous Daemon at Boot Time, page 28 Parameters for rvd, page 29 User Accounts, page 31 Review the Administrators Checklist, page 32 Additional Information for VMS Programmers, page 34
20
| Chapter 4
VMS
Log In as SYSTEM
Log in to the SYSTEM account.
Although you can successfully install the Rendezvous files without running TCP/IP services, the Rendezvous installation verification procedure will fail if TCP/IP services have not been started.
22
| Chapter 4
VMS
Notes
TIB_rv_8.3.0_vms82_ia64.zip
ZIP Files
Installation packages are zipped (compressed) using the VMS free software ZIP utility. To preserve the file attributes, unzip them on a VMS computer (and not on a PC or UNIX computer). Utilities to decompress zip files are available on the HP OpenVMS Freeware distributions, or at the HP web site:
http://h71000.www7.hp.com/openvms/freeware/index.html?jumpid=/go/openvms/freeware
File Attributes
When copying VMS save sets through a Windows PC or UNIX computer, the resulting files do not retain the proper file attributes. As a result, the VMS BACKUP utility cannot read them to install them. To rectify this situation, copy the files to a computer running VMS, and use this command to restore the correct file attributes:
$ SET FILE/ATTR=(RFM:FIX,RAT:NONE,LRL:8192) TIBRV*.%
DVD_device
24
| Chapter 4
VMS
2. Change the default directory to the root directory of the DVD drive, or transfer the installation package zip file to a disk directory and change the default directory to that directory. For example:
$ set default DQA0:[000000]
installation_package -d DKA100:[kits.rv-8-3-0]
4. Retrieve and read the release notes, which are in the sys$help directory. For example, to retrieve the release notes without installing Rendezvous software, use these commands:
$ @sys$update:vmsinstal tibrv-083 dka100:[kits.rv-8-3-0] $_ options N
5. Install the product software. Specify the product name and directory on the command line to VMSINSTAL. For example:
$ @sys$update:vmsinstal tibrv-8-3-08-3-0 dka100:[kits.rv-8-3-0]
26
| Chapter 4
VMS
Verify Installation
We recommend that you verify correct operation of Rendezvous software. You can verify installation at any time by invoking the command TIBRV:[COM]QUICK_TEST.COM. The test procedure starts the Rendezvous daemon, starts a listening program, and sends three messages. The listening program receives the three messages and displays them on the screen or console. Then the procedure prints a sample of correct output. Visually compare the sample with the actual results above it. If they match in all details except for process ID numbers and timestamps, then Rendezvous software is installed and operating correctly.
OPER
To send multicast and broadcast messages, the Rendezvous daemon must have OPER privilege. Without this privilege, Rendezvous programs will not be able to create transport objects. The best way to ensure this privilege is to install the Rendezvous daemon with OPER privilege. The file TIBRV_STARTUP.COM does this automatically.
ALTPRI
The Rendezvous daemon process is as an extension of the operating systems network device driver. To avoid data loss, it must respond immediately to network I/O. To ensure immediate response, the daemon must run at elevated prioritypreempting interactive users and the processes that support them. The daemon executable always runs with ALTPRI privilege, which enables elevated priority. This privilege is in effect whether the daemon starts automatically or explicitly. You do not need to configure anything to set this privilege.
28
| Chapter 4
VMS
However, it is not necessary to start the Rendezvous daemon at boot time, because programs start it automatically as needed.
Byte Limit
High message rates consume significant space in non-paged storage. The byte limit parameter restricts the amount of non-paged storage that a VMS process can use. If rvd fails during accept(), exceeding its byte count quota, raise this resource limit. The Rendezvous daemon requires sufficient non-paged buffer space for messages. The actual requirement depends on the speed of the network, the network card, the processors, and the message data rate. We recommend a value of 6000000.
Boot Time
When starting the Rendezvous daemon at boot time, the SYSTEM accounts bytlm parameter controls this resource limit. To set this parameter, modify these commands appropriately:
$ set def sys$system $ run authorize UAF> mod SYSTEM /bytlm=6000000
Automatic Start
When programs start the Rendezvous daemon automatically, the SYSGEN parameter PQL_DBYTLM specifies this resource limit. Set an appropriate value using the AUTOGEN tool.
If the pool is too small, use the AUTOGEN tool to set an appropriate size.
30
| Chapter 4
VMS
When starting the Rendezvous daemon at boot time, the SYSTEM accounts pgflquo parameter controls this resource limit. To set this parameter, modify these commands appropriately:
$ set def sys$system $ run authorize UAF> mod SYSTEM /pgflquo=1000000
Automatic Start
When programs start the Rendezvous daemon automatically, the SYSGEN parameter PQL_DPGFLQUOTA controls this resource limit. Set an appropriate value using the AUTOGEN tool.
Channel Count
In addition to the usual requirements for I/O channels, rvd uses I/O channels in two more ways: Each client connection from a network transport object consumes one channel. Each UDP and PGM service that those clients access consumes one channel.
The special SYSGEN parameter CHANNELCNT determines the maximum number of I/O devices that a process can access. Although most systems set a sufficiently high value, we recommend that you estimate the number of channels that rvd requires, and verify that the limit is significantly larger than your estimate. For example:
$ mc sysgen SYSGEN> show channelcnt
If rvd fails during accept(), reporting invalid I/O channels, raise this resource limit using the AUTOGEN tool.
User Accounts 31
User Accounts
To run Rendezvous programs, user accounts must have netmbx and tmpmbx privileges. Rendezvous programs accept command line arguments. To set up these arguments, each user must execute TIBRV:[COM]TIBRV_SETUP.COM. As a convenience, we recommend referencing it in each users login.com file.
32
| Chapter 4
VMS
C++ Library 33
C++ Library
This section describes an inconsistency in the behavior of the HP C++ compiler. On HP Integrity servers, version 7.3 of the C++ compiler uses a different name mangling algorithm than version 7.1 used. As a result, programs compiled using C++ compiler V7.3, cannot correctly link libraries compiled using C++ compiler V7.1. The Rendezvous C++ library in the installation package for OpenVMS Integrity is compiled using C++ compiler V7.1. This library is not compatible with C++ compiler V7.3 on HP Integrity hardware. If you are installing Rendezvous software on a computer where this library is incompatible, you must rebuild the library from the source code (see Rebuilding the C++ Library, below). (On OpenVMS Alpha we have not seen this type of incompatibility with C++ compilers.)
To recreate the Rendezvous C++ library, TIBRV:[LIB]LIBTIBRVCPP.OLB, do these steps: 1. Log on using the SYSTEM account. 2. Execute this command:
$ @TIBRV:[COM]MAKE_LIBRVCPP
This procedure compiles the source modules using the system default C++ compiler, creates the object library, and copies it to the TIBRV:[LIB] directory.
34
| Chapter 4
VMS
Compile
On VMS platforms, Rendezvous programmers must define the C-compile command appropriately. For the HP C compiler:
$ CC :== CC/FLOAT=IEEE/IEEE_MODE=UNDERFLOW_TO_ZERO /PREFIX=ALL/INCLUDE_DIRECTORY=("/tibrv/include",[])
Rendezvous programmers using C++ (CXX) must define the CXX-compile command appropriately. For the HP C++ compiler:
$ CPP :== CXX/FLOAT=IEEE/IEEE_MODE=UNDERFLOW_TO_ZERO /PREFIX=ALL/WARNINGS=DISABLE=EXTRASEMI /INCLUDE_DIRECTORY=("/tibrv/include",[])
Link
Rendezvous API libraries are multi-threaded, so VMS scheduler upcalls can yield significant performance improvements:
$ LINK/THREADS_ENABLE=UPCALLS
Migrating to Release 8.x Forward Migration In general, applications linked with shareable images migrate forward to new versions of TIBCO Rendezvous without any need to relink; they usually operate smoothly with newer shareable images. Exception: In Rendezvous release 8.0, we reorganized the Rendezvous shareable image libraries on OpenVMS platforms, in order to resolve issues with third-party libraries. As a result, you must relink applications linked with shareable image libraries when you upgrade across this division (from 7.5.4 or earlier, to 8.0 or later, on OpenVMS). Older Shareable Libraries Applications that link with sharable images usually cannot run with older shareable libraries (from earlier Rendezvous releases). The reason is that new
releases can introduce new entry points, which are absent from older shareable libraries. This incompatibility can cause problems if you link an application against a current shareable library, and then distribute it to other host computers where it runs with older shareable libraries.
36
| Chapter 4
VMS
| 37
Chapter 5
IBM i
Follow these instructions to install Rendezvous software on IBM i platforms. Installation on IBM i platforms uses the RSTLICPGM command, which is described in the IBM i operating system documentation.
Topics
Requirements, page 38 Run the Installation Program, page 39 Post-Installation Instructions, page 41 Check the AAREADME File, page 43 Review the Administrators Checklist, page 44
38
| Chapter 5
IBM i
Requirements
Rendezvous software requires IBM i with TCP/IP installed. For details, see the IBM document TCP/IP Fastpath Setup. IBM i does not support the PGM variant.
2. On a Windows-based or UNIX-based system, unzip the installation package in a temporary location. 3. On an IBM i system, do these steps: a. Login as QSECOFR. b. Create a save file on your IBM i system called TIBRV. Use the command CRTSAVF to do this. c. Copy the save file (TIBRV.SAV) from the temporary (unzip) directory to the save file you created in step b. 4. If another version of TIBCO Rendezvous is installed on your system, you must uninstall it before installing this version. a. Ensure that no TIBCO Rendezvous programs are running, and that TIBRV is not in any users library list. b. Use this command to uninstall:
DLTLICPGM LICPGM(2TRV400) RLS(*ALL)
c. Remove files from the Integrated File System (IFS). Execute this command from the Command Entry screen:
QSH CMD(rm -rf /usr/tibco/tibrv)
libname is the library where you created the save file, in step 3b.
40
| Chapter 5
IBM i
6. To use Java, or to run or develop in the qsh environment, do this step after RSTLICPGM completes: a. Create a tibco directory in /usr (if it doesn't exist already).
CRTDIR ('/usr/tibco/tibrv')
b. Restore the file containing the Java files and the IFS file structure.
RST DEV('/qsys.lib/tibrv.lib/tibrvifsfl.file') OBJ(('/usr/tibco/tibrv/*'))
This command restores files to be placed in the Integrated File System in the directory /usr/tibco, and places the .jar files for Java support in /usr/tibco/tibrv/lib. It also creates symbolic links back to the installed programs, service programs and source files so that you can run and develop programs in qsh as you would in a UNIX or Windows environment. Figure 1 IBM i: Beginning the Installation
Restore Licensed Program (RSTLICPGM) Type choices, press Enter. Product . . . . . . . . . . . > Device . . . . . . . . . . . . > + for more values Optional part to be restored . Type of object to be restored Language for licensed program Output . . . . . . . . . . . . . Release . . . . . . . . . . . Replace release . . . . . . . . Save file . . . . . . . . . . . Library . . . . . . . . . . . 2TRV400 Character value *SAVF Name, *SAVF *BASE *ALL *PRIMARY *NONE *FIRST *ONLY TIBRV QTEMP *BASE, 1, 2, 3, 4, 5, 6,7... *ALL, *PGM, *LNG Character value, *PRIMARY... *NONE, *PRINT Character value, *FIRST Character value, *ONLY, *NO Name Name, *LIBL, *CURLIB More... F12=Cancel
Post-Installation Instructions 41
Post-Installation Instructions
1. The initial library list must contain the Rendezvous library (TIBRV is the default library name). Edit all relevant job descriptions to include it. 2. Rendezvous software requires multi-threading. Edit all relevant job descriptions to enable multiple threads. The example job description TIBRV/TIBRV illustrates items 1 and 2.
3. If your IBM i system is configured with a fully-qualified domain name, ensure that the host table entry for your system contains the full name of the computer. For example, if your domain name is mycompany.com, and the machine name is mymachine, then put mymachine.mycompany.com in the host table. 4. For Java programs, set the CLASSPATH environment variable to include /usr/tibco/tibrv/lib/tibrvj.jar. 5. To run Rendezvous programs using qsh, you must first set the environment variable QIBM_MULTI_THREADED to the value Y (before starting qsh). To set the values of items 4 and 5 automatically, create a CL program similar to this example, and set the INLPGM parameter in the user profile to run it automatically when the user logs in.
PGM ADDENVVAR ADDENVVAR /* start it */ /* For Java with qsh, set these vars */ ENVVAR(QIBM_MULTI_THREADED) VALUE(Y) ENVVAR(CLASSPATH) + VALUE(/usr/tibco/tibrv/libtibrvj.jar)
Whether you set the variables manually or automatically, their values persists until logout. 6. IBM imposes limitations on multi-threaded programs. Remember that all Rendezvous programs are inherently multi-threaded. You must run multithreaded programs either in batch or interactive batch subsystemsnot in the interactive subsystem. When submitting jobs using SBMJOB, set the ALWMLTTHD parameter to (*YES).
42
| Chapter 5
IBM i
You cannot run multi-threaded programs in the interactive environment. In other words, you cannot use CALL from a terminal to start a program that uses Rendezvous. Error messages stating that pthread_create failed indicate that you have not set QIBM_MULTI_THREADED, or you have used the CALL command to start a Rendezvous program. 7. When you receive a license ticket file from TIBCO, do these steps: a. Create a new source physical file named TIBRV in one of your libraries. b. Put the license ticket file in a member of that file named TKT. (This prevents accidental removal of the ticket files when you next upgrade Rendezvous.) c. Ensure that the library containing the ticket file is in the library list. Rendezvous searches for TIBRV(TKT) in your library list, and uses the first license file that it finds.
44
| Chapter 5
IBM i
| 45
Chapter 6
Universal Installer
This chapter presents installation and uninstallation using TIBCO Universal Installer.
Topics
Before Installing, page 46 Install TIBCO Rendezvous, page 48 Uninstalling the Software, page 56
46
| Chapter 6
Universal Installer
Before Installing
Destination Directory
If you are upgrading from Rendezvous 7.x (or earlier) or from any version of Rendezvous installed as part of TRA, read this section. The installers for Rendezvous 7.x (and earlier) installed the product into a destination root directory defined by the TIBCO Runtime Environment (TRA) environment. In contrast, the TIBCO Universal Installer installs into a destination root directory defined by previous invocations of the Universal Installer. That is, if you already installed another product using TIBCO Universal Installer, then the destination root directory for that product becomes the destination root for all subsequent products that use the Universal Installer. In particular, installing Rendezvous 8 after an existing TRA leaves two versions of Rendezvous in separate locationsthe old version (installed with TRA) and the new version. Other TIBCO products that depend on TRA use Rendezvous daemons from the new version, but continue to use Rendezvous libraries from the old version.
Installer Account
Microsoft Windows You must have administrator privileges to install TIBCO Rendezvous. If you do not have administrator privileges, the installer exits. You must then log out of the system and log in as a user with the required privileges, or request your system administrator to assign the privileges to your account. If you intend to install the product on a network drive, you must ensure that the account used for installation has permission to access the network drive. UNIX To install TIBCO Rendezvous, you can login either as a regular (non-root) user or as super-user (root). A graphic environment such as CDE or X Windows is required to run the installer in GUI mode.
Before Installing 47
Disk Space
Temporary Disk Space Required by the Installer When a TIBCO Rendezvous package is unpacked, it is extracted into a temporary folder. The installer requires at least 250 MB of free space in the temporary directory. On Microsoft Windows, the temporary directory location is %SystemDrive%:\Documents and Settings\user_name\Local Settings\Temp. If your system does not have sufficient free disk space in the default temporary directory, you can run the installer with a different temporary directory by using the following option when starting the installer. For example:
TIBCOUniversalInstaller -is:tempdir \new_tmp
where \new_tmp has sufficient free disk space. The installer calculates the disk space required in product home location for the selected components. The calculation is done before the actual installation (copying of files to system) begins. The installer will proceed only if sufficient free disk space is available in product home location. However, if disk space is consumed by another process while the installer is copying the files, and if the required disk space is thereby reduced, the installer may fail and will then give a failure message. While performing installation, avoid running other processes that consume disk space in product home location. Disk Space After Installation TIBCO Rendezvous can consume 500 MB of free space under TIBCO_HOME.
48
| Chapter 6
Universal Installer
6. The License Agreement screen appears. After reading through the license text, click I accept the terms of the license agreement and then click Next
50
| Chapter 6
Universal Installer
7. Install all features by clicking Typical or choose the features to install by clicking Custom. After making your choice, click Next.
8. If you selected Custom, in step 7, a screen similar to the following appears. If you did not select Custom, proceed to step 10. Unselect the check box next to the features you do not want to install, and click Next.
52
| Chapter 6
Universal Installer
9. The Installation Environment screen appears. Specify a location for installing Rendezvous.
10. The installer prepares the features for installation. A pre-install summary screen appears. Click Install.
54
| Chapter 6
Universal Installer
Daemon Variant
11. Select the TIBCO Rendezvous daemon variant for this installation. Select either TRDP or PGM (for background information, see PGM and TRDP on page 18 in TIBCO Rendezvous Concepts). Click Next.
12. A post-install report summarizes the installation results. Click Finish to close the installer window.
If you are using the TIBCOUniversalInstaller.silent file (rather than a copy), you need not supply the file name and can use this command line:
TIBCOUniversalInstaller -silent
A line similar to the following is written to the installer log file when installation completes:
... Install, com.tibco.installer.util.TIBCOInstaller, dbg.Debug, Executing Event:::OnEndInstall
56
| Chapter 6
Universal Installer
5. If you selected Custom Uninstall, then in the next screen select the specific products to uninstall. The choices include only TIBCO products that you installed using the universal installer.
58
| Chapter 6
Universal Installer
General Command Line The general form of the command line gives flexibility.
universal_uninstall_executable_filename -V uninstallProductID="product_id" -V uninstallProductVersion="version" -silent
Description When present, uninstall only this product. When absent, uninstall all TIBCO products.
uninstallProductVersion="version"
When present, uninstall only this version. When absent, uninstall all versions.
| 59
Index
A
ALTPRI privilege, VMS 27
M
Microsoft Windows 13
B
byte limit, VMS 29
N
netmbx, VMS 31
C
customer support xx
O
OPER privilege, VMS 27
D
directory structure 3 disk space 47
P
page file quota, VMS 29
R I
root priority, UNIX 6 Install TIBCO Rendezvous 48 installer log file 47
S L
log file 47 setuid root, UNIX 6 support, contacting xx SYSGEN parameters, VMS 29
60
| Index
T
TCP/IP services, VMS 21 technical support xx temporary disk space 47 TIBCO_HOME xvii tmpmbx, VMS 31
U
uninstall 56 UNIX 5
V
VMS 19
W
Windows 13