One major concern when using JCo is simply that of SAP system resources. The SAP application server has a limited number of dialog users that can be allocated for use across the enterprise. Because JCO uses a synchronous RFC call to connect to SAP, it consumes a work process. If these connections are not carefully managed, you could wind up eating up every available work process, depending on the level of traffic your application gets. See my tip on connection pooling with JCo at SearchSAP.com.
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