Thus, you need to have a policy, that converts your events to driver op data, and along the way you need to add this data into the event. So in any XML attribute, in the node, are available to be pushed into the URL in the Resource configuration. ![]() So obvious question is, where does the info for username and password1 come from? This is the part I wish was clearer in the docs.īasically the REST driver does not take or events per se, instead it expects a policy to transform the XDS to: SaparibaURL/qualifications?realm=s4All&user= &passwordAdapter= A cloud-based innovative solution that allows suppliers and buyers to connect and do business on a single platform. ![]() It provides you seamless connectivity and its a low-cost. So you would be allowed to set the URL in the IDM config as: The most popular way to establish SAP Connectivity with Non SAP System is via OData REST API. When you define a URL for them, you are allowed to stick in 'tokens' delimited inside (angle brackets/less-than/greater-than signs). It is tricky.īasically on the Sub channel, driver configuration, driver properties (I did that backwards, but you know what I mean) there are "Resources" defined. You can incorporate functionality from SAP Ariba solutions into your own applications by calling the APIs published on the SAP Ariba developer platform. The goal of the docs should be to get there first read. ![]() This part is technically there in the docs, but really should be much more in your face and obvious, since after I write this and you go back and re-read the docs you will say "Oh I get it now".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |