Using MessageRequestor Services
To enable the MessageRequestor service to send a JMS Message to a queue or topic and then wait on a temporary destination for a reply, provide values for the parameters listed below in the service's input signature when configuring the adapter service within a flow service in Designer. You can either map in values from the pipeline, or you can set constant values using the pipeline editor.
Parameter | Description/Action |
JMSMessage | The JMS message object that you want to send to the JMS Destination. Create the JMS Message object using one of the following Adapter for JMS services:  DocumentToTextMessage DocumentToObjectMessage DocumentToMapMessage DocumentToBytesMessage DocumentToStreamMessage |
JMSDestination | The JMS Destination object or the JMS Destination JNDI Name (String). If the adapter connection is configured for a queue, the JMS destination must be a queue. If the adapter connection is configured for a topic, the JMS Destination must be a topic. |
The MessageRequestor service contains the following output signature:
Parameter | Description/Action |
JMSMessage | The JMS message object that is retrieved from the JMS Destination. Convert the document to a JMS message object using one of the following Adapter for JMS services: TextMessageToDocument ObjectMessageToDocument MapMessageToDocument BytesMessageToDocument StreamMessageToDocument |
JMSMessageClass | A String containing the name of the Java class for the JMS message. You can use the value from this parameter to determine which message-to-document service to use to convert the JMS message to a document. |