Before installing, configuring, and using the adapter, you must understand its environment requirements. This section contains the following topics:
This adapter runs with the WebSphere Business Integration Adapter FrameworkV2.6 and requires one of the following:
See Release Notes for any exceptions.
For WebSphere InterChange Server (ICS), see the System Installation Guide for UNIX or for Windows.
For message brokers (WebSphere MQ Integrator Broker, WebSphere MQ Integrator, and WebSphere Business Integration Message Broker), see Implementing Adapters with WebSphere Message Brokers, and the installation documentation for the message broker. Some of this can be found at the following Web site:
http://www.ibm.com/software/integration/mqfamily/library/manualsa/
For WebSphere Application Server, see Implementing Adapters with WebSphere Application Server and the documentation at
In addition to a broker, this adapter requires one of the following operating systems:
The adapter supports SAP applications running on SAP application server version R/3 3.1I.
Prior to installing the connectorIBM WebSphere Business Integration Adapter for mySAP.com:
SAP delivers Support Packages for: Basis, the R/3 application, ABAP, and HR. They provide bug fixes for the ABAP code in the SAP application. Use an updated SAP kernel. The kernel is the executables, written in C++, that carry out transports, interface with the operating system, communicate with the database, and run the system.
For example, if the connector must perform certain SAP business transactions, the connector's account in the SAP application must have the permissions to perform these transactions. You must set the connector-specific configuration properties ApplicationUserName and ApplicationPassword using this account information. For more information on how to set these properties, see Appendix D. Standard configuration properties for connectors.
After installing the connector:
SAP calls their Java API the Java Connector (SAP JCo). The SAP adapter currently supports SAPJCo V.2.1.3. If the SAPJCo version mentioned in this document is not available for download from SAP Service Marketplace, please contact your IBM representative.
SAP JCo pools connections and communicates to the adapter which connection to use to execute the request. All connection properties of the adapter are set in the Connector Configuration file. The JCo.PoolManager manages all configurations for connection pooling in the SAP application.
For details about installing this connector dependency, see Installing the SAP JCo
For details about connector properties, see Configuring the connector, Appendix D. Standard configuration properties for connectors, and Appendix E. Connector-specific configuration properties.
This adapter is compatible with IBM's Common Event Infrastructure, a standard for event management that permits interoperability with other IBM WebSphere event-producing applications. If Common Event Infrastructure support is enabled, events produced by the adapter can be received (or used) by another Common Event Infrastructure-compatible application.
For more information refer to the Common Event Infrastructure appendix in this guide.
This adapter is compatible with the Application Response Measurement application programming interface (API), an API that allows applications to be managed for availability, service level agreements, and capacity planning. An ARM-instrumented application can participate in IBM Tivoli Monitoring for Transaction Performance, allowing collection and review of data concerning transaction metrics.
For more information refer to the Application Response Measurement appendix in this guide.
The connector has been internationalized so that it can support multi-byte character sets for non-Unicode SAP systems. Note that this does not apply to Unicode-based SAP systems.
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.
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.
This adapter supports the processing of bidirectional script data for the Arabic and Hebrew languages when the adapter is run in a Windows environment. Bidirectional processing is not supported in non-Windows environments. 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 D. Standard configuration properties for connectors.