Once you define your names, define the environment for the Provisioning Manager. To start with, identify the primary z/OS® system on which you run the Provisioning Manager, and select alternative systems on which a backup of the Provisioning Manager can run if the primary system becomes unavailable. All of these systems need access to the Provisioning Manager data sets.
To allow a restart on an alternative system, the runtime information shown in Table 14 and all paths listed in Table 15 must be identical on the two systems. The term runtime systems refers to all systems on which the Provisioning Manager can run, but note that only one instance of the Provisioning Manager can run at any one time.
You can use z/OS Automatic Restart Manager (ARM) to restart the Provisioning Manager in the event of failure. To use ARM, define the ARM restart policy, element name, and element type. You can also use any other automation product that can restart the Provisioning Manager when needed.
The Provisioning Manager uses z/OS BCPii protocol to communicate with the hardware. BCPii is a method of communicating with the CPC support elements that does not require a network connection from the runtime system to the HMC. Instead, you must create security definitions on your runtime systems.
For these security definitions, you need the name of the community that BCPii uses to access the hardware console. Note that BCPii requires an uppercase community name. This community name must be authorized to issue read and write operations and to issue commands to change the temporary capacity, Defined Capacity or Group Capacity. You must set up the community name for each CPC that is managed by Capacity Provisioning and all CPCs on which the Provisioning Manager can run.
The access requirements for z/OS BCPii differ depending on whether you want to manage physical capacity (On/Off CoD), defined capacity, or both. Have in mind what you plan to manage when defining the security for hardware access.
The CPMC connects to the Provisioning Manager via the CIM server that runs on the same system as the Provisioning Manager. The connectivity between the CIM server and the Provisioning Manager domain(s) is configured in the CIM provider properties files for the Capacity Provisioning CIM provider. The default name and location for this file is /etc/cpoprovider.properties. For more information on the configuration of Capacity Provisioning CIM provider see Preparing the connection to the CIM server.
To create service information, the Provisioning Manager can write trace and log data. Because the data is temporary, it is usually written to the /tmp directory on the runtime system. If you want this data to be written to another location, you can redirect it to another file system. The selected path must be available on the runtime system, and the Provisioning Manager user must be authorized to write to this location. Service data can be deleted after it is sent to IBM®. Do not delete the data while the Provisioning Manager is still running.
Use the CPMC to define the policies and domain configurations for the Provisioning Manager. A web browser is required to run the CPMC program.
Table 14 contains a list of all necessary environment information, and the default values where applicable. Record any values you change for your domain in the table.