IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Adding external software dependencies for SAP

Before you can develop message flows that use WebSphere® Adapters nodes, you must add prerequisite files to the runtime environment.

Before you start:

Ensure that you have the relevant prerequisite files for your SAP system. (For information about the versions of files that IBM® Integration Bus supports, see

IBM Integration Bus Requirements.)

sapidoc3.jar
sapjco3.jar
On Windows:
- sapjco3.dll
On z/OS®, Linux, and UNIX:
- libsapjco3.so

Download these files for your operating system from the external SAP Web site,

SAP Service Marketplace, and save them to a directory, such as C:\SAP_LIB. (On Windows, the directory cannot be a mapped network drive on a remote Windows computer; the directory must be local or on a Storage Area Network (SAN) disk.) You must have an SAPNet account to be able to access this Web site.

On Windows, download the .dll files that come with the SAP JCo download.
On z/OS, Linux, and UNIX, download the .so and .o files that come with the SAP JCo download.

Locating the SAP support files in the runtime environment

To add the SAP prerequisite files to the runtime environment, take the following steps.

On Windows, Linux and UNIX:

Ensure that the broker has started.
Either open the Command Console, or open a Windows command prompt and enter mqsiprofile to initialize the environment.

Enter the following command to display the locations of the prerequisite JAR files and native libraries:

mqsireportproperties IB9NODE -c EISProviders -o AllReportableEntityNames  -r

The following example shows what typically is displayed when you run this command:

ReportableEntityName='' 
	EISProviders 
		JDEdwards=''
			jarsURL='default_Path'
			nativeLibs='default_Path'
		PeopleSoft='' 
			jarsURL='default_Path' 
			nativeLibs='default_Path' 
		SAP='' 
			jarsURL='default_Path' 
			nativeLibs='default_Path' 
		Siebel='' 
			jarsURL='default_Path' 
			nativeLibs='default_Path' 
			siebelPropertiesURL=''
		Twineball='' 
			jarsURL='default_Path' 
			nativeLibs='default_Path'

Set the location of the SAP prerequisite files using the following command:

mqsichangeproperties IB9NODE -c EISProviders -o SAP  -n jarsURL -v C:\SAP_LIB
mqsichangeproperties IB9NODE -c EISProviders -o SAP  -n nativeLibs -v C:\SAP_LIB

To check that the values have been set correctly, run the following command:

mqsireportproperties  IB9NODE -c EISProviders -o SAP -r

The following example shows what is displayed by the mqsireportproperties command.

ReportableEntityName=' '
EISProviders
	SAP=' '
		jarsURL='C:\SAP_LIB'
		nativeLibs='C:\SAP_LIB'

BIP8071I: Successful command completion.

Restart the broker.

On z/OS: Run the mqsireportproperties command by customizing and submitting the BIPCHPR utility. For more information about this utility, see Contents of the broker PDSE.

Locating the SAP support files through the IBM Integration Toolkit

To add the SAP prerequisite files through the IBM Integration Toolkit, take the following steps.

On Windows: When you run the Adapter Connection wizard, you are prompted to specify the paths to the required libraries.
On Linux: Append the directory that contains the SAP libraries to the LD_LIBRARY_PATH environment variable:
```
LD_LIBRARY_PATH=DIRECTORY_CONTAINING_SAP_LIBRARIES:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
```
You must set this variable either for the whole system, or in the same shell or environment from which the IBM Integration Toolkit is launched.

Next: configure the SAP system to work with the adapter

tsap_extdepend.htm |

Last updated Friday, 21 July 2017