View Manager

© 2008 Hewlett-Packard Development Company, L.P.The information contained herein is subject to change without notice

Lesson # 9

HP UCMDB 8.0 Essentials

View Manager

2

Lesson Objectives

In this lesson, you will learn how to:• Navigate the areas of View Manager including the

Definition and Preview area• Use View Manager to create a view• Describe the purpose and use of grouping by CI

type, TQL node and attribute • Use grouping strategies to organize a view• Describe the purpose and use of folding and

relationship folding rules• Use folding and relationship folding to organize a

view• Describe and use the visible property on a node

About this Lesson

3

View Manager Overview

View Manager is used to• Create a new or edit an existing View

– Create and edit the view definition– Create and edit a View TQL – Define grouping and folding rules for view organization

• Preview a View

• Manage Views through the View Explorer– Organize views– Activate and Deactivate a view– Export a view to XML– Delete, Save As

View Manager Introduction

4

View ManagerView Manager Walkthrough

5

View Manager Definition Page View Manager Walkthrough

Views Explorer

CI Type Selector

Editing Pane

Information Pane

6

View Manager Preview Page

Generating a View Preview• View Explorer -> Select the

“Generate Preview” Button or right-click and select the “Preview” menu.

• The Result contains a list view and a topology view of all CIs retrieved by the View TQL.

View Manager Walkthrough

7

Understanding View Components

View Definition• Basic View properties

– View Name, View Type, how often it will be refreshed, TQL name

Query• TQL request to the UCMDB to

retrieve data

Organization Rules• Grouping ‘like’ kinds of data• Layering data• Labeling data

View Creation Overview

8

View Definition Overview

Creates the View structure

Associates the TQL with the view

Associates other properties with the view• View Type• View persistence• Change tracking• TQL priority


9

Creating A New View Definition

Create a New…

• View

– Pattern View (based on TQL)

– Template-based

• Template

• Perspective

– Covered in the Modeling Studio Chapter


10

View TypesPattern View• Built from a TQL query (new or existing). • When the view is displayed or refreshed, View Manager queries

the CMDB for all elements that fit the query, and automatically updates the view with those elements.

Template-Based View• Based on a TQL query, to which a template is then applied. • The template is a reusable view that includes parameters,

folding rules, and other settings, which are saved as part of the template.

• This enables you to build multiple views with the same settings without having to re-enter the setting information.

Perspective-Based View• Built by selecting a collection of individual CIs and applying a

special type of template, known as a perspective– Instance views, which no longer exist, are replaced by

perspective based views. Perspective based views cannot be viewed or edited in View Manager, but Modeling Studio instead.


11

New View Wizard – Welcome and GeneralView Creation Overview

12

New View Wizard – Base SQL DefinitionView Creation Overview

13

New View Wizard – Viewing OptionsView Creation Overview

14

New View Wizard – Wizard CompletionView Creation Overview

15

TQL Query Review

Created with TQL

Define the CITs and relationships to be used to request data from the CMDB

May be filtered by conditions to restrict the objects in the result set • Node properties• Relationship properties

May be new or pre-existing


16

Creating a View TQL

Created in View Manager or Query Manager

Nodes

Relationships

Conditions• Attributes• Select Identities• Cardinality

Properties• Include

Subtypes


17

Organization Rules Overview

Determines how nodes and links will be displayed in the view

Defines the map layers to be displayed

Accomplished with grouping and folding techniques

May be applied to nodes and relationships


18

Managing View OrganizationProvides a clear presentation for understanding managed data

Ability to design self explanatory views for impact analysis and problem isolation

Respond to multiple business objectives while reusing the same TQL

Required to manage limitations of number of CIs in a view (900 by default)

Various options to modify appearance, number of layers in a view, and drill-down path• Grouping, Folding Rules, Relationship Rules


19

Grouping Overview

Group ‘like’ CIs together for organizational purposes

Three different types of grouping are available

• Group by Configuration Item Type• Group by TQL Node• Group by Attribute

Grouping can be combined or used standalone

Grouping can be used on nodes or relationships or both


20

Adding Grouping to a Node

