Browse Prior Art Database

Solution for the lack of Fork/Join problem in WBI Server Express

IP.com Disclosure Number: IPCOM000132179D
Original Publication Date: 2005-Dec-05
Included in the Prior Art Database: 2005-Dec-05
Document File: 7 page(s) / 181K

Publishing Venue

IBM

Abstract

The solution allows the WebSphere Business Integration (WBI) Server Express (SE) (a.k.a InterChange Server) to support the Fork/Join workflow pattern by providing an architecture, a software pattern, and an implementation for allowing the concurrent execution of workflow activities.

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

Page 1 of 7

Solution for the lack of Fork /Join problem in WBI Server Express

The solution presented herein allows the WebSphere* Business Integration(WBI) Server Express (SE) (a.k.a InterChange Server) to support the Fork/Join workflow pattern. The Fork/Join pattern allows parallel execution of workflow activities. WBI SE uses Collaboration template to describe work flows. WBI SE executes Collaboration's workflow sequentially and has no native support for parallel execution. This solution solves this problem by providing an architecture, a software pattern, and an implementation for allowing the concurrent execution of workflow activities. There is no known solution for this problem on the WBI SE platform. Other Business Integration platforms (Say Microsoft BizTalk**) have native support for the Fork/Join pattern WBI Collaboration has no native suport for the Fork/Join pattern. However, by splitting the workflow into multiple collaborations and adapters and by utilizing the parallel execution environment provided by the WBI Server Express for triggering events, the Fork/Join pattern can be implemented.

    The following figure summarizes the generic Fork/Join solution based on existing WBI components.

Fork Adapter

Fork

Join

There is currently no known pattern, generic architecture, and implementation that support the parallel execution of workflow activities within the WBI SE.

The following section summarizes the basic components of this solution:

Business Objects

Input business object

The business object that triggers the Fork process and contains the input data for the forked processes.

Fork Collaboration

Process Collaboration 1 Process Collaboration N

Join Adapter

Join Collaboration (AND/OR)

[This page contains 2 pictures or other non-text objects]

Page 2 of 7

Result business object

The business object that is the result of the processing done by the forked processes. We assume in this document that the Result business object is from the same type as the Input business object.

Wrapper business object

The business object that wraps the Input business object and the Result business objects. It contains information that is needed for the execution of the Fork process.

The id attribute is the unique identifier of the fork process.

The process_id attribute is the unique identifier of the forked process.

The input attribute is the Input business object.

The result attribute is an array of size NUM_OF_PROCESSES of business objects from the same type as the Result business object. This attribute enables to save the results of each forked process.

Collaboration Templates ForkCollaboration

The collaboration that handles the fork process.

2

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

Page 3 of 7

Properties

The following properties are defined for the collaboration template: NUM_OF_PROCESSES - The number of forked processes.

Ports

Two ports are defined for the collaboration template: The From port: the port that is connected to the originator...