# Configure the Workato On-prem Agent (OPA)

Configuring a Workato On-prem Agent (OPA) on the Sap server consists of the following steps:

Download Workato On-prem Agent (OPA)
Download the SAP JCO libraries
Create SAP profile in OPA
Run OPA

# Download Workato On-prem Agent (OPA)

For Workato to talk to SAP, you must install a Workato On-prem Agent (OPA) on your SAP server, or on a separate virtual machine that can reach your SAP server.

The Virtual Machine server and your SAP server must be in the same domain, not outside of the firewall, and able to access each other. To test the virtual machine server and the SAP's server's ability to communicate with each other, try to ping the other server from each server.

Alternatively, if there are restrictions on downloading the on-prem agent on the same system or domain as SAP, you can use SAP router (opens new window) to regulate access to your SAP system. This approach helps ensure compliance with internal policies and regulatory requirements.

Follow these instructions to download and setup a Workato On-prem Group and subsequently following creating an On-prem Agent.

CONNECTION SETUP RECOMMENDATION

We recommend that you select Directly in Workato for easier connection management in the future.

# Download the SAP JCO libraries

If you do not already have a license to use SAP JCo libraries, contact your SAP provider for a license.

Visit SAP JCO Libraries (opens new window) to download the following items:

SAP JCO connector libraries
- Direct connections (version 3.1.7 and above)
- Message server connections (version 3.1.7 and above)

OPERATING SYSTEM COMPATIBILITY

Select the correct version of the library for your operating system.

Additionally, refer to SAP Note 2786882 - SAP JCo 3.1 release and support strategy (opens new window) to make sure your operating system fulfills all prerequisites.

After you download the libraries, place them in the lib_ext/ directory of all On-prem Agents in your created group.

Windows users:: Ensure that you have imported all relevant files into the lib_ext folder. You should have imported a total of 3 files: sapjco3.dll, sapjco3.jar, and sapidoc3.jar into your lib_ext folder. A file named sap-connector-X.X.X.jar should already be inside.
Mac users:: Ensure that you have imported all relevant files into the lib_ext folder. You should have imported a total of 3 files: libsapjco3.dylib, sapjco3.jar, and sapidoc3.jar into your lib_ext folder. A file named sap-connector-X.X.X.jar should already be inside.
Linux users:: Ensure that you have imported all relevant files into the lib_ext folder. You should have imported a total of 3 files: libsapjco3.so, sapjco3.jar, and sapidoc3.jar into your lib_ext folder. A file named sap-connector-X.X.X.jar should already be inside.

# Run OPA

Follow these instructions to run the On-prem Agent. After it successfully runs, you can move on to configure the SAP connector in Workato.

REFLECT SAP SCHEMA CHANGES

For OPA versions v25 and above, whenever there’s a change in the BAPI, RFC, or IDoc schema (such as the addition of custom fields, changes in data type, or changes in field length), click the Refresh button in the top right corner of the recipe editor. For OPA versions lower than v25, you must restart OPA to reflect changes in Workato. Refresh SAP schema

# Create a SAP profile

If you have chosen to setup connections Directly in Workato - Follow these instructions to create a SAP connection within Workato.
If you have chosen to setup connections Manually in each agent - Follow these instructions to create a SAP profile within the On-prem Agent. After configuring the config.yml file, you must restart the On-prem Agent for the changes to be enforced. This update to the config.yml must be done for every agent in your group.