The Unwired Orchestrator design tooling can accept multiple language data if the client machine has the appropriate input methods for each language available. When deploying the tooling data to a server, the server must support the languages used during design. For example, a business process using Japanese character data can be deployed to a server such as Shift_JIS Japanese Windows or EUC_JP UNIX but not to an English server that supports only ASCII characters.
Character data in the incoming messages need not be supported by the system encoding in the server. Any character data in the messages is converted to Unicode inside Unwired Orchestrator regardless of the system encoding used in the server. If you need to deal with multiple language messages, choose a runtime platform that supports all character data, such as UNIX with UTF-8 locale set.
The defaults that the system uses to decode incoming messages are the locale and character set associated with the machine in which the server is running. If non-XML messages are sent from different language regions, the character set and locale must be provided. Use one of the two methods:Set NNOT_MSG_ENCODING and NNOT_MSG_LOCALE in the message header options.
Set NNOT_MSG_ENCODING and NNOT_MSG_LOCALE in the message header options.
Set DEFAULT_ENCODING and DEFAULT_LOCALE transport values of the transport property in Deployment Explorer.
Note: In XML documents, the encoding attribute on the first line provides the character set for the contents so no additional settings need to be made. If the encoding attribute is not available in the XML message, the default is UTF-8.
Use the character set and language information provided through each of the following links to determine the appropriate name values to be associated with messages.
Supported Encoded Character Sets