Subscription data retrieved from client applications (for example, topics from publishers and subscribers, and content filters from subscribers) and the character data entered through the workbench (for example, message flow names) are stored in the configuration repository. This data is translated from its originating code page to the code page of the process in which the broker or Configuration Manager is running, and then by the database manager to the code page in which the database or databases were created.
To preserve data consistency and integrity, ensure that all this subscription data and workbench character data is originated in a compatible code page to the two code pages to which it is translated. If you do not do so, you might get unpredictable results and lose data.
Data stored in the broker database is not affected in this way.
The restrictions described above do not apply to user data in messages. Ensure that any data in messages generated by your applications is compatible with the code page of any database you access from your message flows.
SQL statements generated as a result of explicit reference to databases within message processing nodes can contain character data that has a variety of sources. For example, the data might have been entered through the workbench, derived from message content, or read from another database. All this data is translated from its originating code page to the code page in which the broker was created, and then by the database manager to the code page in which the database was created. Ensure that these three code pages are compatible to avoid data conversion problems.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac14915_ |