SOA 12c DBAdapter : Exception occured during invocation of JCA binding: Could not create/access the TopLink Session.

Recently created a new DataSource and adapter JNDI and when trying to test I got the below error:

Exception occurred when binding was invoked. Exception occurred during invocation of JCA binding: “JCA Binding execute of Reference operation ‘merge’ failed due to: Could not create/access the TopLink Session. This session is used to connect to the datastore. Caused by Exception [EclipseLink-7060] (Eclipse Persistence Services – 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.ValidationException Exception Description: Cannot acquire data source [jdbc/Demo_DB]. Internal Exception: javax.naming.NameNotFoundException: Unable to resolve ‘jdbc.Demo_DB’. Resolved ‘jdbc’; remaining name ‘DemoDB’. You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered not retriable, likely due to a modelling mistake. “. The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.


The solution was simple. Either you can;

1. Cross verify the DataSource name in the adapter JNDI connection pool and make sure to update the DBAdapter.

or

2. Check if your DataSource is targeted to the soa_server. If not, target it.


Helpful? Please Comment.

Happy Learning!!

SOA 12c DBAdapter: Error while validating JCA Reference Binding meta data during composite deployment

What you need to do if you are deploying you DBAdapter service and getting the below error:

Error deploying archive sca_SOADBAdapter_rev1.0.jar to partition "default" on
server soa_server1
HTTP error code returned [500]
Error message from server:
There was an error deploying the composite on soa_server1: Deployment Failed:
Error while validating JCA Reference Binding meta data during composite
deployment.: JCA deployment validation errors for 'Adapters/DBReference_db.jca'.

Check server log for more details.
Error deploying archive sca_SOADBAdapter_rev1.0.jar to   partition "default" on server
soa_server1
Deployment cancelled.
----  Deployment incomplete  ----.
Error deploying archive  file deploy/sca_SOADBAdapter_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)

The possible cause for this issue is that the JNDI being used in .jca is unavailable, incorrect or invalid.

Solution - Create or Correct your JNDI.
Also, Check if your JNDI has the correct DataSource configured and the DataSource test is successful.
If all these are good and you still have the same error, open your DBAdapter configuration and check table imports and settings.


Helpful? Please comment.

Happy Learning!!

SOA 12c FileAdapter : JCA deployment validation errors

What you need to do if you have migrated your 11g code to 12c and you are getting the below error when deploying:

Error deploying archive sca_HelloWorldJCA_rev1.0.jar to partition "default" on server soa_server1
HTTP error code returned [500]
Error message from server:There was an error deploying the composite on soa_server1: Operation failed - Member(Id=3,member:soa_server1, Role=WeblogicServer):Error while validating JCA Reference Binding meta data during composite deployment. : JCA deployment validation errors for 'GetFile_file.jca'
; .  Please see the server diagnostic logs on soa_server1 for details.
 Check server log for more details.

First you will not get any error when you are compiling your code in JDeveloper.

Second this issue can be due to 2 reasons:

1. Your .jca file has a logical or physical directory entry which is invalid (means not a correct path or access permissions is not given to the folder)

Solution - Correct the path or give 777 access to the folder and retry.

2. When migrating your code form 11g to 12c, the resulting composite.xml has new empty property entries for the the logical directory like below:

<binding.jca config="GetFile_file.jca">
..
<property name="LoadDirectory" override="may" many="false" type="xs:string" source=""></property>
..
</binding.jca>

Solution - Remove the unwanted property and retry.

Helpful? Please comment.

Happy Learning!!