Skip to main content

Connecting Adeptia Automate to SAP

Adeptia Automate integrates with SAP systems using the SAP Java Connector (JCo) RFC protocol. When you configure an SAP connection, Adeptia Automate manages a pool of RFC destinations on your behalf; you supply the connection parameters once, and the platform handles session lifecycle, connection pooling, and reconnection automatically.

Prerequisites​

Before configuring an SAP connection in Adeptia:

  • SAP JCo libraries must be installed in the Adeptia runtime environment. Contact your Adeptia administrator if you are unsure whether JCo is installed.
  • You need network access from the Adeptia server to the SAP application server (RFC port, typically 33xx).
  • You need an SAP system user with the authorizations required for IDoc exchange.

Connection Parameters​

When creating a new SAP connection in the Portal, provide:

ParameterDescription
Application Server HostHostname or IP address of the SAP application server
System NumberTwo-digit SAP system number (e.g., 00)
ClientSAP client number (e.g., 100)
Logon LanguageLanguage code for the SAP session (e.g., EN)
UsernameSAP logon user
PasswordSAP logon password
System IDThree-character SAP system ID (SID)

Connection Pooling​

Adeptia manages an RFC connection pool for each configured SAP connection. The pool maintains a set of active RFC destinations, reusing them across invocations to avoid the overhead of establishing a new connection for every document exchange. You do not need to manage pool sizing manually for most deployments; the platform applies sensible defaults.

Testing the Connection​

After saving the connection configuration, use the Test Connection action in the Portal to verify that Adeptia can reach the SAP system and authenticate successfully.