If SAP NetWeaver RFC SDK and NodeJS are already installed on your system, you can install the node-rfc package from npm, or build from source.

You may use the current or any of LTS node releases and the latest SAP NW RFC SDK release (fully backwards compatible).

SAP NW RFC SDK Installation

Information on where to download the SAP NW RFC SDK you may find here .

The NodeJS RFC connector relies on SAP NW RFC SDK and must be able to find the library files at runtime. Therefore, you might either install the SAP NW RFC SDK in the standard library paths of your system or install it in any location and tell the NodeJS connector where to look.

Here are configuration examples for Windows, Linux and macOS operating systems.


  1. Create the SAP NW RFC SDK home directory, e.g. c:\nwrfcsdk
  2. Set SAPNWRFC_HOME environment variable: SAPNWRFC_HOME=c:\nwrfcsdk
  3. Unpack the SAP NW RFC SDK archive to it, e.g. c:\nwrfcsdk\lib shall exist.
  4. Include the lib directory to the library search path on Windows, i.e. extend the PATH environment variable.

Add c:\nwrfcsdk\lib to PATH.


  1. Create the SAP NW RFC SDK home directory, e.g. /usr/local/sap/nwrfcsdk.

  2. Set the SAPNWRFC_HOME environment variable: SAPNWRFC_HOME=/usr/local/sap/nwrfcsdk

  3. Unpack the SAP NW RFC SDK archive to it, e.g. /usr/local/sap/nwrfcsdk/lib shall exist.

  4. Include the lib directory in the library search path:

    • As root, create a file /etc/ and enter the following values:

      # include nwrfcsdk
    • As root, run the command ldconfig. To check if libraries are installed:

      $ ldconfig -p | grep sap # should show something like: (libc6,x86-64) => /usr/local/sap/nwrfcsdk/lib/ (libc6,x86-64) => /usr/local/sap/nwrfcsdk/lib/ (libc6,x86-64) => /usr/local/sap/nwrfcsdk/lib/ (libc6,x86-64) => /usr/local/sap/nwrfcsdk/lib/ (libc6,x86-64) => /usr/local/sap/nwrfcsdk/lib/ (libc6,x86-64) => /usr/local/sap/nwrfcsdk/lib/ (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/ (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/


The macOS firewall stealth mode is by default active, blocking the ICMP protocol based network access to Macbook. Applications like Ping do not work by default (Can’t ping a machine - why?) and the stealth mode must be disabled:

sudo /usr/libexec/ApplicationFirewall/socketfilterfw --setstealthmode off
  1. Create the SAP NW RFC SDK home directory /usr/local/sap/nwrfcsdk (this location is fixed, more info below)

  2. Set SAPNWRFC_HOME environment variable: SAPNWRFC_HOME=/usr/local/sap/nwrfcsdk

  3. Unpack the SAP NW RFC SDK archive to it, e.g. /usr/local/sap/nwrfcsdk/lib shall exist.

  4. Set the remote paths in SAP NW RFC SDK by running following bash script:

    cd $RPATH
    # add LC_RPATH
    for filename in *.dylib; do
        install_name_tool -add_rpath $RPATH $filename
    # fix LC_LOAD_DYLIB
    # in libisui18n
    install_name_tool -change libicuuc.50.dylib @rpath/libicuuc.50.dylib libicui18n.50.dylib
    install_name_tool -change libicudata.50.dylib @rpath/libicudata.50.dylib libicui18n.50.dylib
    # in libicuuc
    install_name_tool -change libicudata.50.dylib @rpath/libicudata.50.dylib libicuuc.50.dylib

This location is fixed to the default /usr/local/sap/nwrfcsdk/lib rpath, embedded into node-rfc package published on npm.

After moving SAP NW RFC SDK to another location on your system, the rpaths must be adjusted in SAP NW RFC SDK and in sapnwrfc.node libraries.

For SAP NW RFC SDK, set the SAPNWRFC_HOME env variable to new SAP NW RFC SDK root directory and re-run the above script.

For node-rfc:

