OSI/MHS Management Programming Manual

Password Server Interfaces
OSI/MHS Management Programming Manual—424824-001
7-42
Using the Master Password Server
if a Register-MS request changes a user’s password, the MPS process updates the
password for the corresponding APPL in its authorization database.
Follow these steps to add new APPLs:
1. Run the MHSMGR process if it is not already running.
2. Use the SCF ADD or 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 your TACL or PATHCOM script to start an MPS process in NORMAL mode,
specifying the authorization database to be used.
4. Use SCF ADD APPL commands to add the APPLs to the MSs. Check the EMS
event log and the SCF and MPS output files to verify that no errors occurred while
APPLs were being added. Correct any problems before continuing.
5. Add the master user APPL object to one of the MSs for each MPS process that will
support a master user.
6. Use SCF to start the OSI/MHS subsystem objects. You might choose to keep the
master user APPL in the STOPPED state to prevent unauthorized logon and
Register-MS attempts.
The MPS is now in operation.
Run and Monitor the MPS
If you populated the authorization database from an active OSI/MHS subsystem (with
APPLs defined), use the following procedure to start and monitor the MPS:
1. Use SCF to start the OSI/MHS subsystem objects, including all APPLs that were
stopped. You might choose to keep the master user APPL in the STOPPED state to
prevent unauthorized logon and Register-MS attempts.
2. Use your TACL or PATHCOM script to start an MPS process in NORMAL mode.
Examine the output file to verify that the MPS process has started and has the
database files open, and to check for errors and warnings.
The MPS is now in operation.
Make Changes to an Established MPS Configuration
Different types of changes to the MPS configuration can be accomplished in different
ways. The following considerations apply to various types of configuration changes:
•
Any change affecting the contents of the configuration database results in an
information message on the output file of the MPS. It also changes the
configuration of all MPS processes that use the database.
•
Running an MPS process in ISOLATE mode changes the configuration of that
process only.