Showing posts with label file adapter. Show all posts
Showing posts with label file adapter. Show all posts

Friday, 17 November 2017

OSB 12c FileAdapter : Physical/Logical Output Directory has invalid value BINDING.JCA-11043

Once trying to deploy a OSB FileAdapter service and activating the changes I received the below Error:

Error(s) found in module 'FileAdapterService'.
Invalid JCA transport endpoint configuration, exception: BINDING.JCA-11043
Invalid Interaction parameter.
Invalid Interaction parameter.
Interaction parameter Physical/Logical Output Directory has invalid value {/placeholder}.
Please correct the value of the interaction parameter and redeploy the process.
 at FileAdapter.biz

Cause -
The issue is typically caused by a invalid directory definition in the business service.
Means, the file path that you have defined in the adapter is invalid.

Solution -
Correct the file path definition, check if the path is valid and has the right permissions.


Helpful? Please Comment.

Happy Learning!!

Tuesday, 26 September 2017

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!!

OSB 12c : Dynamic Routing to Business/Proxy Service

Dynamic routing is a kind of  Content-based Routing pattern, which is used when the BusinessService/ProxyService path is required to be de...