Capacity Provisioning includes samples that you can use to set up a new domain. These samples contain default values for element names. If you are satisfied with these defaults, do not change them when you set up the domain. If you choose a different naming convention, replace all occurrences of the default names with the names you select during the actual definition steps. Table 13 includes space for you to record the names you choose. The following paragraphs describe the element names, their default values, and their meaning.
Each domain is identified by a domain name. If you use multiple domains, each name must be unique. For more information about the rules for a valid domain name, see Naming conventions.
The Provisioning Manager runs as a started task, by using an entry setup for this purpose in the procedure data set for started tasks used in your installation (normally SYS1.PROCLIB). A sample started task procedure, CPOSERV, is delivered in SYS1.SAMPLIB. Copy this procedure or an equivalent to your started task procedure data set. If you choose a name other than CPOSERV for the started task, you must name the member in this data set accordingly.
When the Provisioning Manager starts, a user is assigned to the started task. This user must be defined and authorized for all resources accessed by the Provisioning Manager. The Provisioning Manager user requires a unique UNIX identifier (UID). You also must define a default group for the user and an OMVS segment that specifies a home directory.
The Provisioning Manager connects to the observed systems to retrieve performance data. For this it uses a distinct userid, the so called System Observation user. This userid has to be defined on the runtime system as well as on the observed systems. Because the System Observation user is authenticated with PassTickets, it requires a unique UNIX identifier (UID), it cannot be defined as a protected user, and it must be assigned a password.
The default userid for the System Observation user is CPOCIM. To change the default you have to update the configuration key SystemObservation.UserName in the Provisioning Managers PARM member. If you do not specify a userid for this key, the Provisioning Manager started task user is used for system observation.
The Provisioning Manager contains status and configuration data in data sets. The names of these data sets use the same high-level qualifier, to make security definitions easier.
Provisioning policies and domain configurations are defined by using the CPMC. If a connection is set up between the CPMC and the Provisioning Manager, you can install and activate policies and domain configurations directly from the CPMC. In this case, the user of the CPMC must connect to the CIM server on the system where the Provisioning Manager runs. Different security definitions are needed according to the operations required:
The Provisioning Manager and the CPMC communicate by using the CIM protocol. The CIM server user is required to set up security definitions for the communication, see Defining security for the Capacity Provisioning Management Console user.
Table 13 contains a list of names to be chosen and their default values. If you do not use the defaults, make a note of the names you use.