Previous | Contents |
To use the features of Reliable Transaction Router, each account must have the following privileges:
In addition, the Rights Identifier RTR$INFO is required.
The RTR System Manager (that is, the account that starts up RTR and
creates facilities) must also have either OPER privilege or
have the Rights Identifier RTR$OPERATOR.
3.5 Files Installed on OpenVMS
This section lists the files added to your system by the installation on OpenVMS.
[vms$common]rtr.dir [sys$startup]rtr$startup.com [sysexe]rtr.exe [sysexe]rtr$remote.com [sysexe]rtr_start_acp.com [syslib]rtr.h [syslib]librtr.exe [sysmgr]rtr$snapshot.com [sysmgr]rtr$shutdown.com [systest]rtr$ivp.com [syshlp]rtr_relnotes.txt [syshlp]rtr_relnotes.ps [syshlp]rtr.hlb [syshlp]rtr_migration_guide.ps [rtr]ACCFAIL.mon [rtr]ACP2APP.mon [rtr]ACTIVE.mon [rtr]APP2ACP.mon [rtr]BROADCAST.mon [rtr]CALLS.mon [rtr]CHANNEL.mon [rtr]CONNECTS.mon [rtr]DDTM.mon [rtr]DTX.mon [rtr]DTXREC.mon [rtr]EVENT.mon [rtr]FACILITY.mon [rtr]FLOW.mon [rtr]FRONTEND.mon [rtr]GROUP.mon [rtr]IPC.mon [rtr]IPCRATE.mon [rtr]JCALLS.mon [rtr]JOURNAL.mon [rtr]LINK.mon [rtr]NETBYTES.mon [rtr]NETSTAT.mon [rtr]PARTIT.mon [rtr]QUEUES.mon [rtr]QUORUM.mon [rtr]RDM.mon [rtr]RECOVERY.mon [rtr]REJECTS.mon [rtr]REJHIST.mon [rtr]RESPONSE.mon [rtr]RFB.mon [rtr]ROLEQUOR.mon [rtr]ROUTERS.mon [rtr]ROUTING.mon [rtr]RSCBE.mon [rtr]RTR.mon [rtr]STALLS.mon [rtr]SYSTEM.mon [rtr]TPS.mon [rtr]TPSLO.mon [rtr]TRAFFIC.mon [rtr]TRANS.mon [rtr]V2CALLS.mon [rtr]XA.mon [sysmsg]oormsg.exe (optional component) [syslib]oorcmp.exe (optional component) [sysexe]ooro7v2.exe (optional component) sys$examples:[rtr]crtr.cxx sys$examples:[rtr]crtr.hxx sys$examples:[rtr]cslb.hxx sys$examples:[rtr]example_cli.cxx sys$examples:[rtr]example_cslib.hxx sys$examples:[rtr]example_srv.cxx sys$examples:[rtr]rtr_ivp_osf.sh sys$examples:[rtr]rtrreq.c sys$examples:[rtr]rtrsrv.c |
This chapter describes a full installation on Windows NT to run RTR as a server. For information on installing RTR for client applications on Windows 95 or Windows 98, see Section 1.2.
The installation of the RTR base product requires about five megabytes of disk space. The installation procedure takes about two minutes to complete.
The release notes and README files provide information for RTR that could not be included in the printed documentation. The release notes are in the following files on the :CD-ROM:
or
|
RTR STOP RTR RTR DISCONNECT SERVER/DAEMON |
DELETE /S/Q C:\RTR |
C:\Program Files\Compaq\Reliable Transaction Router |
RTR as a Service runs only on Windows NT; the InstallShield does not register the service but RTR provides batch procedures to do so in the target directory. |
If you install RTR on an NTFS drive, you will need to give RTR users access to the RTR directories. Use Windows NT Explorer and select the RTR root directory. Pull down the Security menu and choose File permissions. Give the RTR root directory and all its subdirectories "Full Control" access for all RTR users. You may then restrict access on individual files to read only. (All RTR users require write access to the RTR journal directory.)
The following examples are provided in the [EXAMPLES] directory:
The program rtrreq.c is a console mode client; the program rtrsrv.c is a console mode server. The program rtrw32rq.c is a sample GUI client that can run with rtrsrv.c. The example applications can be built by using the examples.mak file:
NMAKE/f examples.mak |
The Windows registry will be modified slightly as a result of a RTR installation. |
4.4 Files Installed on Microsoft Windows NT
<DIR> . <DIR> .. Accfail.mon Acp2app.mon Active.mon App2acp.mon Broadcast.mon Calls.mon Channel.mon Connects.mon Ddtm.mon Dtx.mon Dtxrec.mon <DIR> examples Event.mon Facility.mon Flow.mon Frontend.mon Group.mon installservice.bat Ipc.mon Ipcrate.mon Jcalls.mon Journal.mon Link.mon Msvcrt.dll Oorcmp.dll Oorodb32.dll Ooroml32.dll Oorrot13.dll Oorstp32.dll Netbytes.mon Netstat.mon Partit.mon Queues.mon Quorum.mon Rdm.mon readment.txt Recovery.mon Rejects.mon Rejhist.mon Response.mon Rfb.mon Rolequor.mon Routers.mon Routing.mon Rscbe.mon rtr.exe Rtr.h Rtr.hlb Rtr.hlp rtr.ico Rtr.mon rtrdll.dll rtrdll.lib RTRSvc.exe shutdown.bat Stalls.mon System.mon Tps.mon Tpslo.mon Traffic.mon Trans.mon Uninst.isu uninstallservice.bat V2calls.mon xa.mon \examples doswin16.mak examples.mak rtrreq.c rtrsrv.c rtrw32rq.c rtrw32rq.def rtrw32rq.dlg rtrw32rq.h rtrw32rq.rc |
This chapter provides descriptions of all steps in doing a full installation including:
RTR software is distributed on :CD-ROM as part of Compaq's Layered Products Consolidated Distribution. Use the Bill of Materials (BOM) to check the contents of your RTR software distribution kit.
In addition to this guide, the software distribution kit includes the following:
If your software distribution kit is damaged or incomplete, contact
your Compaq representative.
5.1.2 Reading the Online Release Notes
RTR provides online release notes. Compaq strongly recommends that you read the release notes before using the product. The release notes may contain information about changes to the application.
The release notes for RTR are in the following file on the :CD-ROM:
rtr3xx_relnotes.txt |
Where "xx" represents a revision level.
You can use the following command to read the release notes.
more rtr3xx_relnotes.txt |
Where "xx" represents a revision level.
5.1.3 Registering Your Software License
RTR includes support for the License Management Facility (LMF). You must register your License Product Authorization Key (License PAK) in the License Database (LDB) in order to use RTR on a newly licensed node. The License PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order.
If you are installing RTR as an update on a node already licensed for this software, you have already completed the License PAK registration requirements.
If you are installing prerequisite or optional software along with RTR, review the PAK status and install the PAKs for any prerequisite or optional software before you install RTR.
To register a license under the Compaq Tru64 UNIX operating system, first log in as superuser.
At the superuser prompt, edit an empty PAK template with the lmf register command as follows, and include all the information on your License PAK:
# lmf register |
After you register your license, use the following lmf reset command to copy the license details from the License Database (LDB) to the kernel cache:
# lmf reset |
For complete information on using the License Management Facility, see
the Guide to Software License Management and the lmf(8) reference page.
5.1.4 Checking Installation Requirements
This section discusses requirements for installing RTR.
Installing RTR, including running the Installation
Verification Procedure (IVP), takes approximately 10 to 15 minutes,
depending on your type of media and system configuration.
5.1.4.1 Checking Login Privileges
You must have superuser privileges to install the RTR
software and to register the license PAK.
5.1.4.2 Checking Hardware Requirements
To install RTR, you need the following hardware:
See the RTR Software Product Description (SPD) for additional
hardware requirements.
5.1.4.3 Checking Software Requirements
RTR requires the Compaq Tru64 UNIX operating system shown on the cover of this manual.
RTR also requires that the following Compaq Tru64 UNIX software subset be loaded on the system where you install RTR:
The following Compaq Tru64 UNIX software subsets are optional on the system where you install RTR:
To check whether these subsets are loaded, follow these steps:
# setld -i | egrep 'OSFBASE|DNA' |
If you do not log in as superuser (login name root ), you must enter the full path of the command. For example:
% /usr/sbin/setld -i | grep OSFBASE |
Check the displayed rows for the name of the relevant subset and any
related patches. The word "installed" appears in a row after
the subset identifier when a subset is loaded. If the word
"installed" does not appear (the second column in a row is
blank), the subset or patch is not loaded. In this case, you must load
the missing Compaq Tru64 UNIX software before installing RTR.
(For information on how to load the operating system software, see the
Guide to Installing Compaq Tru64 UNIX.)
5.1.4.4 Determining Which Subsets to Load
RTR has only one subset:
Table 5-1 lists the disk space requirements for loading the RTR software subset. These requirements apply to the disks where you load the RTR subset. The requirements are listed by directory for convenience if you are doing installations on systems where these directories are mount points for different disk partitions.
Subset Title | Subset Name | /usr/opt/ | /rtr |
---|---|---|---|
RTR | rtrbase320 | 57020 | 1050 |
Total: | 58070 |
Using these disk space requirements, calculate the total values for the subsets you will load in each directory. You will also require disk space for the RTR journal, which defaults to /rtrjnl.
Compare the space required for the subset with the free space currently
on the disks where RTR files will reside.
5.1.4.5.1 Checking Current Disk Space
To check the current amount of free space for a directory path, log in to the system where you will install RTR. You can check which directories are mounted and where they are by viewing the /etc/fstab file. For example:
# more /etc/fstab /dev/rd0a:/:rw:1:1:ufs:: /dev/rd0g:/usr:rw:1:2:ufs:: /usr/staff/r1/leslie@bigsys:/usr/staff/r1/leslie:rw:0:0:nfs:bg: /usr/man@bigsys:/usr/man:ro:0:0:nfs:bg: |
The display indicates that /usr (mounted to /dev/rd0g ) is the only mount point that affects where RTR files will reside; the system has only one local disk drive, and the /usr/lib and file system resides in the g partition of the disk on that drive.
To check the total space and the free space for the directories where RTR will reside, enter the df command. Given the previous display of the /etc/fstab file, which shows that only /usr is a mount point, you need to check free space only in the /usr file system. For example:
# df /usr Filesystem Total kbytes kbytes % node kbytes used free used Mounted on /dev/rd0g 122598 54447 55892 49% /usr |
This display shows that there are 55,892 Kbytes free. This free space must accommodate the subset requirements listed in Table 5-1, RTR Subset Size (Kilobytes Required).
On systems where /usr/lib and /usr/man are mounted to different devices from /usr , enter the following command:
# df /usr/lib /usr/man |
In this case, you compare space required for RTR files in
/usr/lib
to the free space displayed in the first line of the
df
output list, and compare the space required for RTR files in
/usr/man
to the free space displayed in the second line of that list.
5.1.4.5.2 Increasing Disk Space by Using Alternative Disks
The RTR installation procedure creates the following directory and loads files into subordinate directories:
/usr/opt/RTR320 |
If the /usr/opt/rtr320 directory node in the previous path does not exist, the installation procedure creates it.
If the rtr320 node does exist, the installation procedure uses it.
If you find that there is insufficient disk space for the RTR subsets and you know that you have additional space on alternative disks or disk partitions for your system, perform the following steps before installing RTR:
Someone from your site must perform at least one RTR installation from the distribution medium. Your site system manager can then decide whether or not to make a RTR distribution kit available online so that subsequent installations of RTR can use the Remote Installation Service (RIS). For information on extracting RTR subsets to a RIS distribution area, see the Guide to Sharing Software on a Local Area Network.
If you expect to use RTR subsets from the RIS area of a remote system for installation on your local system, first check with your site system manager to ensure that:
If RTR subsets are available to you on a RIS server system, you must know the name of that system.
For more information on installing RTR from a RIS distribution area, see Section 5.2.1.2.
Previous | Next | Contents |