Integration platform
An integration platform is a middleware product or a combination of such products that enable different applications to be connected in a process-oriented manner along the value chain in the sense of Enterprise Application Integration ( EAI ). The term is sometimes used as a synonym for business bus .
Structure and functionality
An integration platform in this sense consists, as shown in the diagram, of at least four components. The lowest level represents the transport of messages or orders. This task is typically performed by classic middleware products such as CORBA implementations (synchronous) or messaging platforms (asynchronous). In order to make the logic of addressing and distribution as flexible as possible, these products usually also contain a message broker that distributes the data to one or more addressees based on address information in the incoming message or request or based on the content. For this purpose, all incoming data from the transport level is forwarded directly to the message broker and the latter returns it to the transport in an addressed manner.
The Business Process Engine finally enables complex business processes to map and automate. To do this, the message broker forwards incoming messages to this engine. There, it is determined whether this message is an event as a trigger ( trigger is defined) of a business process. In this case, an instance of the process is created and started. As a result, the required exchange of messages is also implemented via the platform.
To keep the specification of the integration as flexible as possible, the rules for are Message Broker and process definitions in a repository maintained and ongoing operation of a rule engine ( Engl. : Rules Engine ) in the Message Broker and Business Process Engine interpreted. This repository must be able to version the stored rules and processes, otherwise version conflicts can arise when processes are still running when a version is changed. The Business Process Engine typically also stores the status of the running process instances in the repository .
example
A customer wants to book a trip online. To do this, he more or less precisely specifies his travel requirements such as destination, accommodation, services, price category, etc. This output message initiates a process to search for and book the appropriate trip. On the basis of the criteria, the Business Process Engine initiates search requests with regard to travel options, e. B. several airlines, hotel capacities and other desired services such as rental cars on site. If possible, a list of offers will be created from this information. If the information is not sufficient, an option list is created for the aspects to be specified in accordance with the process definition in order to make it easier for the user to specify. This information is sent back to the internet application, where it is processed and presented accordingly. The process goes into a waiting state until either the user sends further information, which is then evaluated again, or a preset waiting time is exceeded, after which it is assumed that the user has decided not to pursue this request any further.