cancel
Showing results for 
Search instead for 
Did you mean: 

WAS JCO component

Former Member
0 Kudos

Hi,

is there any JCO component we can define in WAS 6.4 like JDBC DataSource to use in J2ee applications. if yes how can we do that to support Connection pooling. if no then, is implimenting programatically is the only why to implement connetion pooling.

Thanks & regards

Ashutosh

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

I guess you can use SAP Java Resource Adapter for that. It is a JCA-based (Java Connector Architecture) implementation of JCo interfaces and is designed for access to SAP systems from J2EE-compliant applications. For more information, see the corresponding <a href="http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5caa85b11d6b28500508b5d5211/frameset.htm">documentation</a>.

Hope that helps!

Former Member
0 Kudos

Hi Ivaylo Ivanov

you are right as per the document. I can use JCA to use server implemented JCO. I am trying to configure JCA as per the link

<i>http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5caa85b11d6b28500508b5d5211/frameset.htm</i>

but while my java program which is a servlet I am getting the following error

<i>com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name webContainer/applications/sap.com/jcotestEA/jcotest/java:comp/env/eis/MyConnFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "eis/MyConnFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "eis/MyConnFactory" is defined is not deployed or not started.]

</i>

I have seen the JNDI tree using j2eee admion tool. this name exists in the same path as provided.

Can anybody help me how to resolve this error.

Thanks & Regards

Ashutosh

Former Member
0 Kudos

Hi,

Unfortunately, I've no particular idea why you are not able to lookup the connection factory. That's why I'll just give you some hints where you might be going the wrong path:

1. (I know it might be stupid, but I prefer to start with the obvious!) Did you deploy and configure the SAPJRA resource adapter on the Web AS? See thread for that.

Good luck!