Component used in orchestration:

1.Web service- Consumer and exposer both async and sync, need to design their scehema with
the help of XSD(DTO), and need to design SD! for the exposed web ser"ice, if SD! will not
be designed we can not in"oo#e multiple operation with in a web ser"ice$
2.Mediater: ill be used for routing the re%uest and response$
3.DB Adapter, &sed for wor#ing with only, in"o#ing %uery, procedure, function, 'urther wor#ing
on this D( adapter for replacing )!*S+! with it$
4.BP!"Business process e#ecution $an%ua%e&' &sed for desigining business of web ser"ice
either proxy or ser"ice, ,alidation part, Orchestration of web ser"ices will be done here, -ultiple
operation designing with SD!*().!$().! is a eb ser"ices orchestration language
(.)M* Adapter' &sed for publishing and consuming -essaging, will be used in async web
ser"ice if re%ueired
+.,*B can be also used but it will be prefer to use it only when no orchestration is performed, it
re%uieres to use only at the time of proxy generation and "alidation part o"er proxy web ser"ice$
-.#ception hand$in%' System generated and user defined exception(/eed to analysis)$
0$eb ser"ice security layer (/eed to analysis)
1$S Transaction management (/eed to analysis with web ser"ice component)
*,A Advatan%e over Mannau$ orchestration:
2$3eplacing manual code with SO4 components by which performance will be increased as these
components are highly optimi5ed in respect of performance$
6$7nteranlly eb ser"ice interact with each other with the help of messaging$
8$Ser"ices share schema not the classes$
9$Ser"ice compatibitly is defined based on 3-$
:$.asy to manage complexity, /eed to focus on business$
;$Changes will not impact the consumer$
<$3educes TCO and increase 3O7 on e"ol"ing systems
0$4dd "alue to core in"estments by le"eraging existing assets
1$/ew systems can be built faster for less money because
2=$existing ser"ices can be more easily reused (Chappell)
22$(uilt for flexibility
26$!ong term "alue of interoperability
28$."ery thing will be used as a ser"ice
29$-onitoring of ser"ices is more good as we can chec# state and all component
re%uest*response data inside SO4 with the help of .- Console
2:$>uaranteed Deli"ery?Transactionally persist the messages to a data store before passing the
message onto the ().! orchestration engine$ .ach time, delete the message that was persisted
prior to the pre"ious process$
2;$-essage @istory and 4udit !ogs?4ttach a message history to the message that lists all
applications or components that the message has passed through since origination$
Desi%n Patterns:
rror .ospita$. This pattern pro"ides exception handling as a ser"ice$ To maximi5e process
simplicity and performance, the business processes are designed as simple asynchronous or
e"en shortAli"ed synchronous processes$ hen there is an exception, messages are published to
an error hospital process that then pro"ides the necessary exception management, including
human ser"ices if needed$
-any ser"ice orchestration patterns are implemented in orchestration engines such as Oracle
().! )rocess -anager?
Composite *ervice. Combines the functionality of multiple ser"ices into a composite ser"ice and
ma#es it a"ailable to consumers interested in it as a whole$ ().! supports this by automatically
ma#ing e"ery process a"ailable as a ser"ice that can be used as a building bloc# to build higherA
le"el, compound flows$
,rchestration n%ine. Specifies the control and data flow associated with an orchestration
explicitly, using a standard language such as ().! that can run on an orchestration engine$ The
orchestration engine can pro"ide infrastructure ser"ices such as audit trails, persistence of longA
running flows, common exception handling patterns, and so on$
*ervice Compensation. )ro"ides transactional support in a manner that is aligned with loose
coupling, stateless ser"ices, and longArunning processes$
,rchestration /nstance$ Creates and allows users to independently obser"e and manage
concurrent instances of a business process$
There are a number of design patterns that -onster uses in the architecture of our integration
middleware$
*,A Deve$$oper Bene0iits
2$ SO4Bs donBt replace OO De"elopment, but they extend the reach of the functionality$
6$SO4Bs ma#e components reusable at the business le"el and not the component le"el$
8$4pplication !ocation Transparency
9$!oose Coupling allows flexibility
:$>reater C)otentialD for 3eA&se
;$Thin# Cross )latform 3eA&se
<$De"eloper Eellow )ages of Ser"ices F &DD7
0$Common Ser"ices 'ramewor# lea"es de"elopers to wor# on business logic$ (3outing,
3eliability)
1$ 7ndustry ,iew? )latform 7ndependent &se
2=$ @elps applications e"ol"e o"er time and last
22$ 3ich tools to Design, de"elop, debug, deploy ser"ices