|
|
Services
ENTERPRISE SERVICE BUS
The Enterprise Service Bus is a distributed solution integrating the IT systems of a company. It binds various IT resources into a uniform, service‑oriented model, based on exchanging XML messages, and it ensures communication between them by means of infallible message‑oriented middleware, the messaging bus.
Main features of ESB include:
- advanced message routing – the ESB is responsible for finding the system that performs a given service. It limits the number of integrations between the systems and allows for a free, but at the same time structured modification of the already existing integrations, making it possible to add new services offered by individual systems.
- protocol conversion – the ESB provides mechanisms allowing for binding services implementing different protocols, which eliminates the problem of the way a service just made accessible will be invoked by other systems.
- transformation and extension of messages – the ESB makes it possible to modify messages between the parties, including enriching the messages with additional information or even building new messages on the basis of data from several sources. It allows for creating new services and re‑using the existing ones.
- service register – the ESB stores and makes accessible the information on the services and interfaces available through the platform. Such knowledge facilitates the design and development of system functionalities, as well as the re‑use of existing resources.
- service access control – the ESB provides a unique, coherent system for managing access to services. It eliminates the redundancy of such functionality in the other systems.
- central monitoring – the ESB allows for controlling in one location whether all the services function properly, which results in a faster response to problems. It can also provide information on the intensity and the way of using various services, a function on which the business activity monitoring solution (BAM) is based.
A proper use of the ESB is a foundation for developing service‑oriented architecture (SOA) while limiting the interference with the existing systems to the minimum.
|
SERVICE ORCHESTRATION ENGINE
The Service Orchestration Engine (SOE) is a tool for integrating many separate services into a formally defined, by means of Business Process Execution Language (BPEL), business process. This solution allows for an automated performance of services, their coordination and management.
The SOE allows for:
- creating services – the SOE makes it possible to develop new services tailored to the needs of process automation basing on the functionality of the existing applications.
- long‑running transactions support – BPEL’s compensation mechanism allows for maintaining coherence of the process and its data even for processes significantly extended over time.
- asynchrony of processes – the SOE can accept a request to invoke synchronous operations, and to inform on their completion without withholding the super‑ordinate business process. It also ensures mechanisms for developing ways of handling non‑standard situations, such as retrying or invoking notification service in case of an error.
- process monitoring – the solution provides built‑in mechanisms ensuring consistent access to the status of processes of different types.
The SOE constitutes a link between service‑oriented architecture and business process management. In the latter area it functions as a process engine/manager and may be used to conduct business processes involving also the human workflow.
|
As regards ESB and SOE, we base on solutions available on the open‑license basis. They hold the lead in their category. It applies especially to standards of compliance, as for open‑source enterprise solutions it is the standard, and not the organisation, that constitutes the binding element in the process of creating software.
We offer solutions that in terms of functionality and stability outclass the dedicated software that could be developed in a short period of time.
The open source code enables us to tailor the software to the customer’s needs, and to react to errors fast. The avoidance of the vendor lock‑in situation creates a positive atmosphere in the relationships with our customers, since we build our advantage over the competition not by means of a licensing policy, but on excellent competencies that we gain while creating open‑source solutions.
|
|
