Installing the connector component

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.

Installing on a Linux system

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:

Note:
For more information on installing the connector component, refer to the System Installation Guide for Linux.

Installing on a OS/400 system

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

Installing on a Windows system

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.

Installing SAP's Java Connector (SAPJCo)

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.

Installing connectors on remote machines

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.

Creating multiple connector instances

Note:
When you create an additional instance of this adapter (or any adapter that is supplied with WebSphere Business Integration Server Express Plus), that instance of the adapter will be counted as a separate adapter by the licensing function that limits the total number of adapters that can be deployed.

You can set your system up to create and run multiple instances of a connector by following the steps below. You must:

Create a new directory

You must create a connector directory for each connector instance. This connector directory should be named:

Create business object definitions

If the business object definitions for each connector instance do not already exist within the project, you must create them.

  1. If you need to modify business object definitions that are associated with the initial connector, copy the appropriate files and use Business Object Designer Express to import them. You can copy any of the files for the initial connector. Just rename them if you make changes to them.
  2. Files for the initial connector should reside in the appropriate directory:

Create a connector definition

You create a configuration file (connector definition) for the connector instance in Connector Configurator Express. To do so:

  1. Copy the initial connector's configuration file (connector definition) and rename it.
  2. Make sure each connector instance correctly lists its supported business objects (and any associated meta-objects).
  3. Customize any connector properties as appropriate.

Create a start-up script

To create a startup script:

  1. Copy the initial connector's startup script and name it to include the name of the connector directory:

    dirname

    (For Linux only.)You must change the start-up script CONJAR from CONJAR=${CONDIR}/CW${CONNAME}.jar to "CONJAR=${CONDIR}/CWmySAP4.jar"

  2. Put this startup script in the connector directory you created in Create a new directory.
  3. (For Windows only.) Create a startup script shortcut.
  4. (For Windows only.) Copy the initial connector's shortcut text and change the name of the initial connector (in the command line) to match the name of the new connector instance.
  5. (For OS/400 only.) Create a job description for the connector using the information below: CRTDUPOBJ OBJ(QWBISAPC) FROMLIB(QWBISVR43) OBJTYPE(*JOBD) TOLIB(QWBISVR43) NEWOBJ(newmySAP4name)

    where newmySAP4name is a ten-character name that you use for the job description for your new mySAP4 connector

  6. (For OS/400 only.) Add the new connector to the Console. For information about the Console, refer to the online help provided with the Console for OS/400.

You can now run both instances of the connector on your integration server at the same time.

Copyright IBM Corp. 2004