SFSF Onboarding Interface

[Former Member]

Hi All,

In SFSF Onboarding integration i see two different kinds of adapters (ODATA & AXIS) are used. ODATA adapter --->Onboarding Interface / AXIS adapter ----> New hire Interface, Can some one let me know why has SAP has come with this approach.

Thanks,

Siva.

[Muniyappan · Accepted solution]

Odata service is created because it might have been created recently. Last few years whoever is creating web services, they are opting to go with Rest service/Odata..

I won’t get surprised if SOAP service is decommissioned and new Rest service is introduced for new hire. But it is SAP’s decision to do such change.

[Former Member]

Thanks.

But can some one explain me why we use begin / cancel session for SFSF SOAP \ AXIS Adapter, but for ODATA why we don't use any of

these sessions ?

[Muniyappan]

My assumption is ,in REST, before they post the request, they first call the login interface to get the session key and then they post the request. once request is successfull, then they close the session. getting session id and closing is done in adapter module which is incorporated in REST adapter.But that is not the case for SOAP.

Have you noticed why you provide password in the ODATA channel but not in SOAP?

for REST channel, session handling is done using adapter module, so that is why begin and cancel is not used in the REST channel. I am not sure if for each call, they are getting session and closing the session in the REST channel.

For saop, the session key is sent via cookies, that is why you use SOAP axis to set the cookies for outgoing soap message. That is the reason why the magic adapter module configuration is used for soap axis. here in SOAP service, session handling is not done via dapter module, so they made it two seperate interfaces one for begin and one for cancel.

If you are working in SF project you could also ask the product team by raising SAP ticket.I believe Product team should be the one who can give you exact answer for your question.

Also you can give a try to debug and understand how calls are made.moreover you can see what is written in the adapter java code for soap and REST.

https://blogs.sap.com/2016/03/03/lets-debug-debugging-decompilation-fly-sap-application-server-java/