For Acquire NDO mode, the NDO data tree created by the adapter can be encoded in any valid character encoding set supported by core infrastructure version 2.1. The user can also select the encoding of the serialized message by setting the Adapter.Output.Serializer.Encoding key to the desired encoding in the configuration file. Default encoding of the serialized message is slightly different for the e-ADK supported serializers. For NCF messages, the default encoding of the serialized message is the native system encoding. For XML messages, the default encoding of the serialized message is UTF-8.
WARNING!
Transcoding errors do not throw or log exceptions. If a character in the source encoding does not exist in the target encoding, then it is replaced with a fill character.
XML parsers generally support a limited number of supported character encoding sets. Creation of an XML document in an encoding set that is unsupported by the target system will result in an illegible message although the XML is well formed.
