Can the TIBCO EMS server JMSMessageID be reconfigured from the default format (ID:EMS server name.number)to ISO-11578 format (e.g., 503a766d-cbaf-80a1-c27f-22c3ded0f3f0).
Article ID: KB0084614
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Environment:
===========
All versions of TIBCO Enterprise Message Service
Resolution:
==========
Currently there is no way to use ISO-11578 format for the JMS message ID.
EMS clients can specify a variety of common character encoding's for strings in messages. Character encoding for a message applies to strings that appear in any of the following within a message:
• property names and property values
• MapMessage field names and values
• data within the message body
You can add your own property with a unique ID (UUID) for uniquely identifying the message.
Environment:
===========
All versions of TIBCO Enterprise Message Service
Resolution:
==========
Currently there is no way to use ISO-11578 format for the JMS message ID.
EMS clients can specify a variety of common character encoding's for strings in messages. Character encoding for a message applies to strings that appear in any of the following within a message:
• property names and property values
• MapMessage field names and values
• data within the message body
You can add your own property with a unique ID (UUID) for uniquely identifying the message.
Issue/Introduction
Can the TIBCO EMS server JMSMessageID be reconfigured from the default format (ID:EMS server name.number)to ISO-11578 format (e.g., 503a766d-cbaf-80a1-c27f-22c3ded0f3f0).
Feedback
Yes
No
Powered by
