OSI/MHS Administrative Utility (AU) Manual

OSI/MHS Administrative Utility (AU) Manual—424826-001
2-1
2
Installing and Configuring the
Administrative Utility
To install the AU product, a master user creates an AU user-permissions database and
configures the AU Pathway server classes for the OSI/MHS subsystem to be
administered (See Step-by-Step Installation on page 2-2 for details about establishing a
master user). If you intend to use the AU with more than one OSI/MHS subsystem, the
master user must create an AU user-permissions database and configure the AU
Pathway server classes for each OSI/MHS subsystem to be administered.
The AU user permissions (AUUSERS) database determines the extent to which a user
(identified at logon to the AU) may access and manipulate PDUs in the OSI/MHS
subsystem.
The master user must add the two AU server classes (the AU-DISTRIBUTOR class and
the AU-SERVER class) to a Pathway environment for each OSI/MHS subsystem that
the master user administrates.
All files referred to in this section reside on the AU product subvolume (PSV), which is
created when the AU product is downloaded.
Planning Configuration of the AU
To determine how to do the AU installation and configuration procedures in your
location, consider the following questions:
•
How many OSI/MHS subsystems are there on your system?
•
What is the name of the MHSMGR for each of your OSI/MHS subsystems?
•
Where is the OSI/MHS database located for each OSI/MHS subsystem?
•
How many users will need access to each OSI/MHS subsystem?
•
What type of permissions will each user need?
•
What will the name of each AU user-permissions database file be, and where will
each file be located?
•
Which TCP/IP port will the AU-DISTRIBUTOR class listen to for queries on each
OSI/MHS subsystem?
•
What Guardian TCP/IP process will the AU-DISTRIBUTOR class and the
AU-SERVER class communicate over, and what is the IP address of the process?
Note. Maintain all files you download in a single subvolume. If you want to maintain multiple
AU Pathways, set up multiple subvolumes for each AU Pathway and move copies of all files in
the AU PSV to each of the new subvolumes.