For information on installing the adapter, see the discussion of installing from the Adapter Capacity Pack for WebSphere Business Integration Server Express Plus, in the Installation Guide for WebSphere Business Integration Server Express, located in the WebSphere Business Integration Server Express Infocenter at the following site:
http://www.ibm.com/websphere/wbiserverexpress/infocenter
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 connector for mySAP.com connector can be installed on a Linux, OS/400 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 (SAPJCo) files. For more information on downloading the SAPJCo files, see Prerequisites for installation. For more information on installing the SAPJCo files, see Installing SAP's Java Connector (SAPJCo).
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 Linux system, run Adapter Capacity Pack for
WebSphere Business Integration Server Express Plus, and select the connector
for mySAP.com. The Adapter Capacity Pack installs standard files
associated with the connector. Table 1 lists the standard files installed in a Linux
environment.
Table 1. WebSphere Business Integration Adapter: Linux file
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/connector for mySAP.commessages | Directory containing the connector for mySAP.comConnector.txt file |
connectors/SAP/samples | Directory containing sample ABAP objects |
connectors/SAP/CWSAP.jar | Connector class file |
connectors/SAP/start_SAP.sh | Batch file used to start the connector |
repository/SAP | Directory containing the CN_SAPconnector for mySAP.com.txt file |
/lib | Contains the WBIA.jar file |
/bin | Contains the CWConnEvn.shfile |
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 OS/400 system, run Adapter Capacity Pack for
WebSphere Business Integration Server Express Plus, and select the connector
for mySAP.com. The Adapter Capacity Pack installs standard files
associated with the connector. Table 2 lists the standard files installed in a OS/400
environment.
Table 2. WebSphere Business Integration Adapter: OS/400 file
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\messages | Directory containing the SAPConnector.txt file |
connectors\SAP\CWSAP.jar | Connector class file |
connectors\SAP\start_SAP.sh | Batch file used to start the connector |
repository\SAP | Directory containing the CN_SAP.txt and BO_SAPIDocControl.txt files |
\lib | Contains the WBIA.jar file |
\bin | Contains the CWConnEnv.sh file |
To install the connector on a Windows system, run Installer for IBM
WebSphere Business Integration Adapter, and select the connector for
mySAP.com. Installer installs standard files associated with the
connector. Table 3 lists the standard files installed in a Windows
environment.
Table 3. WebSphere Business Integration Adapter: Windows file
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\connector for mySAP.commessages | Directory containing the connector for mySAP.comConnector.txt file |
connectors\SAP\samples | Directory containing sample ABAP objects |
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_SAPconnector for mySAP.com.txt file |
\lib | Contains the WBIA.jar file |
\bin | Contains the CWConnEnv.bat file |
Installer adds a menu option for the connector's application-specific component to the IBM WebSphere Business Integration Server Express adapters menu. For a fast way to start the connector, create a shortcut to this component on the desktop.
The integration broker requires the use of SAP's Java Connector (SAPJCo). If you have already followed instructions for installing the connector component, you should have already downloaded SAP's Java Connector (SAPJCo) as described in Prerequisites for installation. If you have not downloaded the SAPJCo, download and unzip it now.
After you have installed the files delivered with SAPODA, copy the following unzipped SAPJCo files into your environment.
Linux:
From the zipped file, extract the executable jar file (.jar extension) and the runtime libraries.
OS/400:
From the zipped file, extract the executable jar file (.jar extension) and the runtime libraries.
Windows:
From the zip file, extract the executable jar file, (.jar extension) and the runtime libraries (.dll extension). If you have already followed instructions for installing the connector for mySAP.com on the same machine on which you install SAPODA, copy these files from the \connectors\SAP directory to the \ODA\SAP directory. If you install SAPODA on a different machine from the connector, after you unzip the SAPJCo files, copy these four files to the \ODA\SAP directory. For Windows, the librfc32.dll requires one or more C runtime dlls. The C runtime dlls depend on the version of the SAP release being used. Through SAP release 45B, the C runtime dll required is msvcrt.dll version 5.00.7022 or newer. Starting with SAP release 46A, the C runtime dlls required are msvcrt.dll version 6.00.8267.0 or newer and msvcp60.dll version 6.00.8168.0 or newer. The dll or dlls should be copied into the C:\WINNT\system32 directory. This dll or these dlls 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.
You can set your system up to create and run multiple instances of a connector by following the steps below. You must:
You must create a connector directory for each connector instance. This connector directory should be named:
ProductDir\connectors\connectorInstance
If the connector has any connector-specific meta-objects, you must create a meta-object for the connector instance. If you save the meta-object as a file, create this directory and store the file here:
ProductDir\repository\connectorInstance
You can specify the ICS servername as a parameter of startup.bat; an example is start_mySAP4.bat connName ICSName.
/QIBM/UserData/WBIServer43/servername/connectors/connectorInstance
where connectorInstance uniquely identifies the connector instance and where servername is the name of the InterChange Server Express instance with which the connector runs
If the connector has any connector-specific meta-objects, you must create a meta-object for the connector instance. If you save the meta-object as a file, create this directory and store the file here: /QIBM/UserData/WBIServer43/servername/repository/connectorInstance
where servername is the name of the InterChange Server Express instance with which the connector runs
ProductDir/connectors/connectorInstance
where connectorInstance uniquely identifies the connector instance If the connector has any connector-specific meta-objects, you must create a meta-object for the connector instance. If you save the meta-object as a file, create this directory and store the file here: ProductDir/repository/connectorInstance
You can specify the ICS servername as a parameter of connector_manager; an example is connector_manager -start connName ICSName [-cConfigFile].
If the business object definitions for each connector instance do not already exist within the project, you must create them.
\ProductDir\repository\initialConnectorInstance
Any additional files you create should be in the appropriate connector instance subdirectory of \ProductDir\repository
QIBM/UserData/WBIServer43/servername/ repository/initialConnectorInstance
where servername is the name of the InterChange Server Express instance with which the connector runs.
Any additional files you create should be in the appropriate connectorInstance subdirectory of: /QIBM/UserData/WBIServer43/servername/repository
/ProductDir/repository/initialConnectorInstance
Any additional files you create should be in the appropriate connectorInstance subdirectory of /ProductDir/repository
You create a configuration file (connector definition) for the connector instance in Connector Configurator Express. To do so:
To create a startup script:
dirname
(For Linux only.)You must change the start-up script CONJAR from CONJAR=${CONDIR}/CW${CONNAME}.jar to "CONJAR=${CONDIR}/CWmySAP4.jar"
where newmySAP4name is a ten-character name that you use for the job description for your new mySAP4 connector
You can now run both instances of the connector on your integration server at the same time.