This JBI can be a standalone ESB
or an ESB embedded in the JVM of an application server. In the latter case,
even an EJB component deployed in an application server can function as a
provider or consumer to the ESB, thus further narrowing down the bridge
between traditional J2EE application servers and the relatively new ESB.
??? ??? ???
???
Chapter 2
[ 41 ]
Service Engine (SE): SEs are service providers or service consumers
deployed locally within a JBI environment. They provide the actual business
logic like transformation. Transformation service can be done with the help
of an XSLT engine by using a stylesheet. Another engine may use JCA to give
a data access service, or Business Process Execution Language (BPEL), or
even custom logic to integrate legacy code like that in CICS or mainframe.
Binding Components (BC): BC provide communications protocol support
and they are normally bound to components deployed remotely from the JBI
run time. In fact, nothing prevents a user from defining a binding for a local
service in the case where it closely resembles SE. Thus BC provides remote
access to services for remote service providers and consumers.
Pages:
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86