Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Transformation of message flow monitoring information into an executable monitor model

IP.com Disclosure Number: IPCOM000198749D
Publication Date: 2010-Aug-13
Document File: 4 page(s) / 102K

Publishing Venue

The IP.com Prior Art Database

Abstract

This disclosure describes a process which transforms the information of multiple flows into a manageable and executable monitor model that could be deployed onto the monitor server.

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 41% of the total text.

Page 1 of 4

Transformation of message flow monitoring information into an executable monitor model

Disclosed is a process for the transformation of message flow monitoring information into an executable monitor model. Message flows can be inter-related with monitoring information and defined using a message flow tool. A process is required to transform the information of multiple flows into a manageable and executable monitor model that could be deployed onto a monitor server. The message flow may have a parent-child relationship or in a nested structure. Each message flow is run as a separate transaction. Special correlation is required to relate different transactions for monitoring purposes and the task is typically too complex to be handled manually. Typically there is no easy to use mechanism to interpret multiple message flows and associated monitoring information for automatic generation of a monitor model. Message flows may also reference data from a large message set. Only relevant schemas should be extracted for use by the monitor model.

A typical user-scenario begins with specification of multiple message flows having different monitoring data. A top message flow may call sub-flows as depicted in Figure 1.

Figure 1

Monitoring data is defined with an event source address and an event payload in the form of an extensible markup language (XML)

p

                      ath language (XPath) expression. Given the message flow tool specifies the flow node monitoring data including the event source address, event name and the event payload, a transformation process can convert these data into a generic form of monitoring information, such as that of a monitoring application descriptor (MAD). Monitoring information defined for the main flow and sub-flows is extracted as required for a nested flow.

1

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

Page 2 of 4

In addition, an XPath expression specified for each message flow event may reference any XML schema definition (XSD) type in a message set XSD. The tool of the disclosed process extracts relevant XSD types and XSD schemas to pass to the monitor model generator.

An overall architecture of a message flow monitoring information exporter is depicted in Figure
2. The dotted rectangle indicates components of the core of the monitor model generation.

Figure 2

The disclosed process of a message flow monitoring information exporter is depicted in Figure 2 begins with a business analyst defining a message flow model, including sub-flows. The business analyst also defines monitoring data, for example, event source address, event name and the event payload. In particular, an event payload can be in the form of an XPath expression referencing a particular XSD element in any message set referenced by the message flow. The transformation from flow monitoring data into monitoring application descriptor first extracts the flow node and monitoring data from the message flow model.

The disclosed process identifies a rel...