Application System Adapters

This section provides information about iWay Application System Adapters for iWay Release 6.0.1 Service Manager.

iWay Application System Adapter for MySAP

This section provides information for the iWay Application System Adapter for MySAP for Release 6.0.1 Service Manager.

Resolved Issues

Duplicate IDocs created on disk with SAP inbound IDocs. (51112540)
Extra white space inserted in Flat IDocs. (50502555)
Running two iSM instances with identical configuration details generates a repository does not exist error. (50162518)
East Asian language characters are not displayed correctly. (52552506)

Language Considerations

Proper parsing, interpretation, and display of text in any language requires adherence to language protocols of the SAP JCO, the operating system, and XML markup text.

The Operating system must be configured with a set of files (commonly called a language pack) that contains the character set and fonts for all the characters used by that language. A character set assigns numeric values to symbols (glyphs) used to display characters for the desired language. It is not necessary to set the default of the operating system to the language desired for correct output, but the correct character set and fonts must be present.
An encoding is a method of mapping the numeric values of a character set onto a transmission method. All pathways the document will follow must match the same encoding for correct transmission and receipt. For example, http is a US ASCII. It may be necessary to set the mime encoding for correct transmission as showing in the following code.
```
Content-Type: text/html; charset=EUC-JP
```
The document encoding must match the encoding as specified in the XML "encoding" attribute in the XML header of the document. This means the document must be saved in the character set that matches the attribute. For example, the following text indicates that the document data is serialized according to the rules described in the UTF-8 specification http://tools.ietf.org/html/rfc3629.
```
<?xml version="1.0" encoding="UTF-8" ?> 
```
In non Unicode SAP (MDMP systems) the data length of a character may be longer than the character length permitted in an entry field. For example, an english word "water" uses 1 byte = 1 character = 5, so it fits into a field with length 6. A Japanese word may use multiple bytes to display a similar word, so 2 bytes = 1 character = 10. Following the SAP convention, the word would be truncated at 6 bytes and the remaining 2 characters would not be transmitted. This issue is not resolvable in MDMP and upgrading the SAP system to Unicode is the only solution. Consult the SAP service marketplace notes for more information on this issue. It may also be necessary in MDMP systems to filter IDoc segments to output only certain types of text segments and route them to different translation or encoding pathways.

When using multiple languages through the Remote Function Call, the following issues may arise.

A text cannot be converted from the source code page to the target code page because the corresponding character in the target code page is not available.
The field in the target system is shorter than the field in the source system. This may occur if data from a US is transferred to a multibyte system.

In principle, You can assume that text data has a different length in the sending system than in the receiving system.

If the SAP JCO does not find the corresponding language pack, then proper translation is not performed and the square box glyph is used to represent the missing characters. Question marks delineate encoding errors, if any.

The SAP Event listener does not have encoding as one of the parameters, therefore the encoding defaults to the iSM general encoding found under System, Properties. Since this is a general property, only one encoding can be supported per server instance.