Resolution:
Description:
============
When sending the RosettaNet message including special Latin-1 characters (such as ñ) to a trading partner, the host gets the exception ACK “signature verification error" returned by the trading partner. After checking the message that the trading partner received, you will find that some special Latin-1 characters are changed (i.e. “ñ” on the host side may become “?” on the trading partner side).

Environment:
============
ALL

Resolution:
===========
Set the MIME Content Transfer Encoding as base64 instead of 7bit under the Admin GUI -> BusinessConnect > Participants -> &ltTrading Partner name> -> Protocol -> RosettaNet -> RNIF 2.0 Settings.

The Latin-1 character belongs to the extended ASCII (ISO-8859-1) character set.  By default, BusinessConnect RosettaNet uses 7-bit as the content-transfer-encoding to transfer the payload. If the trading partner receives the RosettaNet message and decodes it based on the 7-bit format, the message will  not be decoded correctly (ñ ->?) so the digest calculation will be incorrect for the payload and signature followed by a signature verification error.  Setting the content-transfer-encoding to base64 will correct this issue.

BusinessConnect receives a "Signature Verification Error" when sending a message including Latin-1 characters to a trading partner.