SOAP connector
The SOAP connector lets you integrate Adeptia with SOAP-based web services by exposing your own process flows as SOAP endpoints for other systems to invoke.
What you can do with the SOAP connector
Adeptia can expose a SOAP endpoint (SOAP Webhook) that external systems call to trigger a process flow. Each published endpoint is associated with a specific process flow template. Callers identify which template to invoke by including a token in the SOAP request header. You can also control whether the call is handled synchronously (the caller waits for a response) or asynchronously (the caller receives an immediate acknowledgment and the process flow runs in the background). When no explicit mode is specified, synchronous mode is used by default.
Security options
The SOAP connector supports multiple approaches to securing communication, which you can combine to meet your requirements.
Authentication
| Authentication type | How it works |
|---|---|
| Basic authentication | The caller supplies a username and password, which Adeptia validates before processing the request |
| Kerberos (SPNEGO) | The caller presents a Kerberos ticket; Adeptia validates it and makes the authenticated principal available to the process flow |
Message-level security
For inbound SOAP requests, Adeptia can enforce security at the message level using WS-Security. This covers:
- Digital signatures: Adeptia uses a configured keystore to sign outgoing messages, giving recipients confidence in the message's origin and integrity.
- Encryption and decryption: Incoming messages can be decrypted using a designated keystore. Adeptia supports both plain-text and digest password types for username token validation, and will reject a message if the received password type does not match what is required.
Security policy
A security policy brings together the authentication method, keystores, and token settings for a SOAP endpoint.
Synchronous and asynchronous execution
When an external system calls an Adeptia SOAP endpoint, you choose how the response is returned:
| Mode | Behavior |
|---|---|
| Synchronous | Adeptia runs the process flow and returns the result in the same SOAP response |
| Asynchronous | Adeptia accepts the request immediately and runs the process flow in the background; the caller receives a simple acceptance acknowledgment |
If the process flow produces a SOAP fault (an error condition with a defined fault code, message, and optional detail), Adeptia returns that fault to the caller in the standard SOAP fault format.
Attachment support
Inbound SOAP requests can include attachments. Adeptia handles MTOM (Message Transmission Optimization Mechanism) packages as well as standard MIME attachments, making binary and file-based payloads available to the process flow alongside the main message body.
Routing incoming requests
Adeptia supports context-based routing for inbound SOAP requests. When routing is enabled, the platform evaluates the content or context of each incoming message to determine how it should be handled within the process flow.