Defining the visual model

You can associate a Scalable Vector Graphics (SVG) diagram with a monitoring context or key performance indicator (KPI) context. You can then annotate these diagrams in the Monitor Model editor so that they are dynamically updated at run time. Each diagram is associated with a set of shapes and a set of actions describing how and when the diagram will be modified based on the values of metrics (in a monitoring context) or KPIs (in a KPI context). The actions include color changes and text displays based on the values, as well as hyperlinks from areas of the diagram so that you can navigate to other diagrams.

About this task

If you exported a monitor model, each monitoring context is associated with an SVG representation of the process, loop, or subprocess diagram. Each KPI context is associated with an SVG representation of the process diagram.
To view and test SVG diagrams in the Monitor Model editor, the system default web browser must have an SVG viewer installed as a plug-in. You can verify whether you have an SVG viewer by attempting to open an SVG file. If the diagram opens in the browser, your system is correctly configured. Otherwise, download the Adobe SVG Viewer from http://www.adobe.com/svg/.
Restriction:
  • In Internet Explorer, SVG diagrams that contain double-byte characters might not be displayed properly in the Visual model page of the Monitor Model editor. If you encounter this problem, use IBM® Installation Manager to install the web development tools package to IBM Integration Designer or IBM Rational® Application Developer.
  • On a 64-bit system, click Open in External Browser on the Visual model page to open the SVG diagram.
Tip: The Global Monitoring Context wizard automatically generates an annotated SVG diagram showing the important milestones that can tracked by your monitor model.
  • Preparing SVG diagrams
    Any Scalable Vector Graphics (SVG) file can be used as a static diagram to be displayed in the Diagram view based on a monitoring context or KPI context. For the diagram to be updated dynamically at run time, you must declare a namespace definition in the SVG file and assign monitor model IDs to the shapes that will be associated with actions. Shapes can change color, display text, link to other diagrams, or be hidden or displayed based on the values of metrics or KPIs.
  • Attaching diagrams to contexts
    After you have assigned IDs to the shapes, you can import the Scalable Vector Graphics (SVG) file and attach it to a context in the Monitor Model editor.
  • Defining actions
    To be updated dynamically at run time, a Scalable Vector Graphics (SVG) file needs a group of named shape sets for referencing sets of individual shapes in the SVG diagram. It also needs a set of actions (such as color or text changes, or effects on widgets in the Monitor dashboard space) that describe how the SVG elements represented by the shape sets change their properties based on the values of metrics or key performance indicators (KPIs) at run time.
  • Synchronizing diagrams
    If you change a Scalable Vector Graphics (SVG) diagram outside the Monitor Model editor, you must synchronize it with the visual model.
  • Testing diagrams
    After you have added shape sets and actions to your Scalable Vector Graphics (SVG) diagrams, you can add sample data to test the diagrams in the Monitor Model editor. You can also check the return values of visual model expressions to make sure that they are working as you intended.
  • Removing diagrams
    You can remove a diagram from the monitor model in one of two ways. You can either remove the complete visualization, including the Scalable Vector Graphics (SVG) file reference, shape sets, and actions, or you can remove only the SVG file reference.
Parent topic: Creating monitor models