Securing the SAP service
The Adeptia SAP service lets you control how connections to your SAP system are established and protected, giving you the flexibility to meet your organization's security and network requirements when exchanging IDoc documents with SAP.
Connection types and what you provide
When you configure an SAP client connection, you choose between two connection modes: a direct connection to a specific SAP application server, or a load-balanced connection that routes through an SAP message server to a group of application servers. Each mode requires a different set of network and logon details.
| Connection mode | What you configure |
|---|---|
| Direct | Application server host and system number |
| Load balanced | SAP system ID, message server host, optional message server port, and application server group |
In both cases you also provide the SAP client number, logon credentials, and optionally a logon language and character set settings.
Logon identity options
You can identify the connecting user either by a standard SAP logon username or by a logon alias. Only one of these is used for a given connection; the choice depends on how your SAP system is configured.
Routing connections through SAP Router
If your SAP system sits behind a SAP Router, you can supply a SAP Router string that describes the chain of routers and ports the connection must traverse. This lets Adeptia reach SAP systems that are not directly accessible from the network where Adeptia runs.
Secure Network Communications (SNC)
For environments that require encrypted or single-sign-on connections, you can enable Secure Network Communications (SNC). When SNC is turned on, you provide:
| SNC setting | Purpose |
|---|---|
| SNC partner name | Identifies the SAP system's SNC identity |
| SNC own name | Overrides the default local SNC identity for the Adeptia side |
| SNC quality of protection | Sets the security level (a value from 1 to 9) |
| SNC library path | Points to the library that provides the SNC service |
| SNC single sign-on | Controls whether the SNC identity is used for authentication or whether username and password are used instead while the connection remains encrypted |
When SNC is not enabled, the connection uses standard username and password logon.
Connection pool and performance controls
Beyond security, you can tune how the SAP client manages its pool of active connections. Available controls include the maximum number of simultaneous active connections, the maximum number of idle connections kept open, how long idle connections are held before being closed, how frequently the pool checks for expired connections, and the maximum time to wait when all connections are in use. These settings help you balance resource consumption against throughput for your integration workloads.
Credential resolution from a vault or configuration store
SAP client credentials, specifically the logon username and password, can be resolved at runtime from a project-level configuration or vault store rather than being stored directly in the connection definition.
Transaction integrity for IDoc exchange
Every IDoc sent to or received from SAP is tracked using a transaction identifier (TID). The platform records the state of each TID, progressing through created, executed, committed, confirmed, and rolled-back states. This tracking helps detect duplicate TID submissions and captures any failures during sending or receiving with error details for review. The IDoc payload and its header metadata, including sender and receiver partner information, IDoc type, and release information, are also recorded alongside the transaction state.