Deliverable D5.1: Specification of Components for the Service Bus Sub-system

Abstract

This report presents revised descriptions of system managers (related to the system’s backend) from a designer’s point of view. The revision is based on the selection of third-party software packages to be reused within the project and the incorporation of these packages into the architecture of the system. The selection of software packages is documented in the report. The descriptions of system managers have been revised in order to incorporate the selected software and to meet additional constraints imposed by the selected packages on architecture and functionality of system managers. In addition, a plan and strategy for dealing with testing and meeting performance and scalability requirements are presented as well.

The report represents a basis document providing developers with enough information enabling them to start implementation activities on the Service Bus subsystem.  

The presented report is one part in a series of documents describing a system to be designed and implemented within the SPIKE project. This report is a revised description of those main system components which are related to the Service Bus subsystem (basically forming the system’s backend) – it outlines revised ideas of a group of the project developer partners on what functionality the SPIKE backend is going to provide and how considering the internal structure of system managers.

The deliverable updates a part of the report on functionality of system managers [D3.2] and extends it into a more technical description of the system's components to be provided in the upcoming project phases. It is strongly related to the specification of components for Portal system [D4.1] as well as the underlying security architecture [D7.1] – this trinity of reports represents a starting point for implementation activities.

 The aim of the report is to transform ideas on system managers from an analyst’s point of view into a designer’s point of view. This transformation enriches pure functional approach with information on incorporating reusable software packages into the structure of backend system managers. This enrichment has implied also the revision of the description of the managers – as a reaction to possibilities and additional constraints accompanying the usage of third-party software packages.

The selection of software packages was performed as a two-step process. The first step was based on information from the state of the art analysis (properly updated) and resulted in a pre-selection of a few alternatives. In order to compare those alternatives, some additional selection criteria (specific for a particular software category) have been defined and used to select packages to reuse. Developer partners have selected the following packages: Apache ODE as a JBI compatible BPEL engine (compliant with Intalio Tempo selected in [D4.1]), Apache ServiceMix as a JBI compliant ESB, WSMX as an environment for web service execution, and WSML based semantic infrastructure (wsmo4j as a Java API, WSML2Reasoner and IRIS as a reasoning engine, and ORDI as a repository).

Based on the selection, the description of backend system managers has been revised and updated. The following managers have been included in the report:

Communication Manager, Content Manager, Interface Manager, Notification Manager, Process Manager, Search Manager, Semantic Manager, Service Manager.

The description update accommodates possible use of the selected software packages to provide functionality planned for particular managers as well as changes in functionality offered by the managers (to support selected packages – the managers are expected to be implemented in the form of JBI components e.g. JBI service engines and/or JBI binding components). The revised description is provided on two levels:

Functionality level – which functionality is offered by selected packages, which functionality requires extension/modification of the packages, which functionality should be implemented from scratch, and which functionality is not necessary any more. 

Interface level – a high level manager’s interface reflecting changes on functionality level. 

You can download a short version of this document here:

D.5.1. Specification of Components for the Service Bus Sub-system

In order to obtain the full content of this document, please use the contact form below: