Pap
ordering. All of these methods affects both the repository and the configuration. Use the {@link PapManager#initialize()} method before doing anything with this class.
The PAP service has always one (special) pap defined. This pap is commonly identified in the code with the word default. The alias of this special pap is defined by the constant {@link Pap#DEFAULT_PAP_ALIAS} (its value is {@value Pap#DEFAULT_PAP_ALIAS}). The default pap is local and public.
Paps ordering
For the policy evaluation process (performed by the PDP) the oder of the policies matters. Therefore it is possible to specify an ordering for the Pap
objects (which are containers of policies). The policies of Pap
A are evaluated before the policies of Pap
B if A comes before B in the order. There are two points concerning the pap ordering that must be kept in mind:
1. if the defdault pap is not listed in the pap ordering then it is automatically placed as the first pap in the order;
2. if the pap ordering does not contains all the defined paps then the paps not listed in the order comes after (except the default pap, see point 1).
Repository and configuration
The information associated to a Pap
object are stored both in the repository and in the configuration. Since the configuration can be changed off-line (when the PAP service is not running), synchronization between the configuration and the repository is needed at startup time. See the method {@link PapManager#synchronizeRepositoryWithConfiguration()}.
Information like the polling interval and the pap ordering are only in the configuration.
@see Pap
@see PapContainer
@see DistributionConfiguration
@see PapDAO
@see DistributionModule
|
|
|
|
|
|