Question

Is there anyone who has used or looked into using Jitterbit as well as BizTalk? If so, what are some pros and cons of each, and which one did you go with as your final solution?

Specifically, I’m looking for SAP integration, but any input would be appreciated.

Answer 1

I’ve done a fair bit of integration with SAP, starting with the old SAP DCOM connector. More recently I’ve been involved in the selection of an integration platform to serve in an Enterprise Service Bus pattern.

We did web service samples to connect to SAP on a number of platforms, including BizTalk, Mule, Netweaver, Webmethods and Tibco. Webmethods won out based on licensing and capability, though BizTalk and Netweaver both had very high marks.

Jitterbit was not part of the evaluation – in fact I had to look it up to be sure I understood your question.

If your goal is just to be able to call an RFC, the .NET SAP connector works well.

If your goal is to expose a web service to wrapper a process in SAP, then BizTalk is good, but I recommend you see if your organization already has netweaver licensed as there are many web services available directly from SAP with no coding.

My recommendation is to avoid Jitterbug and Mule for the enterprise for now – unless Open Source is actually a popular thing at your place of employment. Netweaver and BizTalk are very robust, polished products.

If you are looking for something you can ship easily, then Jitterbug may make more sense. Though generally I’d recommend you define it as a web service call, and look to your customers technology stack for the most appropriate integration technique.

More context of what you are looking to achieve will enable a more accurate answer.