Browse Prior Art Database

System and Mechanism for determining and obtaining execution state for a topology model.

IP.com Disclosure Number: IPCOM000187729D
Original Publication Date: 2009-Sep-17
Included in the Prior Art Database: 2009-Sep-17
Document File: 9 page(s) / 100K

Publishing Venue

IBM

Abstract

This article describes a technique for determining and obtaining execution state for a topology model.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 50% of the total text.

Page 1 of 9

System and Mechanism for determining and obtaining execution state for a topology model.

There exists complexity in the determination of the overall execution state of a topology based on the severity and prioritization of issues. Known solutions exist for displaying problem statuses based on severity. However, these solutions do not offer prioritization of problems, indication of the effect on the topology, or allow for custom extensibility.

The following technique provides a method and user interface that holistically organizes and prioritizes problems for an entire topology. This central location helps navigate problems and solutions while providing iterative feedback as topology state changes. The prioritization allows for guidance in which problem to solve first. Known executions for the topology are gathered in the view; only when all the relevant problems are solved are these actions enabled. Additionally, extenders can add sections to the view based on the problem type.

In the determination of the overall execution state of a topology, there exists complexity based on the severity and prioritization of problems. Known solutions exist for displaying problem status based on severity. However, these solutions do not offer prioritization of problems, indication of the effect on the topology, or allow for custom extensibility.

Below (Figure 1) is an example of a typical problems view. There are icons in the left margin to indicate where the problems are, the severity, and in some case, suggested solutions to that specific problem.

1

Page 2 of 9

Figure 1.

Some of the disadvantages of this type of view include:

It does not offer resolutions without opening the text editor


The prioritization is based on status severity, and the order is based on where in the text file it falls. There is no consideration for problem type or scope (e.g., sometimes fixing one general problem can fix many other problems as well).

2

[This page contains 1 picture or other non-text object]

Page 3 of 9

The view is not extensible.

The view context is relative to line numbers in a single text file, which does not translate into a graphical diagram editor.

The current disclosure presents a user interface that holistically organizes and prioritizes problems for an entire topology in a separate view. This central location helps navigate problems and solutions while providing iterative feedback as topology state changes.

Some of the advantages of this of design include:

Prioritization allows for guidance in which problem, across the entire topology, to solve first in order to positively effect the topology. Frequently, solving a particular problem type will fix other related problems. This is an efficient way to divide and conquer complex problems.

The problems across the entire topology are gathered in a separate view, so it is not dependent...