Adapter environment

Before installing, configuring, and using the adapter, you must understand its environment requirements. This section contains the following topics:

Broker compatibility

This adapter is compatible with the integration broker, InterChange Server Express.

Adapter platforms

In addition to a broker, this adapter requires one of the following operating systems:

Adapter supported software and standards

Adapter dependencies

Prior to installing the connector:

After installing the connector:

Locale-dependent data

The connector has been internationalized so that it can support multi-byte character sets for non-Unicode SAP systems. Note that the information in this section does not apply to Unicode-based SAP systems.

This adapter supports the processing of bidirectional script data for languages such as Arabic, Hebrew, Urdu, Farsi, and Yiddish. To use the bidirectional capacity, you must configure the bidirectional standard properties. For more information, you must configure the bidirectional standard properties. For more information, refer to the standard configuration properties for connectors in Appendix B. Standard configuration properties.

When the connector transfers data from a location that uses one character code set to a location that uses a different code set, it performs character conversion to preserve the meaning of the data.

Note:
The WebSphere BI Station log is available only in English.

The Java runtime environment within the Java Virtual Machine (JVM) represents data in the Unicode character code set. Unicode contains encodings for characters in most known character code sets (both single-byte and multibyte). Most components in the IBM WebSphere business integration system are written in Java. Therefore, when data is transferred between most IBM WebSphere business integration components, there is no need for character conversion.

Because this connector is written in Java, it does not need to convert application data (including data in an IDoc file) written in native encoding. The SAP JCo library converts such application data to Unicode before the connector processes it. Figure 1 illustrates the components involved in data conversion.

Figure 1. Configuring agent properties

To log error and informational messages in the appropriate language and for the appropriate country or territory, configure the Locale standard configuration property for your environment. For more information on these properties, see Appendix B. Standard configuration properties.

Important:
The character code set that SAP applications use for Japanese is SAP-8000. This code set does not support MS932 characters. Also, SJIS maps some characters to non-standard Unicode characters. Therefore, the SAP JCo library cannot handle some characters. If these characters are included in the SAP application or the IBM WebSphere business object, the connector replaces them with the # or ? character. When data contains these characters, it is not processed correctly, and the connector does not report errors.

Copyright IBM Corp. 2004, 2005