Websphere6 JNDI DataSource

[Henry Lowell]

I am working on a project that requires Websphere6 and no one on the project has any experience with it. So we are learning as we go along. We'v setup a JDBC Resource to Oracle and we can test the connection successfully from within the console.

However, when we deploy our application via the console, we get the following error message:

ADMA0115W: Resource Assignment of name jdbc/pool/oracle/app and type javax.sql.DataSource, with JNDI name jdbc/pool/oracle/app is not found within scope of module App with URI app.war,WEB-INF/web.xml deployed to target WebSphere:cell=kvmlvwebd02Node01Cell,node=kvmlvwebd02Node01,
server=server1+WebSphere:cell=kvmlvwebd02Node01Cell,
node=webserver1_node,server=webserver1.

Rather than trying to have someone step me through the process of getting this right and trying to explain how we have done things, I was wondering if anyone knew of kind of a step by step guide to getting this kind of thing working. I've been through countless docs from IBM's web site and can't seem to find anything about this process in a centralized location.

Thanks for any information.

[kapil patel]

Hi Hanry,

Please if you find any good material for the same. provide me. I am in the same boat. I do not find specific document with some good examples to start with (some application with database examples) and process

Any start up material for a new bee to webspere application

best regards,
kapil

[Scott Selikoff]

Just a thought, but have you thought of bringing on a websphere expert? Problems like the ones are you experiencing a dime a dozen and trying to trapes through websphere without an expert is often painful.

[Henry Lowell]

Originally posted by Scott Selikoff:
Just a thought, but have you thought of bringing on a websphere expert? Problems like the ones are you experiencing a dime a dozen and trying to trapes through websphere without an expert is often painful.

Yes, we've been trying to contact someone at IBM for a week now. They are in no hurry to return our calls.

[Scott Selikoff]

Originally posted by Henry Lowell:
Yes, we've been trying to contact someone at IBM for a week now. They are in no hurry to return our calls.

Did you try waving a couple of saw bucks around?

[Henry Lowell]

Originally posted by Scott Selikoff:


Did you try waving a couple of saw bucks around?

We pay for support so, yea. We finally got a hold of someone yesterday at around 4:50pm. We had to email them a trace log and several details about our setup. They said they would get back to us in an hour. We are still waiting for the call back. :roll:

[Henry Lowell]

BTW, if anyone else is following this, the initial error went away after we installed all the updates and patches to Websphere 6. However, we get a NamingException thrown because it can't find the JDNI name we have specified. So that is the latest on the support call.

[Hara Totapally]

Do you still have the problem? I have been working with WAS4.x, WAS5.x, and WAS6. Based on the problem you described it appears that the scope of the datasource is not properly defined or you are not using resource reference mapping in the deployment descriptor. Hope this helps.

[Vijay Rathorre]

Hi

Have you provided naming.jar in the classpath. If its not there then pls provide them there.

Thanks!

[Hara Totapally]

including naming.jar etc would be taken care by WebSphere.