Krossover -migrating the ESB
service calls of i.Manage to
Azure Using Odata service
Agenda
1. As-is functionality & To-Be functionality.
2. Prep work/connectivity needed to support this development
3. Understanding of the Consumption of Odata Service code in HANA
4. Confirmation from AZURE on successful receive of the data
5. Challenges faced while developing
6. Q&A
©Larsen & Toubro Infotech Ltd. Privileged and
Confidential 2
As-is functionality
Earlier the interface worked with middleware HCI and ESB for data transmission.
There is no post/get method in development of webservice (only SOAP based
WSDL were used to consume the sevice and the data was sent to downstream
system).
To-Be functionality
MW is decommissioned and we will now have a data transmission using Odata
service for HANA.
The attached email has the requriment to be built in HANA.
FW iFulfill(RR) ESB migration to Azure.msg
©Larsen & Toubro Infotech Ltd. Privileged and
Confidential 3
Prep work needed to support this development
• Microsoft Certificates chaining were failing in the local HANA SAP server.
the latest certificate from https://www.microsoft.com/pki/mscorp/cps/default.htm was
installed into the SAP system. All the four certificates were uploaded in SAP server by
STRUST
©Larsen & Toubro Infotech Ltd. Privileged and
Confidential 4
Understanding of the Consumption of Odata Service code in HANA
Instantiate the Client lo_http_client by using the service URL
“https://asbqa.azurewebsites.net/api/ASBToken/GetAccessToken ”
Pass the headers and set the URI for the GET request of the same Entity for which we want to POST.
– While filling the headers we have to pass a header Field with name ‘X-CSRF-Token’ and value ‘Fetch’.
– While filling the body we will pass the below 3 primary inputs of the service in JSON format
Trigger the HTTP GET request,
– The X-CSRF token can be retrieved from the Response attribute of the HTTP Client object.
Fill the headers of the request Attribute once again. but this time we set the X-CSRF token with the value retrieved from
above steps, with the header fields set to send Authorization .
– Set the Request HTTP method to POST
– Fill the BODY of the HTTP request with the data that has to be modified- data from i.manage.
– Trigger the HTTP post request in JSON format
ztestproxy2_eg2_a
SAP CODE attached. uth
©Larsen & Toubro Infotech Ltd. Privileged and
Confidential
Challenges faced while developing
authentication issue for the posting the token through API
• Solved by disabling the cookie and logon pop up
443-SSL Certificate Error
• Installed 4 certificates of Microsoft
©Larsen & Toubro Infotech Ltd. Privileged and
Confidential
