How to Retrieve Impact Analysis Results – Scenario

Impact Analysis Manager enables you to create an Impact rule that allows you to simulate the impact certain infrastructure changes have on your system. The results of the Impact rule are displayed in IT Universe Manager. The Impact Analysis results in this task describe how a change in CPU operation impacts the node to which it is connected.

This task includes the following steps:

1. Define an Impact Analysis TQL Query

   To define an Impact Analysis TQL query, you need to create an Impact rule and then add the TQL query nodes and relationships that define the query.

   To create an Impact Analysis TQL query, select Managers > Modeling > Impact Analysis Manager. For details about how to add query nodes and relationships to a query, see How to Add Query Nodes and Relationships to a TQL Query.

   Example of an Impact Analysis TQL Query:

   In this Impact Analysis TQL query, a CPU and a node are linked by a Composition relationship.

   

2. Define an Impact Rule

   When you define an Impact rule, you must specify the required causal relationship between the query nodes. Define one query node as the trigger, or the query node that represents the changes you want to make to the system, and another query node as the one that is impacted.

   Right-click the query node you want to define as the trigger and select Define Impacted to open the Impacted Query Nodes dialog box. Select the query node that you want the trigger query node to impact and click Next. Then click the Add button to open the Impact Rules Definition dialog box to set conditions for defining impacted query nodes. For details about how to define an Impact rule, see Impact Rules Definition Dialog Box.

   Note The change state option in the Impact rule definition is no longer relevant for Impact Analysis. The only supported state is operation.

   Example of an Impact Rule:

   The Conditions area in the Impact Rules Definition dialog box defines the conditions under which the simulated change in the system is triggered. The Severity area defines the severity of the impact on the impacted query node.

   The Impact rule in this example states that when the CPU operation is not in the normal state, the node is impacted. Since the severity is set to 100% of the trigger's severity, the severity of the node is the same as the severity of the CPU, which is determined when Impact Analysis is run.

   

   In the resulting TQL query, an upward arrow appears next to the query node defined as the trigger query node and a downward arrow appears next to the query node defined as the impacted query node.

   

3. Create a View in the Modeling Studio

   Go to the Modeling Studio and create a view matching the TQL query of the Impact rule you defined. For details, see Pattern View Editor.

4. Get Impact Analysis Results

   Select Managers > Modeling > IT Universe Manager and select the required view in the CI Selector. To get Impact Analysis results, run the Impact rule on a CI instance in the topology map that is a trigger. Right-click a trigger CI and select Run Impact Analysis to open the Run Impact Analysis dialog box. In the dialog box, select the Impact rules to run. If you want to select Only Impact rules located in specified bundle, make sure to add your Impact rule to the required bundle using the Properties option for the selected Impact rule. For details, see Impact Rule Groups Page.

   For details on how to run an Impact rule, see Run Impact Analysis Dialog Box.

   Example for Getting Impact Analysis Results:

   An Impact Analysis TQL query is created containing a CPU and node connected by a Composition relationship. The CPU query node is defined as the trigger query node and the query node of type node is defined as the impacted query node.

   The following Impact rule is defined for the query.

   

   Right-click a CPU CI in the view, and select Run Impact Analysis to open the Run Impact Analysis dialog box. Set the trigger severity to a value other than Normal.

   

   To see results, click one of the following:

   • Show in Views. This assigns a status to all the CIs in the view. Only the node CI connected to the CPU CI (whose severity was changed), becomes impacted. The trigger CI and the impacted CI turn orange because the trigger severity was set as Major (7) on the scale in the Run Impact Analysis dialog box, which is assigned an orange color.

   

   • Show Map. A map appears in a separate window containing only the trigger CPU CI and the node CI it impacted. The relationship connecting the two CIs contains the name of the Impact rule defined in Impact Analysis Manager.

     Note Optionally, you can create a URL that enables you to embed the map. For details, see Direct Link Parameters – Impact Map Page.

   

   • Generate Report. Generates an Impact Analysis report that displays a list of CIs that are impacted in the system as a result of the simulated changes. For details, see Run Impact Analysis Dialog Box.

Related Information