10.2 Scenario: Displaying Network Dependencies

This example builds a configuration that displays dependencies in the network.

Assume that a Service Catalog hierarchy built using SCM shows all key services, but doesn’t provide any state information. A configuration can provide structure for other configurations without adding to the state information that is defined in subsequent configurations.

This scenario uses SCM to leverage a discovery tool adapter that runs discovery and links dependencies. The resulting list of supporting technology from a Tivoli T/EC adapter displays directly under the services. This enables analysis of affected services and discovery of previously unknown relationships.

This scenario uses:

  • A Service Catalog hierarchy that shows a simple listing of all key services

  • A discovery tool adapter to provide discovery on networks and dependency information

  • A Tivoli T/EC Adapter that provides state information to newly discovered objects found as a result of discovery by the discovery tool adapter

The following sections are specific to this scenario, but use features of the Service Configuration Editor that were described earlier in Section 8.0, Creating a Service Configuration:

10.2.1 Scenario Step 1: Creating a Parent Element in Services

To map dependencies among elements, the first step is creating the parent element of the new hierarchy:

  1. In the Explorer pane under Services, use the Add Element option to create an element that is the parent of the new hierarchy.

    In this example, name it Dependencies Linked.

    Dependencies Linked Element in the Tree

10.2.2 Scenario Step 2: Identifying an Existing Hierarchy

In this step, we identify an existing hierarchy that drives the shape of the new tree:

  1. Right-click the Dependencies Linked element we created in Section 8.3.1, STEP 1: Create the Service Configuration Definition, then select Service Configuration > Create to open the Service Configuration Editor.

  2. Create a Structure definition that adds the Service Catalog element as the Structure Root.

    The Service Catalog hierarchy contains a series of elements that represent key services.

    For more information about creating a structure definition, see Section 8.3.2, STEP 2: Define Structures.

  3. To see all elements contained in the Service Catalog hierarchy, leave Starting Depth and Ending Depth at 0.

  4. Use the default Matching Rule to apply a simple name match to select elements.

    For more information on matching rules, see Creating a Matching Rule.

10.2.3 Scenario Step 3: Defining the Sources of State Information

In this step, we define the sources of state information for the new configuration, select an existing hierarchy:

  1. In the Definition Navigator pane, click Dependencies Linked Element in the Tree (New Source).

    For more information on sources, see Section 8.3.3, STEP 3: Define Sources.

  2. Click Dependencies Linked Element in the Tree (Browse for Root Element) to select the Source Root.

    In this example, select the Hosts branch of the Tivoli T/EC adapter.

  3. Use the default join rule to link state information to structure elements using a simple name match.

    This definition makes available state and property information for all new elements found when the configuration searches for dependencies.

    For more information on join rules, see Using Join Rules.

10.2.4 Scenario Step 4: Defining Dependencies

In this step, we define Dependencies for the configuration by specifying dependency rules to apply to a related hierarchy:

  1. In this example, create a Dependency Consumer definition, then select the By Network branch of a discovery tool adapter as the Dependency Root, as shown in the illustration in Step 3.

    The By Network hierarchy is from a discovery tool adapter that has run discovery on the networks. It contains listings of servers and applications organized by network.

    For more information on Dependency Consumers, see Using Dependency Consumers.

    For more information on defining Dependencies, see Section 8.3.4, STEP 4: Define Relationship Dependencies.

  2. Use the default join rule to link discovered elements to structure elements using a simple name match.

  3. In the Dependencies Selected section, browse the known dependencies for the selected Dependency Root, then select one or more dependencies.

    The selected dependencies display in the Dependencies Selected list as shown in the following illustration:

    By Network Element in Definition Navigator Panel

    The selected dependencies and the join rules together determine which relationship information is included in the new configuration.

10.2.5 Scenario Step 5: Configuring Generation Under Modeling Policies

In this step, under Modeling Policies, we will define Generation and Correlation policy rules:

  1. Expand Modeling Policies, then click Generation or Correlation.

    For more information on Generation modeling policies, see Section 8.3.5, STEP 5: Select Generation Options.

    For more information on Correlation modeling policies, see Section 8.3.6, STEP 6: Select Element Correlation Options.

  2. In the Generation policy page, select the Display Source Elements As Children check box.

    This creates a link to source branches where matches occur and displays source elements as children.

    For more information about Generation, see Section 8.3.5, STEP 5: Select Generation Options.

  3. To include state and property information from the source Tivoli T/EC adapter for structure elements, select the Create State Relationship to Structure Elements and Copy Properties from Structure Elements check boxes.

    Retain Correlation defaults to correlate configuration objects using a basic Static Match. Those objects that are matched are included in the new configuration tree.

    For more information about Correlation, see Section 8.3.6, STEP 6: Select Element Correlation Options.

    In this example, defined sources provide state information to the new objects discovered from the search for dependencies:

    Generation Element in Definition Navigator Panel

10.2.6 Scenario Step 6: Generating a New Hierarchy & Schedule Configuration Regeneration

In this step, we generate the new hierarchy and after verification, we create a schedule to keep the hierarchies updated:

  1. Click Save to save configuration settings.

  2. Click Generate to generate the new hierarchy.

  3. Verify the results of the new configuration are what you expected.

  4. Create a schedule to generate the service configuration on a routine basis.

    Because this view provides insight into the entire environment, this configuration should be regenerated when changes occur, which is sometimes predictable. For example, set up a schedule to automatically generate this configuration to coincide with the end of each scheduled shift.

    In some environments, it could be necessary to schedule this type of configuration to run more often—as frequently as every five minutes.

    For more information on creating a schedule, see Section 8.3.9, STEP 9: Test and Generate the Configuration.