Important restrictions surrounding the use of SAP's JCo connector

Important restrictions surrounding the use of SAP's JCo connector

In general terms, which are the most important restrictions when using the Java Connector for SAP and Java RFCs for SAP?

    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

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.

This was first published in July 2005