Right-Click -> Select “Node Grouping”


21

Grouping by Configuration Item Type

All CIs of the same type placed into a group

Minimum in group

Group Label


22

Grouping Hosts by CI TypeView Creation Overview

23

Grouping Web Servers by CI TypeView Creation Overview

24

Grouping by Node

All CIs of the same type grouped by the node definition criteria

Minimum in group

Group Label


25

Expanding Grouped Web Servers NodesView Creation Overview

26

Grouping by Attribute

CIs grouped by value of selected attribute

CIs may be of different types

Minimum in group

Group Label


27

Grouping by Application Listening Port Attribute


28

Grouping by Host OS AttributeView Creation Overview

29

Adding Grouping to a RelationshipView Creation Overview

30

Grouping Relationship by TQL NodeView Creation Overview

31

Rules implemented to simplify views

Provides layering of TQL results

A solution to “Too many CIs to display“ error• A graph cannot present more than 900 objects.

Two types of rules• Folding (applied to a link between two nodes)• Relationship (applied to a link class across the entire

view)

Folding rules override relationship rules when both are defined for a view


View Rules Overview

32

Defines layering for two nodes connected by a specific relationship

Arranges the CIs in multiple layers

Defines the position of CIs in each layer

Rules• Parent, Child, Left Sibling,

Right Sibling, None


Folding Rules Overview

33

Using the Parent RuleView Creation Overview

34

Using the Child RuleView Creation Overview

35

Parent and Child ExamplesView Creation Overview

36

Left Sibling Rule ExampleView Creation Overview

37

Relationship Rules Overview

Relationship rules are an alternative to folding rules

Relationship folding rules are applied to CI relationships across the view

Sibling and child rules are allowed together

Parent and child rules are not allowed together

Right and left sibling rules are not allowed together


38

Relationship Rule Defined

Information Pane• Folding Rule Tab

describes the folding rule in place

Relationship Rule• Relationship always

begins at node 1 and ends at node 2

• Can be edited

Rule Options• Click on “Edit” button in

Folding Rule Tab• Parent, Right Sibling,

Left Sibling, Child, None


39

Using the Relationship Parent RuleView Creation Overview

40

Using the Relationship Child RuleView Creation Overview

41

Identifying Organization StrategiesGROUPING AND FOLDING RULES: ACTIVITY

What grouping and folding rules are in use?

42

Identifying Organization StrategiesGROUPING AND FOLDING RULES: ACTIVITY

What grouping and folding rules are in use?

43

Visible Property Overview

Node or relationship property selected by default

When deselected, the node or relationship will not appear in the view

Used to manage nodes or relationships necessary in the TQL but which may not enhance the view if visible


44

Editing Visible PropertyView Creation Overview

45

Using Visible PropertyView Creation Overview

46

Managing Views in View Explorer

View Explorer is used to

• Organize views for easy navigation in IT Universe Manager and Topology View application

• Activate and Deactivate a view to make it available or unavailable to the system

• Export and import Views in XML format


47

Organizing Views in View Manager

Folder

• New, Rename, Delete

Views

• New View Definition

• Save As

• Import/ Export to/from XML

• Properties


48

Review Questions

1. What view property ensures a view is always loaded in memory?

2. What view organization rules would you choose to reduce the amount of nodes displayed in a view?

3. What view organization rules would you choose to reduce the number of links between nodes in a view?

4. What is the difference between folding rules and relationship folding rules?

5. Which view organization rules would you use to ensure that the TQL result is shown in layers?

Chapter Review

49

Summary

Key points in this lesson

• View Manager enables you to define a managed view

• A view TQL is associated with each view

• Organization rules are used to define the display structure of CIs in a view

• Grouping and folding are two ways to organize CI information in a view

• Grouping may be defined by CI type, TQL node, or attribute

• Relationship folding rules are applied to the view and folding rules are applied to a specific relationship in the view

Chapter Summary

50

Exercises

Please complete the lesson exercises in your book.

After everyone is finished, the instructor will review the answers.

Chapter Exercises

View Manager

Documents

Transcript of View Manager