A policy sweep processes the objects in a database table in an ongoing manner. In terms of implementation, a policy sweep consists of two main components: a policy component and a sweep component. Policies subscribe to sweeps in a many-to-one relationship: many policy components might share a sweep component. When you create a policy component, the appropriate sweep component is created automatically.
The purpose of this implementation is to optimize sweep efficiency. For example, rather than two policy sweeps independently iterating through the same table, one sweep component iterates through the table on behalf of the two policies. The sweep component passes objects from the table to the two policy components for policy-specific handling.
To open the sweep for a policy: