The first step is to build a JCO server, following the examples provided by the JCO API or my book, Enterprise Java for SAP. The JCO server takes import parameters, structures and can execute JDBC code against an external database. This allows you to store data from any source that can execute the JCO server. Inside SAP, you need to build a user exit or scheduled ABAP program that calls an RFC destination, exporting the data you need to save in your external database. When the JCO server is started, it registers itself with the specific RFC destination you created for it. Once registered, any SAP application that can call an RFC destination canm now pass data to your JCO server.
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 interface Continue 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.