Database Reference
In-Depth Information
Chapter 3. Building the Core - Enterprise
Business Flows
Service Orchestration is one of the terms that is most commonly associated with the Enter-
prise Business Flows framework and SOA implementation in general. At the same time,
Orchestration is one of the two most common compound patterns (the other is ESB) em-
ployed for addressing reoccurring problems related to application integration. In this
chapter, we will discuss these common problems and the ways of mitigating them using
different patterns that are related to Orchestration, and find ways to turn integration into
service collaboration. Not all debated patterns will be related to the Orchestration realm
directly.
However, as long as they are quite universal and applicable to every framework, we will
put them here; this is because the Orchestration layer can be a good demonstration ground
to begin with this exercise. Some basic SOA Suite skills (for 11
g
composites: BPEL, Medi-
ator, and RE) and some Java skills (MDB and JMS) would be useful, as we simply do not
have enough room here to provide a complete technical tutorial. The main focus in this
chapter will be on patterns, ensuring reusability and composability. Therefore, architecting
the agnostic Composition Controllers and subcontrollers will be the most interesting part.
Another reason to start with Orchestration first is that due to the popularity of Oracle BPEL
Process Manager (initially Collaxa and later 10
g
and 11
g
), in the last 9 years, quite a few
enterprises have maintained a considerable amount of orchestrated services with different
degrees of service orientation. It is not too common for an enterprise to start something
from scratch these days (such as the
St. Matthews Hospital
example in
Oracle SOA Suite
11g Handbook
,
Lucas Jellema
,
McGraw-Hill
), practicing a pure top-down approach. Thus,
the patterns related to Service Inventory Analysis and Modeling will be essential for under-
standing the presented example.
Search WWH ::
Custom Search