Hello everyone,
on the Integration Suite we get the error "Duplicate Key error" when using the JDBC adapter and an update.This interface already exists on the PI and works properly.
The test on the Integration Suite takes place with exactly the s...
Hi Experts,
we are facing issues with a HTTP Receiver Adapter for a simple integration flow.we always get an HTTP 500 and unfortunately the recipient cannot say anything about the error.
The Iflow is for routing only. Source->HTTP->ISuite->HTTP (...
Hello everyone,
can you please help me with a UDF? The UDF should generate a hashed value with BCrypt and salt in the current version ($ 2a $). Input is a single value from the mapping.
Thank you very much!
Best regards
Igor
Hello all,I found a solution for myself. We have several clients running in the backend. You can include the client in the API management configuration. But this configuration doesn't seem to have any affect.I checked the HTTP trace in the backend an...
Hello Vijay, thanks!As I wrote, it is an update and therefore the key must be the same.Likewise, I can successfully process the same payload with the same key via the PI again and again.But of course I tried it with another key without success.Do you...
Thank you Riccardo,I found out via weebhook that the HTTP adapter sets the "Transfer-Encoding" header, which makes the "Content-Length" not work.A script at the end of the flow, which changes the body from stream to string, brought the solution. Ther...
Hello Vijay,from the target. As I said before, I'm wondering why setting the payload as a constant in the content modifier body works. With the exact same headers as when the payload comes from the source.
