Using Document-to-Message Conversion Services

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
Message Body	For DocumentToTextMessage, the message body will be a String called TextMessageBody. Map the message data to this field. For DocumentToObjectMessage, the message body will be an Object called ObjectMessageBody. Map the message data object to this field. For DocumentToMapMessage, the message body will be a document called MapMessageBody that contains a set of parameters corresponding to the message body fields you added in step 8 in Configuring Document-to-Message Conversion Services. For DocumentToBytesMessage, the message body will be an Object called BytesMessageBody. Map the message data object to this field. For DocumentToStreamMessage, the message body will be a document called ObjectMessageBody that contains a set of parameters corresponding to the message body fields you added in step 8 in Configuring Document-to-Message Conversion Services.
JMSHeader	This document will contain any JMS Header fields you added in step 9 in Configuring Document-to-Message Conversion Services.
Properties	This document will contain any JMS property fields you added in step 10 in Configuring Document-to-Message Conversion Services.

Parameter	Description/Action
JMSMessageClass	A String containing the name of the Java class for the JMS message.
JMSMessage	The JMS message object to be sent to a JMS Destination. This object can be passed to a MessageProducer or MessageRequestor service.