Ancestors

Toot

Written by Christian Drumm πŸ‡ͺπŸ‡ΊπŸ§—πŸš΅ on 2024-11-28 at 06:57

Has anyone here succeeded in executing a POST request using the #OData v4 adapter in #SAP Integration Suite? I can't find any useful documentation and none of my test did work.

=> More informations about this toot | More toots from ceedee666@mastodon.social

Descendants

Written by Christian Drumm πŸ‡ͺπŸ‡ΊπŸ§—πŸš΅ on 2024-11-28 at 07:49

Finally, after nearly two days of effort, I got it working! πŸŽ‰πŸ’ͺ Why do seemingly simple tasks always have to be so complicated with #SAP solutions? πŸ€”

=> More informations about this toot | More toots from ceedee666@mastodon.social

Written by Christian Drumm πŸ‡ͺπŸ‡ΊπŸ§—πŸš΅ on 2024-11-28 at 08:33

Here is a video of the final process:

httpie -> SAP Integration Suite -> SAP CAP

The integration flow consists of:

JSON to XML -> Message Mapping -> OData v4

cc @qmacro

=> View attached media

=> More informations about this toot | More toots from ceedee666@mastodon.social

Written by Christian Drumm πŸ‡ͺπŸ‡ΊπŸ§—πŸš΅ on 2024-11-28 at 09:36

After further experiments, using the plain HTTP adapter proved to be a much better option. It required simply providing the expected JSON payload, and the integration worked seamlessly.

=> More informations about this toot | More toots from ceedee666@mastodon.social

Written by DJ Adams on 2024-11-28 at 08:13

@ceedee666 what was the issue or problem, in the end? I'm not an Integration Suite person, but I'm curious ...

=> More informations about this toot | More toots from qmacro@hachyderm.io

Written by Christian Drumm πŸ‡ͺπŸ‡ΊπŸ§—πŸš΅ on 2024-11-28 at 08:20

@qmacro My backend is a #SAP #CAP service. It has an entity Products. The #OData adapter of the Integration Suite expects a very specific #XML format to invoke the ODATA service correctly. In my case the XML had top look like this:

<Products>

	<currency_code>USD</currency_code>

	<name>Ridley Kanzo Fast</name>

	<price>5000</price>

	<productID>RidleyKanzo</productID>

	<stock>15</stock>

</Products>

=> More informations about this toot | More toots from ceedee666@mastodon.social

Written by Christian Drumm πŸ‡ͺπŸ‡ΊπŸ§—πŸš΅ on 2024-11-28 at 08:22

@qmacro The first seems to be the entity set, the second the entity.

This was totally different to what I expected. As this is the JSON in needed to send when invoking the service directly:

{

"productID": "Test",

"name": "Test",

"description": "This is a description test",

"price": 1000,

"currency_code": "USD",

"stock": 15

}

=> More informations about this toot | More toots from ceedee666@mastodon.social

Written by Christian Drumm πŸ‡ͺπŸ‡ΊπŸ§—πŸš΅ on 2024-11-28 at 08:23

@qmacro If you know this it kind of makes sense. However, I couldn't find this information anywhere in the documentation. Just trial and error....

=> More informations about this toot | More toots from ceedee666@mastodon.social

Proxy Information
Original URL
gemini://mastogem.picasoft.net/thread/113559277658381488
Status Code
Success (20)
Meta
text/gemini
Capsule Response Time
259.482622 milliseconds
Gemini-to-HTML Time
5.524404 milliseconds

This content has been proxied by September (ba2dc).