All Apps and Add-ons

what are the requirements on the SAP Side?

hgehrts_splunk
Splunk Employee
Splunk Employee

Hi,

we just installed the App and want to connect to the odata service on the SAP Side... but what is needed there? Our odata endpoint reports a 503. We do have Fiori set up but maybe not completely?
It seems to us that SAP cannot find any data on that endpoint.

best
Henning

0 Karma

mtroianovskyi
Explorer

In order to verify that the SAP user is granted all the necessary permissions, check the following. Using a browser, navigate to the SAP ODATA service URL like http(s)://your-solman-host:port/sap/opu/odata/sap/AI_SYSMON_OVERVIEW_SRV/SystemListSet?$format=xml - the browser will prompt for username/password (HTTP basic auth). Use the SAP user that is supposed to be used in Splunk. In case if you see a valid XML response starting with <feed ...> tag, then the permissions are correct. In case if you get HTTP 403 Forbidden, then the permissions are incorrect and additional configuration is required on SAP side.

The most straightforward way to get started in a DEV environment is to assign SAP_ALL role to the user within SAP. However, this is a security risk since this grants all SAP capabilities (not just the ones related to ODATA service access). So this approach must not be used for production.

For production setup, check the fine grained authorization object setup Authorization Objects Overview. Also check section Front-End Server and Back-End Server: Assign OData Service Authorizations to Users in App Implementation: Monitor Systems

In case if for some reason the user still can not access the ODATA service, use the SU53 transaction on SAP side to troubleshoot the failed authorization check.

hgehrts_splunk
Splunk Employee
Splunk Employee

fixed. We used an Account that has all rights on the SAP side. Then it worked. Check splunkd.log for response codes from SAP:
index=_internal solman
Or try the SAP endpoint URL in a Browser and check the feedback there. The login window that pops up in a browser is where you need to put in the API login credentials.

0 Karma

hgehrts_splunk
Splunk Employee
Splunk Employee

we solved the connectivity Problem. It was a settings / rights issue on the SAP side. We tried an account in SAP that has all rights (SAPALL?) and that worked out ok.

0 Karma
Did you miss .conf21 Virtual?

Good news! The event's keynotes and many of its breakout sessions are now available online, and still totally FREE!