That depends on what type of application you are building and who your target users are. If you are building an Intranet application where all your internal users have SAP user IDs, then named JCo connections are the way to go. If you need to deploy your application to a larger audience, especially on the Internet, then you should use JCo's connection pooling combined with a single generic user ID. If you need to switch this generic user to a named user on the fly, see my tip this month for enabling a user switch in SAP.
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.