Skip to end of metadata
Go to start of metadata



  • The Jitterbit Harmony SAP Connector is compatible with either SAP ECC version 6 and above or SAP S/4HANA on-premises
  • The SAP Connector is compatible with the Jitterbit Harmony Cloud Agent Group and Jitterbit Harmony Private Agents. To connect to SAP S/4HANA on-premises using private agentsversion or higher is required

The Jitterbit Harmony SAP Connector supports complete IDoc, BAPI, and RFC compatibility as well as web services and custom fields. To create SAP functions in Jitterbit, you must first create at least one SAP endpoint. The SAP Connector technology is built into the Jitterbit Harmony Design Studio, and creating an endpoint is your first step in activating this capability.

Create an SAP Endpoint

  • Click the orange jigsaw icon  on the main menu.
  • Scroll down and select SAP in the popup window.
  • Select SAP Endpoint.

  • A dialogue for endpoint creation displays as shown below.

Connection Parameters

Configuration of an SAP connection includes these fields:

  • Name: Enter a name to use to identify the SAP connection. The name must be unique for each SAP connection and must not contain forward slashes (/) or colons (:).

  • SAP Version: Select either ECC or S4HANA as the version of your SAP system.

  • Login: Enter the user name for logging in to the SAP system.

  • Password: Enter the password for logging in to the SAP system.

  • Client: Enter the numeric client ID associated with the SAP system. The organization's SAP administrator can supply this information.

  • Language: Enter the language in which SAP messages should be sent. The default language is English.

  • Router: If the SAP system is protected by a firewall, enter the router string required to connect to it.

Configuring for a Direct SAP Connection

  • For Direct Connection: Select the checkbox if the SAP connection is a direct server connection (default).

  • Host: Enter the SAP Application Server HostName.

  • System Number: Enter the SAP System Number.

Configuring for a Load Balanced SAP Connection

  • For Load Balanced Connection: Select the checkbox if the SAP connection processes requests through a load balancer.

  • MSHost: Enter the SAP Message Server Host Name.

  • MSPort: Enter the SAP Message Server Port.

  • Group Name: Enter the SAP Group Name of the application servers.

  • System ID: Enter the SAP System ID.

  • After completing your connection parameters, click the Test Connection button. You will receive a progress report, which should be followed by a success message.

  • Click the Save icon on the toolbar in the upper right corner of the screen.
  • When you have successfully created an SAP endpoint, you can begin creating an SAP function.

In Case of Errors

If you receive an error message when testing the SAP endpoint connection, read the details carefully. Check the folder on your computer where Jitterbit Private Agent is installed to make sure the following SAP components are in place:


Located in Jitterbit Agent Folder (JITTERBIT_HOME)*



Both files in Windows: \Program Files (x86)\Jitterbit Agent\tomcat\webapps\axis\WEB-INF\bin\

Both files in Linux: /opt/jitterbit/tomcat/webapps/axis/WEB-INF/lib


Windows: \Program Files (x86)\Jitterbit Agent\bin\sapjco3.dll

Linux: /opt/jitterbit/lib/


  • The DLL must be version 720.94 or above.
  • The sapjco3.dll file must be compatible with IA32 architecture (Intel 32-bit). This is true even on a 64-bit Windows OS, as Jitterbit currently requires a 32-bit Java Runtime Environment on Windows.

* Substitute the file path of your Jitterbit Private Agent if different on your computer as appropriate, such as C:\Program Files (x86)\Jitterbit Agent\ (for Windows) or /opt/jitterbit/ (for Linux)

These components are included in the Jitterbit Private Agent installer (version and above), The components can be overwritten by newer versions as needed. If this becomes necessary, follow the steps below.


  1. Make a backup copy of the existing files.
  2. Stop the Tomcat server.
  3. Copy the new version to the appropriate folder as shown in the table above.
  4. Restart the Tomcat server.

On This Page

Related Topics

Last updated:  Aug 22, 2019