After your WebSphere business integration system has been installed, you can install additional adapters from the product CD at any time. To do this, insert the product CD, run the installation program, and choose the adapters that you want to install.
This section describes only the installation of the connector's application-specific component. By default, the connector uses the ABAP Extension Module, so you must install the transport files that support that connector module. After you have installed and configured the connector, you must install the ABAP Extension Module. For more information on installing the ABAP Extension Module, see Installing and customizing the ABAP Extension module.
The IBM WebSphere Business Integration Adapter for mySAP.com can be installed on a UNIX or Windows machine. The connector consists of three parts that need to be installed: the connector's application-specific component, SAP's RFC library, and any SAP transport files delivered with the product and required to support the connector.
After you have installed the required connector files, you must download and install the Java Connector (jCO) files. For more information on downloading the jCO files, see "Prerequisites for installation". For more information on installing the jCO files, see "Installing SAP's Java connector (jCO)".
The connector files must be installed on a machine that is capable of acting as an SAP client. By default, the connector JAR files are installed with the integration broker.
To install the connector on a UNIX system, run the Installer for IBM
WebSphere Business Integration Adapter, and select the IBM WebSphere Business
Integration Adapter for mySAP.com. Table 1 lists the files used by the connector that runs in a UNIX
environment.
Table 1. IBM WebSphere Business Integration Adapter for mySAP.com: Files for UNIX
Before you can use the connector, you must configure the connector from the installer's Connector Configuration screen. From this screen:
To install the connector on a Windows system, run Installer for IBM
WebSphere Business Integration Adapter, and select the IBM WebSphere Business
Integration Adapter for mySAP.com. Installer installs standard
files associated with the connector. Table 2 lists the standard files installed in a Windows
environment.
Table 2. IBM WebSphere Business Integration Adapter for mySAP.com: Files for Windows
Directory/filename | Description |
---|---|
connectors\SAP\bapi\client | Directory containing the BAPI Module business object handler files |
connectors\SAP\bapi\server | Directory containing the RFC Server Module business object handler files |
connectors\SAP\dependencies | Directory containing all version-specific transport files |
connectors\SAP\messages | Directory containing the SAPConnector.txt file. |
connectors\SAP\samples | Directory containing sample ABAP objects |
connectors\SAP\utilities | Directory containing the files (cwsapgen.bat and Cwsapgen.jar) and the directory (generatedfiles) for the CWSAPGen utility |
connectors\SAP\CWSAP.jar | Connector class file |
connectors\SAP\start_SAP.bat | Batch file used to start the connector |
repository\SAP | Directory containing the CN_SAP.txt file. |
Installer adds a menu option for the connector's application-specific component to the IBM WebSphere Business Integration Adapters menu (if WMQI is the integration broker) or to the IBM WebSphere InterChange Server menu (if ICS is the integration broker). For a fast way to start the connector, create a shortcut to this component on the desktop.
The IBM WebSphere Business Integration Adapter for mySAP.com requires the use of SAP's Java Connector (jCO). SAP supports jCO for SAP R/3 3.1h and higher. If you have already followed instructions for installing the connector component, you should have already downloaded SAP's Java Connector (jCO) as described in "Prerequisites for installation". If you have not downloaded the jCO, download and unzip it now.
After you have installed the files delivered with SAPODA, copy the following unzipped jCO files into your environment.
Copy the following files to the /connectors/SAP directory:
Copy the following files to the \connectors\SAP directory:
For Windows, the librfc32.dll requires an additional C runtime dll. The C runtime dll required is msvcrt.dll version 5.00.7022 or newer. The dll msvcrt.dll should be copied into C:\WINNT\system32 directory. This dll may already be present and if not, can be found on the Presentation CD that contains the Windows SAPGUI setup in the folder <cddrive>:\GUI\Windows\Win32\system. See SAP OSS note number 0182805 for more information.
You can install and run the connector on a remote machine. Install the integration broker on one machine and the connector on another machine. It is recommended but not required that both machines be on the same subnet. For more information on installing the connector on a remote machine, see he WebSphere Business Integration Adapters Implementation Guide for MQ Integrator, or, for ICS, see the System Installation Guide for UNIX or for Windows.
To enable the integration broker to handle multiple business objects for SAP at the same time, you may want to install and configure multiple connector components for an SAP system and customize each connector to handle specific business objects.
Each connector component can subscribe to certain business objects depending on their type (such as Customer or Purchase Order). Because you can have multiple connectors accessing the same SAP application, each connector can process events and pass them on to the integration broker. In addition, multiple connectors can support multiple business object requests at the same time. This increases throughput and speeds up the transfer of data into and out of the SAP application.
It is recommended that you choose a unique naming convention for each connector component. For example, if you are using two connectors you could name them SAP1_Connector and SAP2_Connector.
To install and set up multiple connector components, do the following:
If you are installing multiple connectors on the same machine, you need only make a copy of the shared library files and rename them. You do not need to install the transports again.