However, BSPs are more or less limited to a program that runs within the ABAP stack of a specific SAP application server. Certainly you could use registered programs and RFC destinations to hook to an external application, but I believe there is an easier way to do this. Used in conjunction with open source frameworks such as Struts and Tapestry, the JCo Java connector can hook to any and all exposed RFC/BAPI interfaces. In this way, JCo acts as a system-to-system bridge between an external application and the SAP server itself. You can build reusable Java services that can allow access to an atomic set of RFC interfaces by a variety of external applications. With the industry-wide move towards SOA (Services Oriented Architecture), the JCo connector sits in the perfect position to let you build Java-based components that can be accessed by applications you build, both now and in the future.
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