TRANSFER Installation and Management Guide

Establishing the TRANSFER Environment
The TRANSFER Environment
2–2 068837, Update 1 to 013198 Tandem Computers Incorporated
Queue Manager, an optional queueing facility that lets requesters add an
entry in a queue and retrieve an entry from a queue for processing
Queue Manager is a separate Tandem product that can be used independently
of TRANSFER. It is automatically installed when you configure the
TRANSFER X400 gateway.
Other applications developed by and available from third-party software vendors,
such as:
Courier, an application that provides electronic-forms processing, including
automatic routing and manager approval
Other electronic mail applications for various terminals
Gateways that allow users to exchange packages with users on other host
systems, including those of IBM, DEC, Hewlett-Packard, and Data General
User applications that customers develop and supply to run on a TRANSFER
system
Establishing the
TRANSFER Environment
To establish the environment in which TRANSFER can run, you need to do the
following:
1. Configure TMF.
2. Select the components you want to include in the TRANSFER system at your site.
3. Follow the instructions for preparing to install TRANSFER (Section 4), defining
and initializing a TRANSFER system (Section 5), and using the installation
procedures to configure, start, and stop the system (Section 6).
4. Customize and tune the system (Section 7).
This section gives a brief description of the data files, of the configuration of the
TRANSFER system components, and of the PATHWAY objects that compose a
TRANSFER system. It also gives guidelines for satisfying the requirements of
TRANSFER.
Developing TRANSFER
Applications
During the development of your TRANSFER applications, you can run multiple
TRANSFER systems on your local node. Running a separate TRANSFER system for
development allows you to isolate the applications under development from programs
and data in your production system.
To run a second TRANSFER system, you install TRANSFER using different database
files and process names. The database files for the second TRANSFER system must
either be placed on different subvolumes or be given names different from the
database files used by your production system. All process names defined for both
TRANSFER systems must be unique. Multiple TRANSFER systems at one node
cannot communicate with each other.