Chapter 6 | Advance Topics | BEA

Integration Patterns

• EIPs (or Enterprise Integration Pattern ) are known design patterns that provide solutions to issues/problems faced during application integration. 
• Major Problems of integration are:

1.  heterogeneous nature of application
2. Varied source of data
3. Continuous changes 

• EIPs are classified in the following categories. Adjacent to these, notations that are used to refer these patterns is also specified.

1. File Transfer (In this mode applications exchange information using files, files are shared at some common location.)
2. Shared database ( Here applications use a common database schema. )
3. Remote Procedure Invocation (In this an application exposes its functionality using interfaces, the caller needs to be aware of those and invokes them using stubs.)
4. Messaging (An entity mediates between applications that want to exchange data. It does the job of accepting messages from producers and then delivering to the consumers. Messaging helps to achieve loose coupling while integrating applications. It isolates the connecting applications from API changes/upgrades that happens over time.)

For more details, visit: Integration Pattern

Service-oriented integration

• Service-oriented integration is the mechanism to expose existing sources of data, functionality, and process so that those sources can be readily consumed by a composite application.
• The primary goal of service-oriented integration is to better leverage existing systems within the IT environment by applying service-oriented principles
• Benefits of SOI :

1. Promotes reusability
2. Integrate once, connect many  ( Each system is integrated once into the service bus, rather than many time for each point-to-point connection )
3. Flexibility ( Multiple services can be easily constructed from the integration of existing applications )

Service choreography and Orchestration

• Service choreography and orchestrations are two flips of the same coin.
•  On one hand, in service choreographies the logic of the message-based interactions among the participants is specified from a global perspective. In service orchestration, on the other hand, the logic is specified from the local point of view of one single participant, called the orchestrator.

• The choreography describes the interactions between multiple services, where as orchestration represents control from one party's perspective. This means that a choreography differs from an orchestration with respect to where the logic that controls the interactions between the services involved should reside.

Business Process Model and Notation (BPMN)

- Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes in a business process model.

For more details : BPMN Tutorial