First we need to create a XA thin JDBC datasource in the WLS console of the OSB Server. Go to deployments in the WLS Console of the OSB Server, where we select the Db Adapter deployment.
Go to Outbound Connection Pools Tab under Configuration and select the already created connectionfactory and press New.
Well, embarrassingly enough it turns out that the actual JNDI Binding name is eis/Ftp/Ftp Adapter and not eis/ftp/Ftp Adapter (upper case F) as proposed by I wonder how such a blunder could take place in JDeveloper...
Please create a Service Request with Oracle Support. JCABinding Activation Agent.activate Endpoint(JCABinding Activation Agent.java:340) at impl.
I have created a FTP Adapter in JDeveloper 188.8.131.52 and imported in OSB.
IBM Web Sphere Application Server provides periodic fixes for the base and Network Deployment editions of release V8.5.
The following is a complete listing of fixes for V8.5 with the most recent fix at the top.