Hi Laszlo,
if you already have the token, you can hand it over as query, if you need a complete token process you need to manually handle it a the moment using the persist atom to store it in the bizstore for later usage.
Please compare with B1i help "Call HTTP Atom" usage of query id:
<query id="identifier" value="value"/>
<!--optional - define your own query parameters - multiple elements allowed-->
query id
Enter query strings for your call.
If you want to handover URL parameters containing special characters, you must URL encode the string. The integration framework provides the encode Java function in the utils2 namespace. To ensure that the function works correctly, cast the string with the string XPath function.
Define the call as follows:
<call>
<xsl:variable name="var">{"myPar":"myVal"}</xsl:variable>
<query id="json" value="{utils2:encode(string($var))}"/>
...
</call>
If the queries are fixed and you use the SLD entry for your HTTP connection settings, you could also enter them in the segment query using the following notation:
query
Enter the query strings, separated by semicolon. Do not add ?.
Best regards
Bastian
P.S.: A full automatic token process supporting Outh is not yet part of or http adapter, but we enhanced our http adapter to be able to communicate with the B1 Service Layer for HANA (based on a customized Outh protocol) with Framework version 1.22.1. This could maybe an option to avoid the manual token process for your requirement, too.