By doing so,
the SOAP formatted messages can be routed through the traditional HTTP channel
through firewalls over the Internet, and also through the messaging channel over the
intranet for access by interdepartmental systems.
For example, you can think of a scenario where an enterprise provides a "Product
Query" service or an "Inventory Update" service. Such services can be accessed by
interdepartmental or LOB systems such as the "Order Entry" system or "Shipping"
system over JMS. If the enterprise wants to expose these services over the firewall
for B2B interaction with other enterprises, they can do so in the SOAP over HTTP
style of interaction. For both these two types of interaction, we don't need to define
two separate services. Instead, using an adapter, the same service can be made
accessible through multiple channels. The web services gateway provided by the
IBM Websphere Application server is a first class example of a web service adapter.
Web Service in the JMS Channel Binding
Sample
We will now look at a complete sample of how to bind a web service using the JMS
channel to ServiceMix.
Pages:
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296