Messaging connector parameters

Know how to use the messaging connector to send and receive messages through messaging systems like JMS (Java™ Message Service). Here are the key parameters that are involved when configuring or using a messaging connector.

Input parameters

JMSMessage
A document that represents the JMS message to be sent.
  • properties- A document that contains the optional fields added to the message header. The following properties are added to the JMS messages before sending.
    • uuid- A universally unique identifier for the message.
  • body- A document that contains the JMS message body. webMethods Integration supports the following formats for the JMS message body.
    • string- Message body in the form of a string.
    • object- Message body in the form of a serializable object.
    • data- Message body in the form of a document.
    Note:
    • Only one of the mentioned formats can be used to send data.
    • In Workflows, the string and data formats can be used. In flow services, all mentioned formats can be used.

Output Parameters

JMSMessage
A document that contains the message sent to the JMS provider.
  • properties- A Document containing optional fields added to the message header. webMethods Integration adds the following properties to the JMS messages that it sends.
    • uuid- A universally unique identifier for the message assigned by the sender.
  • body- A document that contains the JMS message body. webMethods Integration supports the following formats for the JMS message body.
    • string- Message body in the form of a string.
    • object- Message body in the form of a serializable object.
    • data- Message body in the form of a document.
    Note: This message format can be used for exchanging JMS messages between webMethods Integration and On-premise webMethods Integration Server.