Hi Tim,
Firstly, do you have a particular reason for wanting to use JMS instead of webMethods Messaging? If you use wM Messaging, it all becomes a lot simpler:
- Configure wM Messaging alias in IS admin
- Set the IS document type to be Publishable = true (doc type properties)
- Publish the message using pub.publish:publish
- Subscribe using a wM Messaging trigger
This is much simpler as you get the document directly in the pipeline, you don’t need to create the queue/topic, you don’t need to deal with JNDI and ConnectionFactories.
If you still want to use JMS, then make sure that on the publish side, you map the document to be published to JMSMessage/body/data when calling the pub.jms:send service.
Your triggered service should be set up to use the pub.jms:triggerspec specification.
Then, in that service, map from JMSMessage/body/data to a new document reference (referencing the relevant doc type) in the pipeline output. To do this, add a Map step, then in the Pipeline view, right-click in the Pipeline Out area and add a document reference, selecting the relevant doc type. Give the document a name and then map to it from the JMSMessage/body/data. Note: If you click away before doing the mapping, then the docref you created will disappear.
If this is still not working, then add a call to pub.flow:tracePipeline at the top of the triggered service and then post the output to this thread. It will help determine whether the message has been published correctly.
Hope this help.
#webMethods#Universal-Messaging-Broker#Integration-Server-and-ESB