TIBCO Rendezvous Performance Insights
TIBCO Rendezvous Performance Insights
Installation
Software Release 8.4
February 2012
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 THE LICENSE FILE) 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.
TIBCO, The Power of Now, TIB, Information Bus, 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 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 © 1997–2012 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
| iii
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Manual Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
TIBCO Rendezvous Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
How to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
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
Select the Installation Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Run the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Review the Administrator’s Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 4 VMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Log In as SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Check TCP/IP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
VMS Installation Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
ZIP Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
File Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Mount the Distribution Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Check Storage Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Install the Rendezvous Product Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Verify Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Daemon Privilege and Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
OPER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
ALTPRI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Starting the Rendezvous Daemon at Boot Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Parameters for rvd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Byte Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Total Non-Paged Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Page File Quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Channel Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Review the Administrator’s Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
C++ Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Rebuilding the C++ Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Additional Information for VMS Programmers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Compile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Chapter 5 IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
IBM i Installation Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Post-Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Check the AAREADME File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Review the Administrator’s Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Figures
Tables
Preface
Topics
Manual Organization
This book includes one chapter for each group of related operating system
platforms.
Related Documentation
z/OS Only
z/OS Installation
Installation Concepts and Configuration
COBOL
Administration C Reference
Reference
C++ Reference
Configuration
COM Reference
Tools
Java Reference
RVDM JMX
MBean API
.NET Reference
Reference Pages
Typographical Conventions
Convention Use
TIBCO_HOME Many TIBCO products must be installed within the same home directory. This
directory is referenced in documentation as TIBCO_HOME. The value of
ENV_HOME
TIBCO_HOME depends on the operating system. For example, on Windows
TIBRV_HOME systems, the default value is C:\tibco.
Other TIBCO products are installed into an installation environment. Incompatible
products and multiple instances of the same product are installed into different
installation environments. An environment home directory is referenced in
documentation as ENV_HOME. The default value of ENV_HOME depends on the
operating system. For example, on Windows systems the default value is
C:\tibco.
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.
Convention Use
italic font Italic font is used in the following ways:
• To indicate a document title. For example: See TIBCO FTL Concepts.
• To introduce new terms For example: A portal page may contain several
portlets. Portlets are mini-applications that run in a portal.
• To indicate a variable in a command or code syntax that you must replace.
For example: MyCommand PathName
Key Key name separated by a plus sign indicate keys pressed simultaneously. For
combinations 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.
Convention Use
[ ] An optional item in a command or code syntax.
For example:
MyCommand [optional_parameter] required_parameter
| A logical OR that separates multiple items of which only one may be chosen.
For example, you can select only one of the following parameters:
MyCommand para1 | param2 | param3
Convention 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}
Chapter 1 Introduction
This manual contains step-by step instructions for installing TIBCO Rendezvous®
software, release 8.4.0.
Topics
• Read the TIBCO Software Inc. License Agreement included with the product.
• Read the appropriate chapters for your platforms.
• Review the section Do This First—Administrator’s Checklist on page 1 in
TIBCO Rendezvous Administration.
Directory Structure
When you install Rendezvous software, the installation directory contains these
subdirectories:
Subdirectory Status
bin Required to develop or run Rendezvous programs.
Contents: executable files, shared libraries (DLL files).
Platform See
UNIX Chapter 2 on page 5
Chapter 2 UNIX
Topics
Please consider these items before you install Rendezvous software on one or
more UNIX platforms.
Download the appropriate installation package for your platforms and variant, or
locate it on the distribution DVD.
Installer package names concatenate three parts:
• Prefix TIB_rv_8.4.0_
• Core string denoting the operating system and hardware for which the
package is appropriate; see Table 5
(For the latest changes, see the README file.)
• Suffix indicating the archive type (for example .[Link])
Installer Package
OS Hardware Suffix Notes
General Information
The following UNIX installer packages include both 32-bit and 64-bit components, except as noted
below.
Installer Package
OS Hardware Suffix Notes
Proceed to Chapter 6, Universal Installer, on page 43, and follow the installation
instructions there. When installation is complete, see Do This First—
Administrator’s Checklist on page 1 in TIBCO Rendezvous Administration.
See
Do This First—Administrator’s Checklist on page 1 in TIBCO Rendezvous
Administration.
The Rendezvous installation procedures for all Windows platforms are identical.
Images in this chapter might not exactly match the images on your screen.
Topics
Hardware
O/S Platform Platform Installer Package Notes
Windows Registry
See
Register Windows Services on page 8 in TIBCO Rendezvous Administration
Windows Services on page 415 in TIBCO Rendezvous Administration.
See
Do This First—Administrator’s Checklist on page 1 in TIBCO Rendezvous
Administration.
Chapter 4 VMS
Topics
Log In as SYSTEM
Rendezvous software will operate properly only if you have installed and started
HP TCP/IP Services, or a fully-compliant third-party TCP/IP product. (The
appropriate release number of that software may vary; see Table 7.)
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.
The distribution DVD contains the Rendezvous software for VMS platforms, as
shown in Table 8. These files are also available for download from the TIBCO web
site.
Hardware
Platform Installer Package Notes
Platform
OpenVMS Itanium HP TIB_rv_8.4.0_vms82_ia64.zip Does not support
v.8.2 or later Integrity/Itanium Java or RVDM.
This package
provides only 32-bit
API and daemons.
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:
[Link]
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*.%
Total 9000
The installation procedure requires your input. The most important items you
supply are the target location for the Rendezvous files, and the environment to
install (development or runtime environment).
The installation procedure takes less than 10 minutes.
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]
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-084 dka100:[[Link]-8-4-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-4-08-4-0 dka100:[[Link]-8-4-0]
Verify Installation
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 system’s
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
priority—preempting 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.
You can start a permanent daemon at boot time, by adding a line to the start-up
file SYS$MANAGER:SYSTARTUP_VMS.COM:
$! This line is already present in the start-up file.
$ @SYS$STARTUP:TIBRV_STARTUP.COM
$! Add this line immediately after it.
$ @TIBRV:[com]RVD_PROC_START
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 account’s 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.
Boot Time When starting the Rendezvous daemon at boot time, the SYSTEM account’s
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.
If rvd fails during accept(), reporting invalid I/O channels, raise this resource
limit using the AUTOGEN tool.
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 user’s [Link] file.
C++ Library
This procedure compiles the source modules using the system default C++
compiler, creates the object library, and copies it to the TIBRV:[LIB] directory.
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",[])
Link
Rendezvous API libraries are multi-threaded, so VMS scheduler upcalls can yield
significant performance improvements:
$ LINK/THREADS_ENABLE=UPCALLS
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).
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.
Chapter 5 IBM i
Topics
• Requirements, page 36
• IBM i Installation Package, page 37
• Post-Installation Instructions, page 39
• Check the AAREADME File, page 41
• Review the Administrator’s Checklist, page 42
Requirements
Rendezvous software requires IBM i with TCP/IP installed. For details, see the
IBM document TCP/IP Fastpath Setup.
c. Copy the save file ([Link]) 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 user’s library list.
b. Use this command to uninstall:
DLTLICPGM LICPGM(2TIBRV2) RLS(*ALL)
libname is the library where you created the save file, in step 3b.
6. To use Java, or to run or develop in the qsh environment, do this step after
RSTLICPGM completes:
b. Restore the file containing the Java files and the IFS file structure.
RST DEV('/[Link]/[Link]/[Link]')
OBJ(('/usr/tibco/tibrv/*'))
More...
F3=Exit F4=Prompt F5=Refresh F10=Additional parameters F12=Cancel
F13=How to use this display F24=More keys
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.
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 /* start it */
/* For Java with qsh, set these vars */
ADDENVVAR ENVVAR(QIBM_MULTI_THREADED) VALUE(Y)
ADDENVVAR ENVVAR(CLASSPATH) +
VALUE(’/usr/tibco/tibrv/[Link]’)
Whether you set the variables manually or automatically, their values persists
until logout.
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.
Topics
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 locations—the 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.
Disk Space
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
8. If you selected Customize Installation, in step 7, you may unselect check boxes
corresponding to features you do not want to install. Click Next to continue.
(If you did not select Custom, proceed to step 10.)
10. The installer prepares the features for installation. A pre-install summary
screen appears. Click Install.
The installer copies files to the TIBCO_HOME directory.
12. A post-install report summarizes the installation results. Click Finish to close
the installer window.
A line similar to the following is written to the installer log file when
installation completes:
... Install, [Link],
[Link], Executing Event:::OnEndInstall
Index
A M
ALTPRI privilege, VMS 25 Microsoft Windows 11
B N
byte limit, VMS 27 netmbx, VMS 29
C O
customer support xx OPER privilege, VMS 25
D P
directory structure 3 page file quota, VMS 27
disk space 45
R
I
root priority, UNIX 6
Install TIBCO Rendezvous 46
installer log file 45
T
TCP/IP services, VMS 19
technical support xx
temporary disk space 45
TIBCO_HOME xvii
tmpmbx, VMS 29
U
uninstalling the software 53
UNIX 5
V
VMS 17
W
Windows 11