In previous article, I brief about JMS palettes using text message type. Here in this article, I would explain how to process XML message to EMS queues and topics.
Lets build a EMS Order Publisher and Subscriber Processes, publisher reads the a file directory and parse the xml and send to JMS Queue Sender. Subscriber reads the message and transforms to target format and writes to file system.
Below is the publisher process and configurations of all the activity is shown below. Order Request is published to queue.
Subscribers process for Cab related messages.
Lets build a EMS Order Publisher and Subscriber Processes, publisher reads the a file directory and parse the xml and send to JMS Queue Sender. Subscriber reads the message and transforms to target format and writes to file system.
Below is the publisher process and configurations of all the activity is shown below. Order Request is published to queue.
Below is the subscriber process, which reads the message from Queue and transforms to output format and writes to file system as shown below. Configurations are shown below.
JMS Queue Receiver picks up the order request and transforms it to output format type as shown below.
Now, lets build a EMS Order Publisher and Subscriber Processes, publisher reads the a file directory and parse the xml and send to JMS Queue Sender.Subscriber reads the message and invokes a web services (Cab or Hotel services based on the messages received.) Add JMS properties explicitly to the message we sent to topics and queues.
Here is process, which receives booking request from file directory and publishes to topic before publishing it updates the JMS properties as shown below.
Here are the subscribers, which subscribes based on the Servicetype JMS properties for Hotel. Subscribers process for Cab related messages.
Run and test the project.
The video demonstration is available on the Youtube, here is the embedded video.
No comments:
Post a Comment
Note: only a member of this blog may post a comment.