How You Use a PMDB to Propagate Configuration Settings

When you edit a Policy Model's configuration, the new configuration values are propagated to the Policy Model's subscribers. The following process describes how configuration updates are propagated to a Policy Model's subscribers:
capamsc141
When you edit a Policy Model's configuration, the new configuration values are propagated to the Policy Model's subscribers.
The following process describes how configuration updates are propagated to a Policy Model's subscribers:
  1. You edit one or more of the Policy Model's configuration values.
  2. The Policy Model writes the new configuration values to the virtual configuration file.
Note:
The virtual configuration file does not contain values for the audit.cfg file. The Policy Model does not write any changes that you make to this file to the virtual configuration file.
  1. The Policy Model sends the new configuration values to its subscribers.
  2. selang commands update each subscriber with the new configuration values.
Virtual Configuration File
Each Policy Model has a virtual configuration file that contains the configuration values for its subscribers. The virtual configuration file is located in the PMD directory, and is named cfg_
configname
, where
configname
is the name of the Policy Model configuration.
The virtual configuration file does not contain the configuration values held in the audit.cfg file.
How New Subscribers Are Configured
The Policy Model configures each new subscriber with the existing configuration values. The existing configuration values are stored in the virtual configuration file.
Note:
The virtual configuration file does not store configuration values from the audit.cfg file. Any changes that you make to the audit.cfg file before creating a subscriber are not propagated to the new subscriber.
The following process describes how a Policy Model configures new subscribers:
  1. You create a subscriber to the Policy Model.
  2. The Policy Model reads the values in its virtual configuration file.
  3. The Policy Model adds the configuration values from its virtual configuration file to the updates.dat file. The updates.dat file also contains the access rules for the Policy.
  4. The Policy Model sends the updates.dat file to the new subscriber.
  5. selang commands configure the new subscriber with the values in the updates.dat file.