JMS protocol
Decision Server Insights can receive and send events in the form of JMS text messages or JMS bytes messages. The messaging provider can be either WebSphere® MQ or WebSphere Application Server.
JMS inbound message format and encoding
| Message format (from binding) | Message type | Message content | Character encoding |
|---|---|---|---|
| application/xml or text/xml | TextMessage | Message text parsed as XML | As presented by the messaging provider. The encoding specified in the XML directive is ignored. |
| BytesMessage | Message bytes parsed as XML | If present, the JMS_IBM_Character_Set message property is authoritative. Otherwise, the encoding specified in the XML directive is used. |
For more information about the JMS_IBM_Character_Set message property, see JMS client message conversion and encoding.
JMS outbound message format and encoding
| Message format (from binding) | Message type | Message content | Character encoding |
|---|---|---|---|
| application/xml or text/xml | TextMessage | Message text contains XML content. The encoding UTF-8 is specified in XML directive. | The message includes a JMS_IBM_Character_Set message property with the value, UTF-8. |
| BytesMessage | Message bytes contain XML content using in UTF-8 encoding. The encoding is specified in XML directive. | The message includes a JMS_IBM_Character_Set message property with the value, UTF-8. |
By default, the outbound JMS message is a TextMessage with the JMS delivery mode PERSISTENT. These settings can be customized for individual outbound JMS endpoints by using advanced properties.