| Previous | Contents | Index |
Your Reliable Transaction Router for Windows kit is supplied on CD-ROM. After installation, the Readme file is located in the directory where you installed RTR; you are advised to read the Readme file before using RTR.
If you have changed any RTR monitor (*.mon) files, you must rename them or they will be over-written during installation. To avoid this, always work from renamed copies of RTR monitor files when making local modifications. |
The installation of the RTR base product requires about 22 MB
(megabytes) of disk space. The installation procedure takes about two
minutes to complete.
1.3.2 Installation Procedure
Your Reliable Transaction Router for Sun Solaris kit is supplied on CD-ROM. After installation, the Release Notes are located in the directory /opt/rtr/RTR420/hlp; you are advised to read the Release Notes before using RTR.
If you have changed any RTR monitor (*.mon) files, you must rename them or they will be over-written during installation. To avoid this, always work from renamed copies of RTR monitor files when making local modifications. |
The installation requires about 15.5 MB (megabytes) on the partition on /opt , the package base directory, about 8 MB on /rtr and about 2 MB for the RTR journal. The installation procedure takes about two minutes to complete.
Note that the Installation Verification Procedure (IVP) requires a
working C language compiler to run.
1.4.2 Installation Procedure
There are both an rtr and an rtr_r ; ( rtr_r is installed only on SunOS 5.6/Solaris 2.6 systems). A soft link is established to the appropriate one from /usr/bin/rtr . RTR provides both librtr_r.so and librtr.so for SunOS 5.6 in case you need to link your application with the threaded version. On SunOS 5.6, RTR uses librtr_r.so to enable asynchronous I/O (aio) support. |
# pkginfo -l rtr |
# sh # NONABI_SCRIPTS=TRUE |
# cd /cdrom/rtr_kit # pkgadd -d . |
If the RTR executable is modified after installation to no longer be suid root or the mode of the /rtr directory is changed, an application process (for example a client) can encounter a fatal error (Unable to locate a socket) when the client process finds it cannot create an rtr_ipc_sock_* file for the process ID (pid) in the /rtr directory. To avoid this, ensure that application processes run with user and group IDs that have access permission to create and remove files in this directory. |
Section 1.4.3 shows an example of an RTR intallation for the Sun Solaris.
The Installation Verification Procedure (IVP) requires a working C language compiler to run.
Do not run the IVP program on a production system as it may alter the RTR journal or interrupt processing of transactions. You will be prompted to abort the IVP before it can do any damage. Consider your situation carefully before running the IVP. |
You may run the IVP separately from the installation procedure. If you are not using the C shell, start it by typing /usr/bin/csh and run the IVP by typing the following:-
# setenv BASEDIR /opt |
and then executing the file
opt/rtr/RTRxxx/examples/IVP/rtr_ivp_osf.sh
where xxx = 420 for RTR V4.2.
Section 1.4.4 shows an example of IVP output for RTR on the Sun Solaris.
1.4.3 Sample Sun Solaris Installation
# pkgadd -d .
The following packages are available:
1 rtr Reliable Transaction Router
(sun4u) 420
Select package(s) you wish to process (or all to process
all packages). (default: all) [?,??,q]:
Processing package instance <rtr> from
</CDROM/rtr420/rtrkit>
Reliable Transaction Router
(sun4u) 420
Hewlett-Packard Development Company, L.P.
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <rtr> [y,n,?] y
Installing Reliable Transaction Router as <rtr>
## Executing preinstall script.
Copyright 1994, 2003 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP and/or its
subsidiaries required for possession, use or copying. Consistent
with FAR 12.211 and 12.212, Commercial Computer Software, Computer
Software Documentation, and Technical Data for Commercial Items
are licensed to the U.S. Government under vendor's standard
commercial license.
This kit will only run on Sun Solaris 2.6 and higher.
Installation should complete in approximately 1 minute.
## Installing part 1 of 1.
[All installed files are listed in the output. See Chapter 6,
"Full Installation on Sun Solaris" for the list.]
.
.
.
[ verifying class <none> ]
## Executing postinstall script.
Copyright 1994, 2003 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP and/or
its
subsidiaries required for possession, use or copying.
Consistent
with FAR 12.211 and 12.212, Commercial Computer Software,
Computer
Software Documentation, and Technical Data for Commercial Items
are licensed to the U.S. Government under vendor's standard
commercial license.
directory /rtr -> /var/opt/rtr created
Starting Reliable Transaction Router V4.2 for SunOS
Installation Verification Procedure
WARNING: This is not a first time install.
WARNING: Please ensure that you have terminated *all* existing
WARNING: rtr processes and rtr applications before continuing.
See man fuser or lsof to identify processes using
/usr/*lib/librtr*.so
Rtr will find and reuse any existing journal files in the
top level rtrjnl directory on each suitable filesystem, and will
reuse any existing shared memory segment associated with
/rtr/RTRENVPS
Normally this is intended and should not cause any problems.
WARNING: Any existing journal will be used and modified, otherwise
WARNING: a new journal will be created on the default filesystem.
WARNING: Facilities RTR_IVP_FACILITY and RTR$DEFAULT_FACILITY
will be created.
WARNING: Result may be affected by size and contents of any
existing journal.
WARNING: The sample client and server do not necessarily complete
if they
WARNING: encounter previously journalled transactions for these
facilities.
NOTE: The following question is ignored in a non-interactive
install
NOTE: unless NONABI_SCRIPTS=TRUE, see man pkgadd for details...
You may run the IVP separately from the installation
procedure by executing the file:
/opt/rtr/RTRxxx/examples/IVP/rtr_ivp_osf.sh
Would you like to abort the IVP? (y/n) [y] IVP aborted
Installation of <rtr> was successful.
The following packages are available:
1 rtr Reliable Transaction Router
(sun4u) 420
Select package(s) you wish to process (or all to process
all packages). (default:all) q
#
|
.
.
.
Would you like to abort the IVP? (y/n) n
IVP continuing ...
keep any existing log file settings (RTR_DBG not set)
starting RTR . . .
creating a journal, if not already created . . .
creating test facility . . .
stopping RTR.
Reliable Transaction Router V4.2 for SunOS
Installation Verification Procedure successful
The following packages are available:
1 rtr Reliable Transaction Router
(sun4u) 420
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: q
#
|
To upgrade RTR, use the following process:
Take note of the following restrictions if upgrading an RTR environment from RTR V3.2 to Version 4.2.
See Chapter 3 for how to retain the V2 help file when migrating to a later version of RTR. Refer to the Reliable Transaction Router Migration Guide for information on performing this migration. |
The RTR recovery protocol consists of messages sent from one backend, via a router, to the target backend. If either of the RTR backends is upgraded to RTR Version 4.2, then the router that will be used for recovery must also be running RTR Version 4.2. This generally means that any RTR router nodes should be upgraded to RTR Version 4.2 before any RTR backend nodes. There is no restriction in the order that RTR backends should be upgraded to Version 4.2.
The order in which RTR nodes should be upgraded for a rolling upgrade from V3.2 to Version 4.2 is as follows:
For more complex configurations, where a node may have combinations of facilities with different backend/router groupings, use the command SET NODE/RECOVERY=V32 to set the recovery protocol to the V3.2 algorithm.
Once RTR has been upgraded on all nodes, the recovery protocol can be reset to its default value (V4.0), and RTR restarted at a convenient time on each node. This need not be a simultaneous restart on all nodes. RTR can be restarted on each node one by one after resetting the default recovery protocol, so that continuous application availability is maintained.
This chapter describes how to install Reliable Transaction Router on OpenVMS Alpha systems. It includes steps for:
Before you start the installation, complete the preparation tasks outlined in this section.
If you have changed any RTR monitor (*.mon) files, you must rename them or they will be overwritten during installation. To avoid this, always work from renamed copies of RTR monitor files when making local modifications. |
To retain RTR V2 help when installing later versions of RTR, before uninstalling RTR make a copy of the RTR V2 help file that is on SYS$COMMON:[SYSHLP]RTRHLP.HLB . Rename it, for example, RTRHLPV2.HLB. After completing installation of the later version of RTR with its current help file, copy the old RTRHLPV2.HLB file back. You can then access the old file from the DCL command line with the DCL command HELP @RTRHLPV2. |
Reliable Transaction Router is distributed on CD-ROM. Use the Bill of Materials (BOM)
received with your kit to verify the contents of your software
distribution kit.
3.1.2 Check Required Hardware
To install RTR, you need the following minimum hardware:
See the Reliable Transaction Router Software Product Description for additional hardware requirements.
3.1.3 Check Required Software
Table 3-1 provides information on the software that must be installed on your system before installing Reliable Transaction Router. The table also includes information about optional software that you can use with Reliable Transaction Router. See the Reliable Transaction Router Software Product Description (SPD) for the list of prerequisite and optional software and their required version numbers.
| Prerequisite Products | Purpose |
|---|---|
| OpenVMS Alpha Version 6.2,7.2-2,7.3 | System Software |
|
One of the following must be present on your system to use RTR: |
|
| Networking Products | Purpose |
| TCP/IP Services for OpenVMS (Version 4.2 or higher, depending on OpenVMS version) | Network Transport |
| DECnet (Version 6.2 or higher, depending on OpenVMS version) or DECnet-Plus (Version 6.3 ECO5 or higher, depending on OpenVMS version) | Network Transport |
The Installation Verification Procedure (IVP) will complete successfully only if at least one of the supported network protocols (DECnet or TCP/IP) is installed.
There is no requirement that you must register a software license for
RTR for OpenVMS.
3.1.4 Check Required Disk Space
Reliable Transaction Router's requirements for free disk storage space are different during installation and after installation. Table 3-2 summarizes the storage requirements.
| Kit | Blocks During Installation | Blocks After Installation |
|---|---|---|
| Reliable Transaction Router for OpenVMS Alpha | 53000 | 36000 |
To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt:
$ SHOW DEVICE SYS$SYSDEVICE |
Installing Reliable Transaction Router for OpenVMS may mean that you have to increase the values for some system parameters. For more details, see the Reliable Transaction Router System Manager's Manual.
Size global pages and global sections appropriately. (Refer to Reliable Transaction Router System Manager's Manual, Section 2.10, RTR Shared Memory Sizing, for information on sizing.) Table 3-3 lists the minimum free amount of global pages and global sections required for the installation.
| System Parameter | Required Amount |
|---|---|
| GBLPAGES | 4000 |
| GBLSECTIONS | 4 |
RTR has basic memory requirements. For information on how much virtual
memory to allocate, refer to Reliable Transaction Router System Manager's Manual, Section 2.11, RTR ACP
Virtual Memory Sizing.
3.2 Install RTR
If RTR is already installed on your system, see Section B.1, Uninstalling on OpenVMS, for information on uninstalling RTR and removing related processes.
Log on to the System Manager's account to do the installation.
The Reliable Transaction Router installation procedure uses the POLYCENTER Software Installation Utility (PCSI). For details on using PCSI, refer to the OpenVMS System Manager's Manual, Section "Installing with the POLYCENTER Software Installation Utility."
The logical name PCSI$SOURCE is used to define the location of the software kits you want to install. For example, if the Reliable Transaction Router software is located in DISK1:[KITS], enter the following at the DCL prompt (or include the line in the system manager's login command file):
$ DEFINE PCSI$SOURCE DISK1:[KITS] |
The installation prompts you with questions. Enter your response to each question and press the [Return] key. Defaults are shown in square brackets, for example, [YES].
To start the installation, enter the command:
$ PRODUCT INSTALL RTR |
A display similar to the following appears:
The following product has been selected:
DEC AXPVMS RTR V4.2-xxx (1) Layered Product
Do you want to continue? [YES] yes
Configuration phase starting ...
You will be asked to choose options, if any, for each
selected product and for
any products that may be installed to satisfy software dependency
requirements.
DEC AXPVMS RTR V4.2-xxx: Reliable Transaction Router for OpenVMS
Copyright 1994, 2003 Hewlett-Packard Development Company, L.P.
Do you want the defaults for all options? [YES] no
Have all RTR processes on the system been stopped? [YES] yes (2)
Run installation verification procedure [NO] yes (3)
DECnet users:Have you read the Release Note regarding
minimum version? [YES] yes
Do you want the V2 programming kit installed? [NO] yes (4)
Do you want to review the options? [NO] yes
DEC AXPVMS RTR V4.2-xxx: Reliable Transaction Router for OpenVMS
Have all RTR processes on the system been stopped?: YES
Run installation verification procedure: YES
DECnet users: Have you read the Release Note regarding
minimum version?: YES
Do you want the V2 programming kit Installed ?: YES
Are you satisfied with these options? [yes]
Execution phase starting ...
The following product will be installed to destination:
DEC AXPVMS RTR V4.2-xxx <logical for SYS$COMMON> (5)
Portion done: 0%
...10%
...20%
...30%
...40%
...50%
...60%
...70%
...80%
...90%
...100%
The following product has been installed:
DEC AXPVMS RTR V4.2-xxx Layered Product
%PCSI-I-IVPEXECUTE, executing test procedure for
DEC AXPVMS RTR V4.2-xxx ...(6)
%PCSI-I-IVPSUCCESS, test procedure completed successfully
DEC AXPVMS RTR V4.2-xxx: Reliable Transaction Router for OpenVMS
Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM: (7)
@sys$startup:rtr$startup.com
Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:
@sys$manager:rtr$shutdown
See the Release Notes and documentation for use of the
optional
rtr$startup P1 parameter. (8)
$
|
| Previous | Next | Contents | Index |