Introduction

Universal Connector for SAP requires the SAP NW (NetWeaver) RFC libraries to run. Before executing Universal Connector for SAP, you must first install the appropriate SAP NW RFC Libraries for the platform on which the connector agent is installed.

Download

To acquire the SAP libraries, access the SAP Service Marketplace and download the appropriate package for your platform:

https://launchpad.support.sap.com/#/softwarecenter/template/products/%20_APP=00200682500000001943&_EVENT=DISPHIER&HEADER=Y&FUNCTIONBAR=N&EVENT=TREE&NE=NAVIGATE&ENR=01200314690100002214&V=MAINT&TA=ACTUAL&PAGE=SEARCH/SAP%20NW%20RFC%20SDK

Note

In order to extract the downloaded SAP NW RFC package, you must use the SAPCAR executable. That utility program can be found here:

https://support.sap.com/software/patches/a-z-index.html

In order to download products from the SAP Service Marketplace you will need an SAP S-User ID with the "Download Software" authorization, which you can request via your company's SAP user administrator.

Install

Once the appropriate package has been downloaded, it can be extracted using the SAPCAR utility. The command line to extract an SAP NW RFC package is basically the same on all platforms. The only difference is the name of the SAP NW RFC package. The following is a sample command line to extract the SAP NW RFC package and its resulting output:

C:\tmp\sap>sapcar -xvf NWRFC_35-20004568.SAR
SAPCAR: processing archive NWRFC_35-20004568.SAR (version 2.01)
x nwrfcsdk
x nwrfcsdk/bin
x nwrfcsdk/bin/rfcexec.exe
x nwrfcsdk/bin/startrfc.exe
x nwrfcsdk/demo
x nwrfcsdk/demo/companyClient.c
x nwrfcsdk/demo/readme.txt
x nwrfcsdk/demo/rfcexec.cpp
x nwrfcsdk/demo/rfcexec.h
x nwrfcsdk/demo/sapnwrfc.ini
x nwrfcsdk/demo/sflightClient.c
x nwrfcsdk/demo/sso2sample.c
x nwrfcsdk/demo/startrfc.cpp
x nwrfcsdk/demo/startrfc.h
x nwrfcsdk/demo/stfcDeepTableServer.c
x nwrfcsdk/doc
x nwrfcsdk/include
x nwrfcsdk/include/sapdecf.h
x nwrfcsdk/include/sapnwrfc.h
x nwrfcsdk/include/sapuc.h
x nwrfcsdk/include/sapucx.h
x nwrfcsdk/lib
x nwrfcsdk/lib/icudt34.dll
x nwrfcsdk/lib/icuin34.dll
x nwrfcsdk/lib/icuuc34.dll
x nwrfcsdk/lib/libicudecnumber.dll
x nwrfcsdk/lib/libsapucum.dll
x nwrfcsdk/lib/libsapucum.lib
x nwrfcsdk/lib/sapdecfICUlib.lib
x nwrfcsdk/lib/sapnwrfc.dll
x nwrfcsdk/lib/sapnwrfc.lib
x SIGNATURE.SMF
SAPCAR: 32 file(s) extracted

Windows Install

From the extracted SAP NW RFC library, the dll files located in nwrfcsdk/lib/ must be placed in a directory path that is listed in the environment variable Path.

This can be done by adjusting the Path environment variable to include the nwrfcsdk/lib/ path or by moving the dll files from the SAP NW RFC SDK archive to a location that already exists in the Path.

Note

It is sufficient to place the SAP NW RFC *.dll files in the Universal Connector's bin directory. That path for a typical Windows install is C:\Program Files\Universal\USap\bin.

NetWeaver RFC LIbrary Dependencies

The runtime dependencies form the SAP NetWeaver RFC libraries will likely differ from Universal Agent dependencies. One known issue is that the NW RFC 750 libraries require a different version of the Microsoft Visual C++ runtime libraries than the required for the Universal Agent. If the runtime dependencies for those libraries are not available on your Agent system, attempts to run USAP will fail. To review runtime requirements for the NetWeaver RFC SDK version 750, refer to the information on this page.

UNIX Install

From the extracted SAP NW RFC library, the shared library files located in nwrfcsdk/lib/ must be placed in a directory path that is listed in the environment variable LD_LIBRARY_PATH.

This can be done by adjusting the LD_LIBRARY_PATH environment variable to include the nwrfcsdk/lib/ path or by moving the shared library files from the SAP NW RFC SDK archive to a location that already exists in LD_LIBRARY_PATH.

Preparation of the RFC libraries for Linux

Step 1	Download the appropriate tar file for the target platform: `SAP_NW_RFC_Lin_x64.tar` or `SAP_NW_RFC_Lin_x86.tar` (64-bit and 32-bit respectively)
Step 2	Create the `/usr/local/lib/sap/` directory for the SAP libraries to reside in. `md /usr/local/lib/sap`
Step 3	Copy the RFC tar file into the directory (from Step 2) and extract the contents: `$tar -xvf SAP_NW_RFC_Lin_x64.tar`
Step 4	Put the library files into a $LD_LIBRARY_PATH folder.
Step 5	Add LIBRARY_PATH and PATH to `/etc/profile`: export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/lib/sap" export PATH=$PATH:/opt/universal/opscli/bin/:/opt/universal/usap/bin/:/root/startup/

Preparation of the RFC libraries for SUSE Linux

Step 1	Download the appropriate tar file for the target platform: `SAP_NW_RFC_Lin_x64.tar` or `SAP_NW_RFC_Lin_x86.tar` (64-bit and 32-bit respectively)
Step 2	Create the `/usr/local/lib/sap` directory for the SAP libraries to reside. *REQUIRED, MUST MATCH THIS NAME:* `md /usr/local/lib/sap`
Step 3	Copy the RFC tar file into the directory from Step 2 and extract the contents: `$tar -xvf SAP_NW_RFC_Lin_x64.tar`
Step 4	Put the library files into a $LD_LIBRARY_PATH folder.
Step 5	Add the path from Step 2 to the LD_LIBRARY_PATH environment variable `export LD_LIBRARY_PATH=`"$LD_LIBRARY_PATH:/usr/local/lib/sap"
Step 6	To maintain the LD_LIBRARY_PATH setting across sessions, place the export line from Step 4 into your profile. Example: Add LD_LIBRARY_PATH to `/etc/profile.local`. Note If `/etc/profile.local` does not exist, create it and exit from the user session to re-source the new profile.

File Content of profile.local

export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/lib/sap"

PATH=$PATH:/opt/universal/ops/bin

PATH=$PATH:/opt/universal/ucmdmgr/bin

PATH=$PATH:/opt/universal/usap/bin

PATH=$PATH:/opt/universal/bin

export PATH

Universal Agent 7.3.x

Installing Universal Agent - Universal Connector for SAP Prerequisite