Migrating to other systems


You can migrate the product to other systems without performing a full installation on each system. Perform one full SMP/E installation on one system and then migrate runtime data sets to required target systems.

You must create the product procedure and ESM resources on each system and grant users access to the required resources.

To migrate the runtime environment to other systems

  1. Verify that the target system for the migration satisfies the System-requirements.
  2. Transfer the following runtime data sets to the target system:

    • hlq.RSSLOAD
    • hlq.RSSDOCS
    • hlq.RSSSAMP
    • hlq.RSSPARM

    Modify the data sets as required.

  3. Authorize the load library as described in Authorizing-the-load-library.
  4. Complete all the steps in the Configuring-after-installation section.

Using Security Policy Manager across a multi-LPAR environment

In a multi-LPAR environment, you can log on to any SPM 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 an ESM 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 Updating-the-global-RSS-parameters.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*