A Content Enricher can get the customer identification data (customer key)
from the incoming message and retrieve the extra details from a local resource store.
The extra details can now be appended to the original message and then routed to
the target service. The whole setup is shown in the following figure:
Enterprise Integration Patterns in ESB
[ 304 ]
Sample Use Case
The following figure illustrates how various components can be assembled in the JBI
bus for our sample use case:
The sample use case will have following components:
JMS client: This is a normal external JMS client, placing XML messages onto
the JMS Consumer component configured within the ESB.
JMS consumer: This is a servicemix-jms listening on queue "A". Any
incoming messages to this queue will be routed to the next component in the
flow chain which is the Content Enricher.
Content enricher: The Content Enricher router is a servicemix-eip
component. It enriches the original message with additional information. The
enriched message will be placed back in the JMS Provider queue.
Content appender: The Content Appender is a custom transform component.
Pages:
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418