Summary
Enterprise Integration Patterns (EIP) help in solving recurring problems faced in the integration of enterprise applications. This article introduces the Claim Check – one of the Enterprise Integration patterns in the context of SAP NetWeaver Process Orchestration.
Applies to
SAP NetWeaver Process Orchestration EhP1 for SAP NetWeaver 7.3 SP5
Authors
Abdul-Gafoor Mohamed & Prashant Gautam
Product Management, SAP NetWeaver BPM, SAP Labs
Enterprise Application Integration (EAI) is an integration framework composed of a collection of technologies and services that form a middleware, enabling the integration of systems and applications across an enterprise.[1] A twenty-first century enterprise typically consists of tons of distributed applications, varying percentages of which may be homegrown, acquired, legacy or even a combination of these.
Enterprise Integration Patterns (EIP) are design patterns that help in solving recurring problems faced in the integration of enterprise applications. The Claim Check helps address this question:
“How can we reduce the data volume of a message sent across the system without sacrificing information content?”[2] |
Let us consider an example. A mattress manufacturer SnooZ, has a manufacturing unit(factory) in Turkey, with hundreds of outlets in Europe where customers can walk-in and experience a variety of mattresses. There are different models of mattresses based on coil strength, fibres – natural and synthetic – and a few other features.
Each customer that walks into a SnooZ outlet can try out the available mattresses and order a customized one with the help of the sales staff at the outlet. The sales staff submits an order into the system, which generates a delivery date printed on the order receipt. These orders are aggregated and submitted to the factory thrice a week. SnooZ wants to achieve customer satisfaction by promising a delivery to the customer within three weeks of the order date.
Figure 1. An example illustrating the Claim Check pattern
The Claim Check is a message transformation pattern that helps in reducing the payload of a message that flows through a system. Unlike a Content Filter, the complete message will need to be restored later on, and that requires a key (the Claim Check) to be persisted to facilitate this retrieval.
A typical Claim Check integration scenario has the following steps:
In this example, the order details, including the customer information, shipment details, mattress specifications are entered into SnooZ's Business System S1 which generates a message to SAP NetWeaver PI (AEX). The message payload is persisted and the message id (the Claim Check) is passed to SAP NetWeaver BPM (Inbound[3]). The BPM process awaits the collection of all orders for each accumulation during the week.
The BPM process retrieves the details of each order from the data store and sends it to the factory to manufacture the mattresses. A consolidated message for the orders entering the manufacturing phase is sent to the Business System S1 through PI.
Figure 2. An integration scenario for the Claim Check pattern
As depicted in Figure 2, we are dealing with these two integration configurations:
Figure 3. A generic SAP Process Orchestration scenario sequence
The Integration Flows have to be created and activated using the same interfaces that were used in the Business Process. The generic scenario referenced above applies to most Enterprise Integration patterns.
Note: Only XI 3.0 compatible stateless interfaces are supported.
Prerequisites
Figure 4. A Claim Check scenario modeled in SAP NetWeaver BPM
The Process Model for a Claim Check scenario is shown in Figure 4. The steps for modeling the process are enumerated below:
Notes:
[1] Enterprise Application Integration, Wikipedia
[2] Gregor Hohpe & Bobby Woolf, Enterprise Integration Patterns. 2003
[3] Inbound and Outbound are terms used with reference to the application, in this case SAP NetWeaver BPM.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
35 | |
25 | |
14 | |
13 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 |