In this section: |
If you are using an SAP server that supports unicode, the adapter must also be configured for unicode. With this configuration, no character conversion tables are required.
If, however, you are using an older SAP server that does not support unicode the following information applies.
SAP, as well as adapters, can be installed on various platforms. If SAP is installed on a platform that uses a code page or character set different from the adapter platform, two character conversion tables must be generated to translate the different character sets, one for each direction of data flow.
For example, SAP is installed on an IBM i EBCDIC machine and the Adapter for SAP is installed on an Intel Windows ASCII machine. If a request is going from the server to SAP, an ASCII to EBCDIC translation is required. If SAP is sending data back to the Adapter for SAP, an EBCDIC to ASCII translation is required. This section describes how to create conversion tables and where they must reside.
How to: |
SAP provides a transaction, SM59, to generate conversion tables for RFC-based applications such as the Adapter for SAP. Once these tables are created, they must be copied to the adapter.
If you did not specify a unique file name, the default file name of the newly created conversion table will contain the source and target code page values. For example, if you specified a source code page of 0102 (IBM i for some CUAs) and a target code page of 1101 (7 bit USA ASCII pur), the default file name is 01021101.cdp. This is your IBM i (EBCDIC) to ASCII conversion table file.
It is now necessary to create another conversion table file for translating code pages in the opposite direction.
Continuing with previous example, you should have a source code page of 1101 and a target code page of 0102, resulting in a default file name of 11010102.cdp. This is your ASCII to IBM i (EBCDIC) conversion table file.
Note: If a unique file name was used for the first conversion table, be sure you specify a unique file name for the second conversion table.
Once these conversion table files are created, you can download them from the SAP application server directory to the server configuration ETC directory. Use SAP transaction AL11 to browse and download the two conversion table files to a local file on the desktop or Windows machine where the server is installed. Note that SAP GUI is required on the machine to which you are downloading the conversion table files. The following window represents transaction AL11.
A dialog box displays prompting on a format for the transfer file.
Directory /tmp Name: 01021102.CDP -----------------------------------------------
After the edits have been made, configure the server with the Adapter for SAP. Once the adapter is configured, the conversion table files must be moved to the server EDAHOME ETC directory. Make sure both conversion table files are moved.
Traces are enabled from the Web Console. Use the Custom option and select one of the following:
where:
Indicates the trace level. Currently supported trace levels are:
You may also run a diagnostic trace from the SAP system by running transaction ST05 (Performance Trace). See your SAP system administrator for details.
iWay Software |