Get Adobe Flash player
The official site of the project's partner

postheadericon SOA-enT system on-line

Architektura systemu SOA-enT

The concept of the implemented system is based on the SOA (Service Oriented Architecture) paradigm. It works on the principle that the components responsible for performing certain  functions (providing services) are loosely coupled with the remaining elements of the system. This loose coupling is a result of introducing a universal service interface description language. Service interface describes a type of operation performed by a given service by means of defining the conditions that have to be met before the service is performed, as well as the output (the final result) of its execution. Because of this approach, the system becomes open, and allows to add heterogenic services (they can be implemented in different programming languages and on different platforms). The service is like a "black box" for the user. He only knows the description of its interface (the way to use it), and he does not need to know how a given service realizes its functionality. What the user is interested in is the result described in the service interface.

Service servers, independent components, which manage services of one or more types, are responsible for realization of services. Type of service (service category) is described using an abstract interface that defines the type of operation common for a given service category. When a specific service, i.e. an instance of a certain type of service, is created, information about the method of communication with the service (its network address), as well as elements of description of input condition, and the specific result for this particular service are added to the abstract interface.

Task Manager (TM) represents the commissioning party in the system. It is responsible for the interaction with the user, generating the plan to realize the task submitted by the user, its arrangement and execution (by calling pre-arranged services).

The Service Broker is responsible for finding services that are capable of realizing a given intention and obtaining commitments from these services in an automatic, universal way, independent of the area of application. The functionality of the Service Broker is used by Task Manager during the arrangement  of the abstract plan. During the arrangement, abstract types of services are replaced with specific services selected on the basis of commitments collected by the SB. The specific plan to carry out a task specified by the client (business process) is realized by calling services in the pre-arranged order.  A service must register its interface (describing the functions it realizes) with the Service Broker in order to be found, arranged and executed within the frame of business processes realization. Figure above presents the general architecture of the system.

Go to:

Created: Saturday, 08 May 2010 11:57
Last Updated: Sunday, 28 September 2014 15:52