The challenge of managing a heterogeneous enterprise is one of the most daunting problems facing IT professionals today. The sheer number of resources (systems, applications, network devices, etc.) in a single environment can be quite large and ever-changing, and a typical administrator may have no accurate catalog of his environment—let alone an understanding of the interdependencies that his resources have with each other. However, sophisticated tasks (e.g., taking down a server, moving workload, etc.) can be difficult (and risky) without this knowledge. Clearly, there's a need for advanced, automated applications to help system administrators in this area.

IBM took steps to address this problem by introducing the IBM Virtualization Engine console resource topology. Resource topology is an innovative approach to allowing systems administrators to visualize resources and relationships in their enterprise as collected and discovered by IBM Resource Dependency Service (RDS).

Resource topology makes overall system management in a heterogeneous environment easier by providing the following:

• Visualization of resources and relationships in an environment that facilitates reasoning about how changes to a particular resource might affect other resources. (For example, visual topology data could be used to improve backup and recovery strategies by allowing an administrator to infer what will happen if a disk unit, server, or application fails.)
• Powerful browse and search capabilities that help find the resources of greatest interest among the thousands (or millions) or resources potentially discovered by RDS
• The ability to display and edit resource properties
• Functionality to create and delete resources and relationships to augment the discoveries made by RDS
• User-defined groups that form user-defined logical sets of the resources of greatest importance

Understanding the Virtualization Engine Console

The goal of the Virtualization Engine console is to enable the management of solutions rather than specific IBM products by removing operating system boundaries and maximizing the sharing of resources. In its second release, the Virtualization Engine console consists of several complementary components that allow administrators to monitor and manage key eServer systems. It is the user interface identity of the set of Virtualization Engine technologies, and it works with any standard Web browser.

Understanding RDS

RDS gathers information about the IBM and non-IBM virtual and physical resources in an IT environment to be used by the resource topology user interface. RDS uses the following methods to gather this information:

• Collection is the process of gathering information that exists in remote data repositories or endpoints. RDS collects data from DB2 Universal Database, Enterprise Workload Manager (EWLM), IBM Director, System i server, Tivoli Business Systems Management (TBSM), Tivoli Configuration Manager (TCM), WebSphere MQ, WebSphere Application Server, and zSeries server.
• Discovery is the process of acquiring new information that is not in an existing data repository. To acquire this new information, RDS uses a component called Intelligent Device Discovery (IDD) to search the network for resources that are not in a data repository.

Using Resource Topology

After installing the Virtualization Engine console and RDS, open the console in any Web browser and select the following path in the left-hand navigation frame: Virtualization Engine Console > Hardware and Software > Resource Topology. This will launch the resource topology portlet (Figure 1).

Figure 1: Here's your Managed Resources home view. (Click images to enlarge.)

Each node in the Managed Resources home view represents one of the 12 resource types known by RDS. The number next to each label represents the number of resources of that type that have been discovered (or, in the case of Groups and Services, the number that have been created by the user). The table below lists the resource types and their descriptions.

Note that RDS requires configuration to run collection and discovery. If it appears that discovery has not been run, resource topology provides a button to launch the Resource Dependency Service Configuration tool (which is also located in the console at Virtualization Engine Console > Virtualization Engine Setup > Resource Dependency Service Configuration) to allow the user to configure, schedule, and manage data collection of his physical and logical IT assets.

Finding Resources and Building a Topology

The search and browse features of the home view allow users to find a discovered resource of any type and make it the center of its own topology. This provides a powerful means for an administrator to drill down through arbitrary slices of his environment as he seeks to make informed management decisions.

For example, to see the list of resources for a given type, the user can right-click on the node for the type to see its context menu. Figure 2 shows the context menu for the Operating Systems node.

Figure 2: Right-click on the node to see the resource's context menu.

The Open submenu has options for Search 'Operating Systems...' and All Operating Systems. Depending on the enterprise, the number of resources for a given type can be quite large, so the search option (which allows a wildcard search based on name) is typically recommended to help reduce the result set size.

After clicking All Operating Systems, the user will see all of the operating systems that RDS has discovered (Figure 3). The table features advanced sorting and filtering to narrow down the list of resources if desired.

Figure 3: By selecting All Operating Systems, the user sees all of the operating systems that RDS has discovered.

For the purposes of this example, the user is interested in finding out what system the sys12.mycompany.com operating system is installed on. Figure 4 shows the context menu for sys12.mycompany.com. Under the Open submenu, there are three options (Child, Parent, All) for generating a topology with sys12.mycompany.com as the root node, showing what other discovered resources it's related to. The Child option would show what resources have relationships from the root node, the Parent option would show what resources have relationships to the root node, and the All option would show all resources that have relationships either to or from the root node.

Figure 4: Choose Child, Parent, or All to see what other discovered resources the root node is related to.

Figure 5 shows the topology that resulted from choosing the Open > All option. With help from the relationship legend (Figure 6), it can be seen that the operating system represents an instance of i5/OS installed on the sys12.mycompany.com system (an System i Model 840). Furthermore, it hosts a data container (IFS1 of the IFS file system type), a network interface (1.2.3.4), a database (U102ZBDM), and 77 applications. (As a side note, it should be pointed out that RDS is uniquely capable of discovering System i-specific resources such as installed LPPs and IASPs in DB2.)

Figure 5: This is the "All" topology of depth 3 with a root node of sys12.mycompany.com.

Figure 6: The topology relationship legend helps identify color-coded dependencies.

From this point, any resource of interest within the currently displayed topology can be explored to see what else it might be related to simply by invoking the appropriate context menu item. For example, if a user wanted to see what applications are hosted by the operating system, he could choose the Open > Applications menu option on the Applications node. Similarly, the depth of the topology can be changed (see the Depth box at the bottom of Figure 5) to go further from the root node to find more relationships.

In addition, this view enables other features:

• Properties for the selected resource or relationship are displayed in the area in the lower right of the display (which can also be edited by clicking the Edit button).
•  RDS discoveries can be enhanced by creating user-defined resources and relationships that will also appear in the graph.
• Resources of interest can be added to custom groups (e.g., logical sets of resources representing business processes, etc.) to more easily find them from the home view later.
• Standard graphical options such as zooming, panning, etc. are available. In addition, when zoomed in on the graph, the blue box in the Overview window shows the part of the graph that's visible, and the small blue box can be used to pan to other parts of the graph.

Make Better Systems Management Decisions

The Virtualization Engine console resource topology provides a powerful means for system administrators to visualize, explore, and work with Virtualization Engine resources and relationships that RDS has discovered within their IT environments. With these advanced visualization capabilities, administrators are empowered to more efficiently keep track of their resources and make sophisticated systems management decisions.

Tony Erwin is a software engineer in IBM's Rochester, Minnesota, lab. He has extensive GUI design and development experience, working on such products as iSeries Navigator, the Abstract User Interface Markup Language (AUIML) toolkit, and the IBM Virtualization Engine Console. You can email him at This email address is being protected from spambots. You need JavaScript enabled to view it..

Also Read

Practical Middleware: Architecting for the Future

Practical Middleware: Starting the Journey

IBM i 7.2: The Carrot Versus the Stick