OSI/MHS Management Programming Manual

Password Server Interfaces
OSI/MHS Management Programming Manual—424824-001
7-40
Using the Master Password Server
This parameter is optional. If the configuration database already exists (because
another MPS process created it), the new MPS process uses the value defined in the
database unless it is in RECONFIGURE or ISOLATE mode. If you specify a
different value for a process in NORMAL or POPULATE mode, the MPS writes a
warning message to the output file and ignores the new parameter.
MPS-CHECK-OSI
has a value of ON or OFF, and a default value of OFF. This parameter controls
whether the MPS process validates OSI addresses when servicing Bind requests
from remote (but not local) user agents.
This parameter is optional. If the configuration database already exists (because
another MPS process created it), the new MPS process uses the value defined in the
database unless it is in RECONFIGURE or ISOLATE mode. If you specify a
different value for a process in NORMAL or POPULATE mode, the MPS writes a
warning message to the output file and ignores the new parameter.
It can be very convenient to set up different template files for different MPS
configurations you anticipate using. For example, if you plan to load the authorization
database from an existing OSI/MHS configuration, you might define a script that defines
and starts a server in POPULATE mode. For normal use, you could make a script that
defines two servers—one in NORMAL mode and one in RECONFIGURE mode—but
that starts only the normal-mode server. Later, if you wanted to change the
configuration dynamically, you could run the reconfigure-mode server explicitly from
PATHCOM or using a TACL command interpreter.
Load the Authorization Database: APPLs Already
Defined to OSI/MHS
Follow this procedure when your OSI/MHS subsystem already has APPLs assigned to
message store (MS) groups. In this case, the MPS process copies over APPL
information from the subsystem to the MPS authorization database.
If your subsystem (or a particular MS group on the subsystem) does not yet have any
APPLs configured, do not follow this procedure. Instead, perform the task titled, “Load
the Authorization Database: APPLs Not Yet Defined to OSI/MHS,” described next.
This procedure presumes that you have already used the installation macro to create the
authorization database and created a script to define and run an MPS process in
POPULATE mode. Follow these steps:
1. Run the MHSMGR process if it is not already running.
2. Use the SCF ALTER GROUP command to specify an MPS process name for each
MS group to be supported by the MPS. Use the SCF attribute MS-BIND-PW-SVR
to specify the MPS process name.
3. Use SCF to stop all the APPLs on the MS groups to be supported by the MPS
processes. Be sure to notify users in advance.
Note. Do not execute the TACL or PATHCOM script until you have followed the steps to add
APPLs to the authorization database, as explained next.