OData Session Management and Metadata Hostnames

[Former Member]

Hi Experts,

Two quick questions:

1/ In my oData read / GET response, the id and uri properties contain fully qualified URLs that represent the resource accessed, such as:

"__metadata": {

"id": "https:\\myinternalhost.com\sap\opu\odata\sap\SOME_SRV\SomeSet(A='1')",

"uri": "https:\\myinternalhost.com\sap\opu\odata\sap\SOME_SRV\SomeSet(A='1')",

...

myinternalhost.com is resolvable only within the internal network, not on the internet where this service is being consumed from.

How can persuade Gateway to either use a relative id and uri (such as "id" : "\sap\opu\odata\sap\SOME_SRV\SomeSet(A='1')" ) or, alternatively, use a different hostname in those urls - one that matches the hostname the clients connect to?

2/ If I have an internal batch application authenticating with Gateway via basic authentication header but NOT honoring the set-cookie directives on subsequent calls, are there any performance ramficiations? That is, in terms of speed and capacity, is it okay to have applications continually call into Gateway with a user:password but ignoring the cookies that Gateway returns? Does Gateway access an external credential store to check the password on each call, or is the credential cached in memory?

Thanks a lot. I've searched around for previous questions along these lines.

[Andre_Fischer]

Hi Chris,

for the URL issue you can try to configure the hostname in table HTTPURLLOC

URL Generation - SAP NetWeaver Gateway Foundation (SAP_GWFND) - SAP Library

Regards,

Andre