Resolution:
Description:
============
BusinessConnect EDI Protocol 5.2 and above can only generate EDI-X12 documents in ISO-8859-1 (ASCII) and UTF-16 (Unicode) formats.  Some customers have expressed a desire to send EDI-X12 documents using UTF-8 characters so that international characters (such as Japanese or Chinese characters) can be incorporated into their EDI-X12 documents.
    
Environment:
==========
BuinessConnect EDI Protocol 5.3 and 5.4

Resolution:
=========
To generate documents for outbound transport:

1).  For the trading partner in question, create an EZComm protocol definition using BC/1.0/Notify as the operation. Also, create a corresponding BusinessAgreement for the same.

2).  For the trading partner's X12 transport, create an outbound FILE or HTTP transport.  If using a FILE transport, create a directory where the outbound UTF-16 file will be generated.  If using an HTTP transport, set it to the http process starter for the BW project described in the next step.

3).  Create a BW project with either a File poller process starter or an HTTP process  starter that will pick up the UTF-16 file when generated.   Have this process convert the document from UTF-16 to UTF-8 and then send a request to the trading partner via EZComm with the UTF-8 encoded document.

How to get BusienssConnect to generate UTF-8 encoded EDI-X12 documents.