Multi-LPAR environment installation considerations
Using Security Policy Manager across a multi-LPAR environments
In a multi-LPAR environment, you can log on to any Security Policy Manager that runs the HTTPServer. Each instance stores its own data so when you start a query from the browser, a transaction passes around all the instances and the results are collated and sent back.
Because a RACF or Top Secret database can be shared between LPARS, we do not need to analyze security definitions on every system in the sysplex. Set the RACFAnalysis parameter on only one system that shares the security database.
Ensure that all instances running in the same sysplex use the same RSSID value. For more information about the settings, see Reviewing-the-startup-JCL-procedures.
Migrating Security Policy Manager to other systems
You do not have to do a full installation of BMC AMI Security Policy Manager on each system where it is required.
BMC recommends that you perform one full SMP/E installation on one system, and migrate the runtime data sets to any other required target systems.
You must perform the Security Policy Manager procedures specified below, and create RACF or Top Secret resources on each system. Ensure that you grant Security Policy Manager user access to the required resources.
To migrate the complete runtime environment to other systems, complete the following steps:
Task | Description |
|---|---|
1 | Verify that the target system for the migration fulfills all of the criteria in Preparing-for-installation. |
2 | Transfer the following runtime data sets to the target system: |
3 | Complete all the steps listed from Authorizing-the-load-library onward under the Performing-the-installation topic. This completes the migration process. |
For more information, see Compliance Testing.