The DocumentPush function transfers document data directly to the configured target system at the time it is created. The middleware automatically triggers the process and delivers a complete JSON payload to the stored interface. The result is seamless, event-driven integration without any manual intermediate steps.
Requirements for your interface
To ensure that the target system can receive the data reliably, the following technical requirements must be met:
| Requirement | Description |
|---|---|
| Network availability | Target URL must be accessible from the middleware instance. |
| HTTP(S) protocol |
Processing of POST requests required.
|
| Data format |
Acceptance of JSON payloads (Content-Type: application/json).
|
| Security |
Optional: Authentication via Authorization header.
|
Configuration in the portal
Configuration is carried out directly on our portal for the respective Configuration:
1. Activate license on Configuration level
In Configurations, open the desired configuration.
On the right side of the sidebar under Actions, click on Licenses.
Activate the DocumentPush license and save.
Optional: With the Document trigger license, the same document can be sent to multiple target systems simultaneously.
2. Define interface
URL for Terminals (with/without ‘isTest’)
Store the target URL for the production and test environment.
Authorization Header for DocumentPush (with/without ‘isTest’)
Optional (recommended): Secure the interface via Authorization header.
Comments
0 comments
Please sign in to leave a comment.