OSI/MHS Management Programming Manual

Password Server Interfaces
OSI/MHS Management Programming Manual—424824-001
7-44
Sizing and Performance Information
•
Run a new MPS process in RECONFIGURE mode, specifying new values for
the startup parameters. The MPS process in RECONFIGURE mode updates the
configuration and then stops. All MPS processes using that configuration
database are notified of the update and begin to operate with the new
parameters.
•
Run an MPS process in ISOLATE mode, specifying new values for the startup
parameters. This option changes the configuration only for the MPS process in
ISOLATE mode. All other MPS processes continue to use the former values.
Even in ISOLATE mode, the MPS process continues to use the master user
information—MPS_MASTER_APPL, MPS_ALLOW_BINDS and
MPS_ALLOW_REG—stored in the configuration database.
•
Changing the Set of APPLs an MPS Process Serves
To change the set of APPLs an MPS process serves, stop the MPS processes, create
a new authorization database, and follow the procedure to load the authorization
database when APPLs are already defined to OSI/MHS. To remove the MPS from
the configuration of MS groups that will no longer use it, perform the next task.
Deconfigure the MPS
Use the following procedure to remove an MPS process from an OSI/MHS subsystem:
1. Stop all the APPLs on any MSs that use the MPS process.
2. Stop the MS groups that use the MPS process.
3. Alter the MS groups to remove the name of the MPS process.
4. Alter all the APPLs on these MS groups to specify new passwords
You must specify new passwords because whenever you remove an MS bind
password server from an OSI/MHS subsystem, NULL passwords are stored in the
OSI/MHS databases for all APPLs that used to use the server. A NULL password
allows any supplied password to match.
5. Delete the master user APPL if it was defined solely for use with the MPS.
6. Restart the APPLs and MS groups, and resume normal operation.
7. Notify users of their new passwords.
Sizing and Performance Information
To authorize requests as efficiently as possible, the MPS process retains in memory
almost all elements of its authorization database. (The APPL O/R name is not be kept in
memory, because it does not play any part in the authorization of requests and it
occupies most of the record length.) For 1000 APPLs the memory requirement for the
authorization database will be approximately 500KB. To support large numbers of
APPLs, you can spread the workload across multiple MPS processes.