Configuration Manager Similarity Policy - Use Cases

This scenario includes the following steps:

• Background

• Define a Similarity Policy

1. Background

   A UNIX lab administrator has the following view managed in Configuration Manager:

   

   He wants to ensure that all the UNIX machines that are connected to an Oracle database (that is, those highlighted in the diagram above) have the same OS version. Since he always likes to make sure his machines are running the latest patch, this version changes often.

2. Define a Similarity Policy

   In Configuration Manager, navigate to Policies and create a new similarity policy.

   1. Deselect the Enable grouping check box.

   2. Set the name and description.

   3. Select UNIX as the main CIT.
   4. Filter the comparison scope by Related to Oracle.

   5. Select the OS version attribute as the similarity criterion.

      Note This is unlike a baseline policy, which contains fixed attribute values that are entered when the policy is created or updated.

   The new policy dynamically and constantly detects any misalignments in the OS version attribute of each of the UNIX machines that are highlighted in the diagram above. This means that the user does not have to manually update the policy definition every time an upgrade occurs in the environment.

   After defining this policy, policy status icons are displayed in the Review/Authorize, Changes History, Authorization History, and Explore Views modules.

In this example, the attributes that must be the same are Application Installed Path, Application Version Description, Vendor, and Version.

This scenario includes the following steps:

• Background

• Create Views

• Define a Similarity Policy

1. Background

   A user has the following view managed in Configuration Manager:

   

   Since there are many clusters and many application servers in each cluster, he wants to ensure that for each cluster, the application servers have the same defined attributes.

2. Create Views

   Use the view shown above or create new views (each containing a cluster) to test against the policy.

3. Define a Similarity Policy

   In Configuration Manager, navigate to Policies and create a new similarity policy.

   1. Make sure that the Enable grouping by CI type and pattern check box is selected.

   2. In the Grouping section:

      • Select the grouping CI type (in this example, Cluster).

      • Select the grouping TQL that defines the desired path between the Cluster CIT and the application server. For example:

        

        

   3. Set the name and description.

   4. Select the Version attribute as the similarity criterion.

      Note This is unlike a baseline policy, which contains fixed attribute values that are entered when the policy is created or updated.

   The new policy dynamically and constantly detects any misalignments in the compared attributes of each of the highlighted application server groups shown above. This means that the user does not have to manually update a policy definition every time an upgrade occurs in the environment. Note that the compared attributes are compared only within each cluster group, and not between groups.

   After defining this policy, policy status icons are displayed in the Review/Authorize, Changes History, Authorization History, and Explore Views modules.