webMethods step by step JMS Adapter service scenarios
Task: JMS Adapter Scenarios
Platform: webMethods 6.1
Understanding JMS Terminology
An implementation of the JMS interface for a Message Oriented Middleware (MOM). Providers are implemented as either a Java JMS implementation or an adapter to a non-Java MOM.
An application or process that produces and/or receives messages.
A JMS client that creates and sends messages.
A JMS client that receives messages.
An object that contains the data being transferred between JMS clients.
A staging area that contains messages that have been sent and are waiting to be read. Note that, contrary to what the namequeue suggests, messages don't have to be delivered in the order sent. A JMS queue only guarantees that each message is processed only once.
A distribution mechanism for publishing messages that are delivered to multiple subscribers.
PRODUCER SCENARIO : [ For sending messages or data to Queues ]
Map pipe out
Queue name : look 4 jms
Data : testingData (any data)
Create a adapter service ( jms adapter document to message), drag and drop it here
Data ------ text message body
Create a adapter service ( jms adapter message producer template), drag and drop it here
Queue ----- jms destination
Jms message ------ jms message
CONSUMER SCENARIO : [ For getting the data or messages which are sent by the producer from the queue]
Map pipe out
Queue Ã look 4 vicky
Create a adapter service ( jms adapter message consumer templat ), drag and drop it here
Queue Ã jms destination
Create a adapter service ( jms adapter text or message to docuent)
Jms message ------- jms message
Sample . Io. Test . write to file
Text message body ------ file content
------- file name : path
------- over write flag : overwrite.