SAP CPI-PI iFlow
The SAP CPI-PI iFlow operator provices the possibility to trigger iFlows in an SAP CPI system. It calls the set CPI system sending the received input data (JSON is assumed) as payload. The response is emitted via the outbound port. Currently, only HTTP Basic Authentication is supported.
Configuration Parameters
|
Parameter |
Type |
Description |
|---|---|---|
| Connection | object | Mandatory. Connection parameters and credentials setting the CPI backend to communicate with. |
| iFlow path |
string |
Mandatory: The iFlow that should be triggered. Currently, this has to be an iFlow expecting JSON input. |
| Retry attempts | integer | In case an HTTP(S) request to the CPI system fails, it will be
retried n times. Only responses in the range of
5xx status codes trigger a retry;
4xx status codes will lead to an immediate
failure.
Default: 1 |
| Verify TLS certificates |
boolean |
In case the CPI system uses a self-signed certificate, you may
want to disable the certificate validation performed during the TLS
handshake. Use this with caution as the replying host's identity
will no longer be ensured!.
Default: true |
| Outgoing request timeout | string | Defines the maximum amount of time a request outgoing to the set CPI system is allowed to take before being canceled (this does not necessarily stop the triggered iFlow). Valid suffixes are ms, s, m, h. Setting this to 0s results in no timeout. (Independently, underlying software/hardware layers may enforce shorter timeouts.) |
Input
|
Input |
Type |
Description |
|---|---|---|
|
input |
message |
Receives DH message objects only considering their body. The body currently needs to be JSON. |
Output
|
Output |
Type |
Description |
|---|---|---|
|
output |
message | Emits messages containing the response of the CPI system. In case an error occurred the error message - if existing - will be contained. The message.error attribute will be set accordingly. |