Installation overview
Within a sysplex, Security Policy Manager instances support cooperative processing and provide a centralized view across the sysplex.
An optional REXX address space is provided, which is required only if REXX security policies are in effect.
As the system administrator, perform the following tasks to install Security Policy Manager:
Task | Preinstallation tasks | Reference |
|---|---|---|
1 | Review system requirements. | |
2 | Prepare your system for installation, including the following tasks:
| |
Task | Installation tasks | Reference |
1 | Run the INSTALL procedure from the installation data set. Review and run the JCL deck that it builds. | |
2 | Authorize the load library. | |
3 | (CA Top Secret only) Install the Top Secret installation exit TSSINSTX. | |
4 | Create the external security manager (ESM) resources and make sure that all users have read access to the required resources according to their authority level. | |
5 | Define the profiles and rules (depending on the ESM) for the required features. | |
6 | Define the started task to the ESM. | |
7 | Create the database directory. | |
8 | Review and edit the product configuration in your hlq.RSMPARM so that it conforms to your installation requirements. | |
9 | Configure the parameters that are necessary to start the product. | |
10 | Create a started task user. | |
11 | Define the checkpoint data set. | |
12 | Review and edit the sample product startup JCL procedures and copy them to your production PROCLIB. | |
13 | Start Security Policy Manager and verify the startup messages. |
You do not have to perform a full installation of the product on each system on which it is required. Perform one full SMP/E installation on one system and then migrate the runtime data sets to any other required target systems. For more information, see Multi-LPAR-environment-installation-considerations.