JMS consumer (request queue for client).
Pipeline bridge.
HTTP provider.
External web service.
JMS provider (response queue for client).
As we know, all the components are bound appropriately to the NMR and all the
message exchanges take place through the NMR. The following figure shows the
component architecture:
??? ??? ??? ??? ??? ???
Access Web Services Using the JMS Channel
[ 210 ]
As shown in the above figure, when the client sends a message, the message-flow
through the NMR through various JBI components are marked by numbers in
sequence. You may note the dynamics of the Pipeline component in the previous
figure. Here, the Pipeline will send the input message in an In-Out MEP to the HTTP
Provider destination and then in turn forward the response in an In-Only MEP to the
JMS Provider.
An aspect to notice in the above architecture is that the whole interaction is in a
request-response style from the consumer (client) perspective. However, at the
transport-level we implement this as a combination of a In-Only request and its
corresponding response.
Let us now set up the individual components shown in the technical
architecture figure.
Pages:
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298