SOA Integrataion

With the widespread use of service-oriented architecture (SOA), the integration of different IT systems has gained a new relevance. The era of isolated business information systems—so-called silos or stove-pipe architectures—is finally over. It is increasingly rare to find applications developed for a specific purpose that do not need to exchange information with other systems. Furthermore, SOA is becoming more and more widely accepted as a standard architecture. Nearly all organizations and vendors are designing or implementing applications with SOA capability. SOA represents an end-to-end approach to the IT system landscape as the support function for business processes. Because of SOA, functions provided by individual systems are now available in a single standardized form throughout organizations, and even outside their corporate boundaries. In addition, SOA is finally offering mechanisms that put the focus on existing systems, and make it possible to continue to use them. Smart integration mechanisms are needed to allow existing systems, as well as the functionality provided by individual applications, to be brought together into a new fully functioning whole. For this reason, it is essential to transform the abstract concept of integration into concrete, clearly structured, and practical implementation variants.

This book is available for purchase at packtpub.com

Read "Service-Oriented Architecture: An Integration Blueprint" Book Review

1. Service-Oriented Architecture - an Integration Blueprint Author: Packt Publishing

   Service-Oriented Architecture -  An Integration Blueprint The Trivadis Integration Architecture Blueprint indicates how integration architectures can be implemented in practice. It achieves this by representing common integration approaches such as Enterprise Application Integration EAI ; Extract Transform and Load ETL ; event-driven architecture

2. SOA Integration - Integration Architecture Blueprint Author: Packt Publishing

   The Trivadis Integration Architecture Blueprint specifies the building blocks needed for the effective implementation of integration solutions. It ensures consistent quality in the implementation of integration strategies as a result of a simple tried-and-tested structure and the use of familiar integration patterns Hohpe Wolf 2004 . Standards

3. SOA Integration - Structuring the Integration Blueprint Author: Packt Publishing

   The following diagram is an overview of the Trivadis Integration Architecture Blueprint. It makes a distinction between the application and information view and the integration view. The application and information view consists of external systems which are to be connected together by an integration solution. These are source or target entities

4. SOA Integration - 4 Implementation Scenarios Author: Packt Publishing

   Having understood the structure of the blueprint covered in Chapter 3 Integration Architecture Blueprint this chapter will use individual scenarios to illustrate how the business pattern can be implemented using the Integration Architecture Blueprint. The scenarios shown in this chapter have been deliberately designed to be independent of specific

5. SOA Integration - Implementing the Process Integration Business Pattern Author: Packt Publishing

   In the scenario shown in the following diagram the process integration business pattern is implemented using BPEL. Trigger An application places a message in the queue. Primary flow The message is extracted from the queue through JMS and a corresponding JMS adapter. . A new instance of the BPEL integration process is started

6. SOA Integration - Variant with Externalized Business Rules Author: Packt Publishing

   Variant with externalized business rules in a rule engine A variant of the previous scenario has the business rules externalized in a rule engine in order to simplify the condition logic in the integration process. This corresponds to the external business rules variant of the process integration business pattern and is shown in the form of a scenario

7. SOA Integration - Variant with Batch-Driven Integration Process Author: Packt Publishing

   In this variant the integration process is initiated by a time-based event. In this case a job scheduler added before the BPEL process triggers an event at a specified time which starts the process instance. The process is started by the scheduler via a web service call. The following diagram shows the scenario Trigger The job scheduler

8. SOA Integration - Implementing the Workflow Business Pattern Author: Packt Publishing

   In this scenario additional user interaction is added to the integration process scenario. As a result the integration process is no longer fully automated. It is interrupted at a specific point by interaction with the end user for example to obtain confirmation for a certain procedure. This scenario is shown in the image below. Trigger An

9. SOA Integration - Modernizing an Integration Solution Author: Packt Publishing

   This section uses an example to illustrate how an existing integration solution that has grown over time can be modernized using SOA methods and the scenarios from the previous sections. The example is a simplified version of a specific customer project in which an existing solution was modernized with the help of SOA. The task of the integration

10. SOA Integration - Sending New Orders Author: Packt Publishing

    Trigger The job scheduler triggers an event every 30 minutes for each external system that has to be integrated. Flow The event triggered by the job scheduler starts a shell script which is responsible for part of the orchestration. . The shell script first starts a PL SQL procedure that creates the files or writes the information

11. SOA Integration - Evaluation of the Existing Solution Author: Packt Publishing

    By evaluating the existing solution we came to the following conclusions This is an integration solution that has grown up over time using a wide variety of different technologies. . . A batch solution which does not allow real-time integration or which makes this very difficult. . Exchanging information in files

12. SOA Integration - Modernizing Author: Packt Publishing

    Modernizing— Integration with SOA The main objective of the modernization process from a business perspective is the realtime integration of orders. From a technical standpoint there are other objectives including the continued use of the batch mode through file connections. This means that the new solution must completely replace the old