Interfacing to SAP HR
in [Visual Objects]
|
From: Mike Pitcher on 17 Mar 2010 08:06 Has anyone actually interfaced with SAP HR? We have been told that SAP themselves deprecate the use of their .NET Connector (because it is based on Framework 1.1) and advise the use of web services. We have an opportunity to interface our e-recruitment package but are looking for someone to guide us on answering some technical questions in an "invitation to tender" with a view to paid work if we get the job. Anyone shed any light? Mike Pitcher
From: Geoff Schaller on 17 Mar 2010 17:10 Mike. We haven't done work on SAP but we do work with web services. A lot. Generally it is the way to go because it completely removes version issues to do with underlying OS and frameworks. It also allows the owner of the WS to upgrade and change their frameworks at will. There is always a small performance hit with a WS in that it needs to spin up after going to idle but beyond that, they are a lot easier to implement, deploy and utilise. For example, MS SharePoint and Reporting Services both have an object model you can use from code but they also both have and encourage developers to use their web service interface. That way they can change their object design from version to version without affecting the delivered interface. If you use the object model directly, you need to change your code. And ws are nice because (at least with VS) you get the class code to use the ws for free - it self generates. With VO we build our ws wrapper into a small but simple COM object and use that COM object in VO. We could do all the soap stuff direct from VO but it is messy, slow to develop and complex to maintain. All that XML parsing and constructing is just a pain. So I reckon you should go for it. Geoff "Mike Pitcher" <mike_no_spam_please_(a)pamuk.demon.co.uk> wrote in message news:675f92b6-de11-431b-a7fe-d2ef9a181381(a)q16g2000yqq.googlegroups.com: > Has anyone actually interfaced with SAP HR? > > We have been told that SAP themselves deprecate the use of their .NET > Connector (because it is based on Framework 1.1) and advise the use of > web > services. > > We have an opportunity to interface our e-recruitment package but are > looking for someone to guide us on answering some technical questions > in an > "invitation to tender" with a view to paid work if we get the job. > > Anyone shed any light? > > Mike Pitcher
From: Mike Pitcher on 18 Mar 2010 08:00 On 17 Mar, 21:10, "Geoff Schaller" <geo...(a)softxwareobjectives.com.au> wrote: > Mike. > > We haven't done work on SAP but we do work with web services. A lot. > Generally it is the way to go because it completely removes version > issues to do with underlying OS and frameworks. It also allows the owner > of the WS to upgrade and change their frameworks at will. There is > always a small performance hit with a WS in that it needs to spin up > after going to idle but beyond that, they are a lot easier to implement, > deploy and utilise. > > For example, MS SharePoint and Reporting Services both have an object > model you can use from code but they also both have and encourage > developers to use their web service interface. That way they can change > their object design from version to version without affecting the > delivered interface. If you use the object model directly, you need to > change your code. > > And ws are nice because (at least with VS) you get the class code to use > the ws for free - it self generates. With VO we build our ws wrapper > into a small but simple COM object and use that COM object in VO. We > could do all the soap stuff direct from VO but it is messy, slow to > develop and complex to maintain. All that XML parsing and constructing > is just a pain. > > So I reckon you should go for it. > > Geoff > > "Mike Pitcher" <mike_no_spam_plea...(a)pamuk.demon.co.uk> wrote in message > > news:675f92b6-de11-431b-a7fe-d2ef9a181381(a)q16g2000yqq.googlegroups.com: > > > > > Has anyone actually interfaced with SAP HR? > > > We have been told that SAP themselves deprecate the use of their .NET > > Connector (because it is based on Framework 1.1) and advise the use of > > web > > services. > > > We have an opportunity to interface our e-recruitment package but are > > looking for someone to guide us on answering some technical questions > > in an > > "invitation to tender" with a view to paid work if we get the job. > > > Anyone shed any light? > > > Mike Pitcher- Hide quoted text - > > - Show quoted text - Thanks Geoff. We'll be doing it from ASP.NET (C#) so the VS toolset will come in handy. Would you write the Web Services for SAP or would you get a SAP specialist to do it?
From: Geoff Schaller on 18 Mar 2010 18:23 Mike, > Thanks Geoff. We'll be doing it from ASP.NET (C#) so the VS toolset > will come in handy. Would you write the Web Services for SAP or would > you get a SAP specialist to do it? My understanding is that SAP were going to provide them as a way of replacing their current API - or do you believe something else? WS are a far superior way to provide connectivity, except in performance terms (they sometimes can be a tad slower to kick off) but if it were to be you writing the ws then you've gained nothing because the ws needs the API. That is version dependent so you are back at ground zero. Somehting has to use the object model APi at some point. It is either you or the ws. So see if they are going to supply the connectivity via a ws. And if you were to write it, SELL IT TO THEM FOR BIG BUCKS! <g> Geoff
From: Mike Pitcher on 19 Mar 2010 11:55
On 18 Mar, 22:23, "Geoff Schaller" <geo...(a)softxwareobjectives.com.au> wrote: > Mike, > > > Thanks Geoff. We'll be doing it from ASP.NET (C#) so the VS toolset > > will come in handy. Would you write the Web Services for SAP or would > > you get a SAP specialist to do it? > > My understanding is that SAP were going to provide them as a way of > replacing their current API - or do you believe something else? > > WS are a far superior way to provide connectivity, except in performance > terms (they sometimes can be a tad slower to kick off) but if it were to > be you writing the ws then you've gained nothing because the ws needs > the API. That is version dependent so you are back at ground zero. > Somehting has to use the object model APi at some point. It is either > you or the ws. > > So see if they are going to supply the connectivity via a ws. And if you > were to write it, SELL IT TO THEM FOR BIG BUCKS! > > <g> > > Geoff Done a bit more research and consulted in the SAP forums ... Web Services are now the recommended way as far as SAP is concerned. The whole of the latest release (ECC 6) is based on a service oriented architecture and any extensions are written in Java using their NetWeaver Development Studio. Hence any web services would be developed using the NetWeaver DS to exploit what is - apparently - a well-documented API. It could even be that some of the web services we need are already available to support the integration of SAP's own e- recruitment package. Thanks for all interest shown. |