Bill,
Some questions about JCo. Are you using JCo 3.0?
the easiest way would be to use single, just open the connection with the Jco commands and close it when you are done.
I assume you are doing this through JCoDestinationManager.getDestination(). This seems slow to do it each time, so creating it once and storing it for later access looks more attractive.
If you have a real high call volume like hundreds of calls per hour, you can use pooled connections which will open a pool of threads to the database and you grab one and do you stuff and release it. That's what we use here to access SAP with the SAPJCO packages.
That looks more interesting. Are you creating the JCoDestination in your first custom element - perhaps a StartClass - and storing it on the Session structure? With JCo 3.0 it will make them pooled if you set JCO_POOL_CAPACITY.
I've got some JCO examples if you get stuck.
I would not say I am stuck yet, but I would like to exchange some information. Those examples sound attractive.
(a) Which version of JCo?
(b) Did you use the file-based (default) DestinationDataProvider or did you implement your own? If you used the default, where did the file go?
(c) Did you have any issues with the location of the JCo JAR or DLL
(d) Did you have to make any stateful calls?
Regards,
Geoff