Designer services are executed with the xUML Runtime. The Runtime works with the concept of sessions. Sessions are equivalent to units of work, that can be committed or rolled back depending on the status at the end of the session. A session corresponds to one concrete instance of an execution of a service, namely of
- SOAP services,
- timer services
- schedulers
- HTTP services
- SAP RFC services
- JMS services
- Java services
Refer to xUML Runtime Transaction Concepts for more information on session and transaction handling in general.
The first SAP adapter call within a session takes an SAP connection from the SAP connection pool. All subsequent adapter calls within this session will reuse this SAP connection, means the connection is blocked until session end. Take this into account when defining the connection pool size (poolSize) on the SAP alias. See SAP Adapter Reference to see an overview on all configurations of the SAP adapter.