$ npm install node-rfc@next
$ cd node_modules/node-rfc/lib/binding/darwin-x64-node-v64
$ install_name_tool -rpath /usr/local/sap/nwrfcsdk/lib /usr/new-path/lib sapnwrfc.node

The v64 suffix is the node abi version for the node release 10 and the suffix for your node release you may find here:

node-rfc Module Installation

If not already installed, you need to install node and npm first.

Set NODE_PATH to wherever your node modules are installed, like

set NODE_PATH=C:\Users\BSrdjan\AppData\Roaming\npm\node_modules

Install the node-rfc module from npm

npm install node-rfc


Check if the module can be found and loaded:

var r = require ('node-rfc)

Call remote enabled function modules in NW backend system (maintain your test system parameters first):

$ node demo\demo # demo1 ...

In case of issues, check if the SAP NW RFC SDK is properly installed:

$ sudo chmod a+x rfcexec
$ ./rfcexec # should show something like:
  Error: Not all mandatory parameters specified
    Please start the program in the following way:
    rfcexec -t -a <program ID> -g <gateway host> -x <gateway service>
      -f <file with list of allowed commands> -s <allowed Sys ID>
  The options "-t" (trace), "-f" and "-s" are optional.

The output when SAP NW RFC SDK cannot be found:

$ ./rfcexec
$ ./rfcexec: error while loading shared libraries: cannot open shared object file: No such file or directory


Behind a Proxy

If you are within an internal network that accesses the internet through an HTTP(S) proxy, some of the shell commands will fail with urlopen errors, etc.

Assuming that your HTTP(S) proxy could be accessed via http://proxy:8080, on Windows you can communicate this proxy to your shell via:

SET HTTP_PROXY=http://proxy:8080
SET HTTPS_PROXY=http://proxy:8080

or permanently set environment variables.


  1. ImportError: DLL load failed: The specified module could not be found.

    (Windows) This error indicates that the node-rfc connector was not able to find the SAP NW RFC SDK libraries on your system. Please check, if the $SAPNWRFC_HOME\lib directory is in your PATH environment variable.

  2. ImportError: DLL load failed: %1 is not a valid Win32 application.

    (Windows) This error occurs when SAP NW RFC Library 64bit version is installed on a system with 32bit version Python.

Environment variables


The environment variable may be set within a command prompt via the set command, e.g.

  • set PATH=%PATH%;C:\nwrfcsdk\lib (extend PATH with the C connector lib)
  • set HTTPS_PROXY=proxy:8080 (setting an proxy for HTTPS communication)

When the command prompt is closed, the environment variable is reset. To achieve a persistent change of the environment variable, do the following (Windows 7):

  1. Open the Start Menu and type environment into the search box.
  2. A window opens in which the user variables are displayed in the upper part and the system variables in the lower part. You may select and edit the desired variable.
  3. The modified variables are used when a new command prompt is opened.

Building from Source


Toolchain used for building on Windows is VS2013 Professional Update 2, with native tools command prompts for 32 and 64 bit architectures:

node-pre-gyp clean
node-pre-gyp configure --msvs_version=2013
node-pre-gyp build

Linux and macOS

node-pre-gyp clean configure build

In case of ‘utility’ file not found isssues with certain node releases on macOS, try:

env CXXFLAGS="-mmacosx-version-min=10.9" node-pre-gyp clean configure build

For unit tests run

npm test

For more test examples, see files in demo folder.

Building the Documentation

Change into the doc directory and type:

make clean
make html

The result is found in _build/html and for other options call make.

  • If you get an error ‘sphinx-build’ is not recognized as an internal or external command, operable program or batch file on calling make html, install sphinx

The docu is hosted on GitHub Pages, a propietary solution where a git branch gh-pages is created as an orphan and the output of the documentation build process (_build/html) is stored in that branch.

GitHub then serves these files under a special /pages/ url.

To update GitHub Pages, copy everyhing under _build/html and overwrite the existing files in the gh-pages branch root:

rm -Rf ~/tmp/html

cp doc/_build/html ~/tmp/.

git checkout gh-pages

rm -Rf *.html *.js *.inv _* doc .buildinfo

cp -R ~/tmp/html/. .

touch .nojekyll