This content has been marked as final. Show 5 replies
Hi,1 person found this helpful
If you don't have any other defined datasource you can delete the DbAdapter, and deploy it again.
Probably you have a corruption with one of the files.
Thank you, I undeployed the database adapter, and redeployed it. This was helpful for resetting everything to default, but it did not solve the problem with deploying my composite. I still get "unable to complete unload due to null".
If I remove the database adapter from my composite and BPEL, then I can deploy my project to weblogic. If I put the database adapter back into my composite & BPEL, then I get that same error back again.
Does the JNDI need to be set correctly when creating the db adapter in jdev for it to deploy successfully?
Which JNDI do I need to specify when creating the adapter? In WebLogic Admin Console:
under General tab
JNDI Name: xyzConnPool- which is "The JNDI name of the Outbound Connection instance within this group."
Is this what I specify in jdeveloper, or is it some other JNDI?
When you want to use the DbAdapter there is some "preparation" to be made before using it in Jdev (in a SOA composite).
Not sure how much you did already so I'll write the whole preparation you can make manualy.
1 - First you need to create a weblogic data source.
For that you can go in the weblogic admin console (not EM) to :
- Services > Data source
There you can create a Generic data source (for a JDBC connection). (be sure to remember the JNDI name of the data source).
2 - You need to configure your DbAdapter for using the previous data source created
Go to deployment, click on the DbAdater > Configuration > Outbound/outgoing connections
Create a new outbound connection (set a new JNDI name not used already and different from the JNDI name of the data source). Once done, click on it and set the JNDI name of the data source in the xADataSourceName field of the table.
Click on "save"
3 - Redeploy the adapter with the new connection (button update)
4 - In Jdev, open your _db.jca file. Set the adapter outbound connection JNDI name in the file (if it is not already the case)
Note : The DbAdapter should be in "active/running" state (not prepared).
Edited by: mathieu.d on May 7, 2013 1:25 AM
Thank you, that fixed it.
Edited by: JasonSmithy on May 7, 2013 1:38 AM
Then can you check the server side logs ? Maybe there is more information in order to narrow down the issue.
Edited by: mathieu.d on May 7, 2013 1:44 AM