Skip to Content

SAP connector prerequisites

Introduction

Certain prerequisites are required to be met in order to use the SAP Connector for Jitterbit Integration Studio, as described here.

Supported SAP versions

An SAP instance using ECC version 6 or later, or SAP S/4HANA single-tenant is required.

Jitterbit's SAP connector relies on the SAP Java Connector (SAP JCo) library and network connectivity to communicate with ECC or S/4HANA. Customers must enable network connectivity between Jitterbit agents and the necessary SAP components, such as the SAP Application Server and the SAP Gateway. This may require changes to the network configuration of the on-premises or cloud hosting service (such as SAP RISE).

Supported Jitterbit agent versions

Jitterbit agents that are version 10.1 or later are required. These agent versions automatically download the latest version of the connector when required.

Both private agents and cloud agents are supported. If cloud agents are used, no further configuration is necessary.

If private agents are used, they must have certain libraries provided by SAP installed. See SAP connector installation.

Note

Beginning with private agent version 10.54, Jitterbit's SAP connectors will no longer work until you install these libraries as described in SAP connector installation. You can install the libraries prior to upgrading to 10.54 or later to prepare for the upgrade, or you can install them after upgrading to 10.54 or later.

These files persist on post-10.54 private agent upgrades, so this process needs to be followed only a single time on each private agent machine.

Supported activities

The SAP Connector supports these methods of communicating with SAP:

Outbound IDocs (outbound from SAP, inbound to Jitterbit) are not currently supported in Integration Studio.

To use outbound IDocs requires the Jitterbit SAP event listener, which is supported only in Design Studio. See the Design Studio SAP connector and SAP event listener sections for more information.