The IEP engine internally uses a database engine like
Java DB for business event processing.
??? ??? ??? ???
Chapter 8
[ 163 ]
One of the caveats though is that the IEP Service Engine can enumerate events
reaching that particular JBI container to which it is bound. In Chapter 3 on Service
Engines, we discussed various Service Engines supported by the JBI container. IEP
Service Engine, which is one among them, can work with all of the other Service
Engines including BPEL Service Engine, XSLT Service Engine, and other Binding
Components discussed in Chapter 4 on Binding Components.
Client
JBI Message
Router
HTTP/SOAP Binding
Component
Application Server Bridge
Application Server
Java EE Service
Engine
BPEL
Service Engine
JBI Runtime Environment
The figure above depicts the JBI Runtime and IEP Service Engine interaction. This
is in no way different to how the lifecycle of the Service Engines are controlled by
the JBI container (at least for the developer). The IEP runtime component obtains
data via the HTTP/SOAP Binding Component and provides data through the
File Binding Component (For more information on Binding Components, refer to
Chapter 4). The IEP runtime component provides the physical connectivity between
the JBI Message Router in the JBI Runtime and external SMTP clients and servers.
Pages:
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153