Use > Configuration Manager > Working with Configuration Manager > Automation Policies > Configuration Manager Automation Policy - Use Case

Configuration Manager Automation Policy - Use Case

Note This module is only valid for use by customers who purchased the relevant license for Universal CMDB Configuration Manager versions 9.2 or 9.3. New customers cannot purchase this license.

It is recommended to use the UCMDB Browser module > Automation widget to configure automated flows that are based on Configuration management conditions. For details, see the section about the Automation widget in the CMS UI > UCMDB Browser module online help.

This section describes a use-case for defining an automation policy in Configuration Manager.

  1. Background

    The owner of the Factory Portal application (an example application) needs to continually monitor the high-availability of his application. As a result, it is important to guarantee that when changes occur, the application will continue to function in accordance with its agreed to requirements.

    Toward this end, the application owner wants to define an automation policy that gives an indication in the event that:

    • An automation which implements a change causes application downtime

    • The CI is directly affected by more than one automation.

  2. Prerequisite - Import the Managed View from Universal CMDB

    The application topology is modeled in a view in Universal CMDB. Once you import the required view, there is a corresponding managed view in Configuration Manager. The following image displays the Factory Portal application topology in Configuration Manager:

    For details on how to import a managed view, see Add a View to be Managed.

  3. Define the Automation Policy in Configuration Manager

    1. Navigate to Administration > Automation Policies to create a new automation policy.

    2. In the General area, do the following:

      • In the Name box enter: Causes downtime and a CI collision on the Factory Portal application.

      • (Optional) In the Description box, enter the required description.

      • Use the Perform Validation check boxes to define the frequency of policy validation.

    3. In the Scope area do the following:

      • Select Selected Views and click the button to select the managed view to which to apply the policy.

      • In the Assign CI Type box, click the button to select BussinessApplication as the CI type to be tested against the policy.

    4. In the Restriction area, do the following:

      • Under Automation restriction conditions, select Causes Downtime.

      • Under CI restriction conditions, select Direct Collision Exists.

    5. Save the new automation policy.

  4. View Policy Evaluation Results

    You can view the policy evaluation results within the context of running a controlled automation. For details, see Run a Controlled or Non-Controlled Automation.