What are the different ways of communicating with SAP through Java? Which is preferable?
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
There are many different ways to connect to SAP R/3. Your choice depends largely on the type of application you are building. If you are looking to support transparent system to non-SAP system commication, then using the XML document standards of Business Connector (BC) is the tool for you. BC allows you to chain together multiple RFC/BAPI calls in what is termed a pipeline into which you map inbound XML fields using the BC browser.
If you need to provide realtime, client based communication (from a Web page), then JCo is the right connector for you. JCo is a highly optimized Java Native Interface (JNI) that provides quick connectivity into the RFC/BAPI layer.
If you are looking for a more Microsoft-centric solution, check out SAP's COM/DCOM bridge. As you can tell, there are many approachs for connecting to R/3. The right one depends largely on your requirements and internal platform landscape (UNIX, Windows, etc.)
Dig Deeper on SAP Java and J2EE
Related Q&A from Austin Sincock
How to provide an SAP R/3 4.5B application server with a Web service interfacecontinue reading
A reader wants to know how to consume a Web service from an SAP 4.6c R/3 application server.continue reading
Are you a Java/J2EE developer interested in SAP? This expert tip lists the most relevant SAP modules and technologies for you.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.