Universal Event Monitor for SOA Workflow

The following figure illustrates the workflow of Universal Event Monitor for SOA.
 
 

Workflow Description

Supported Protocols

Universal Event Monitor for SOA supports synchronous and asynchronous communication for file-based event detection via two protocols: SOAP and JMS.

Synchronous communication requires that the calling party wait for a response from the target application before beginning the next task.

Asynchronous communication allows the calling party to move to the next task without waiting for a response (if there is one) from the target application.

SOAP Protocol

SOAP (Simple Object Access Protocol) is a synchronous protocol for exchanging XML-based messages over computer networks. It is the foundation layer of the web services stack.

For Universal Event Monitor for SOA, the SOAP protocol is used to allow an inbound SOAP message to be sent by any application that supports the SOAP protocol. This inbound message can represent an event and can contain data relevant to the event or the target application.

JMS Protocol

JMS (Java Message Service) defines the standard for reliable Enterprise Messaging and uses both point-to-point (queue-based) and publish / subscribe (topic-based) messaging patterns.

For Universal Event Monitor for SOA, the JMS protocol is used to allow an inbound JMS message to be sent by any application that supports the JMS protocol. This inbound message can represent an event and can contain data relevant to the event or the target application. Unlike a SOAP message, the JMS message is not required to contain data.

Message Exchange Pattern

A Message Exchange Pattern (MEP) describes the pattern of messages required by a communications protocol to establish or use a communication channel.

There are two major types of MEPs:

• Request-response pattern (synchronous)
• One-way pattern (asynchronous)

Universal Event Monitor for SOA supports the one-way (asynchronous) MEP, more commonly referred to as the Listen MEP.

Listen MEP

The Listen MEP represents an asynchronous inbound event initiated by an external application. This operation is a publish only from the external application, meaning that Universal Event Monitor for SOA will not reply to the inbound request. External applications can make use of both the JMS and SOAP protocols for inbound operations.

Currently, Universal Event Monitor for SOA will write the inbound message to a file for processing by Universal Event Monitor.

Logical View of Listen MEP

The following figure illustrates a logical view of the Listen MEP.
 
 

Connectors

The work of transforming the command line and STDIN input to the appropriate protocol message is the responsibility of the connectors that are deployed in the Universal Event Monitor for SOA environment.

A summary of the current connectors follows.

SOAP Connector

The SOAP connector supports inbound operations via the SOAP protocol.

It is a synchronous listener component that supports the following features:

• Supports the SOAP 1.1 specification
• Supports the Listen MEP

JMS Connector

The JMS connector supports inbound operations via the JMS protocol using asynchronous communication.

It supports the following features:

• Supports the JMS 1.1 specification.
• Supports the Listen MEP.
• Supports Queue- and Topic-based operations.
   

Defined Ports

Universal Event Monitor for SOA uses a specific set of ports.