Browse Prior Art Database

Using Workflow for Describing SOAP Message Path

IP.com Disclosure Number: IPCOM000031797D
Original Publication Date: 2004-Oct-11
Included in the Prior Art Database: 2004-Oct-11
Document File: 1 page(s) / 4K

Publishing Venue

IBM

Abstract

SOAP messages going from the initial sender to the ultimate receiver can be transmitted via a set of intermediaries. These intermediaries can perform then actions that are applicable to the message, such as storing the message in a message warehouse. The current SOAP specification does not provide a means of specifying the sequence in which these intermediaries are processing the SOAP message. A separate specification, called WS Routing, has been proposed to provide for the specification of the sequence in which these intermediaries are handling the SOAP message. The proposed specification provides just a simple sequence in which these intermediaries processing the SOAP message are to be invoked, a rather restrictive way. It is proposed that a workflow is used to describe the sequence in which intermediaries process the SOAP message.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 70% of the total text.

Page 1 of 1

Using Workflow for Describing SOAP Message Path Using Workflow for Describing SOAP Message PathUsing Workflow for Describing SOAP Message Path Using Workflow for Describing SOAP Message Path

SOAP Messages go from an initial sender to the ultimate receiver through a set of intermediaries. The purpose of the intermediaries is to perform appropriate actions with the message, such as encrypting the message or storing the content of the message in a message warehouse.

    SOAP only specifies that intermediaries are playing a certain role, however does not specify whether a message needs to be processed by intermediaries at all and if so, the sequence in which the message is processed by the individual intermediaries. This is left to the individual application designer and the implementers of the different intermediaries .

    WS-Routing tries to address this problem by describing the entire message path in the SOAP envelope. The message path is the path that the message takes from the initial sender via the various intermediaries to the ultimate receiver . The complete message path is defined in a SOAP header, which is carried along with the actual payload. This provides each intermediary with appropriate information about the next intermediary. Appropriate elements in the header indicate the individual intermediaries.

    WS-Routing only defines a sequence of intermediaries that process the message. It does not provide for the flexibility that is needed in some scenarios . For e...