Resolve JCA connection error in Oracle EBS to SAP integration with OSB 11g

Doing a Oracle EBS to SAP integration with Oracle Service Bus 11g (OSB) I noticed a strange exception at runtime. During the establishment of a connection to the SAP system via the iWay SAP adapter the following error occurs in the adapter logs:

servicebus:/WSDL/ebs2sap-data-integration/Sap/v2.0/jca/BAPI_ORACLE_SYNCHRO_RESPONSE_invoke [ BAPI_ORACLE_SYNCHRO_RESPONSEPortType::BAPI_ORACLE_SYNCHRO_RESPONSE(input_BAPI_ORACLE_SYNCHRO_RESPONSE,output_BAPI_ORACLE_SYNCHRO_RESPONSE) ] – : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: java.lang.IllegalArgumentException: Adapter ‚MySAP‘ not available. Names are case sensitive.
Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections.

At first glance I suspect a typo or a general error within the connection configuration of the adapter to be responsible for this error. After double checking the configuration I wasn’t able to detect a configuration issue, everything seems to be fine. I restarted the servers, the complete domain – nothing changed, the exception remains.

So I decided to double check the general adapter setup. Walking through all setup steps, I finally discovered the root of all evil: I simply forgot to copy the SAP JCO libraries to the $MW_HOME/user_projects/osb_domain/lib folder. After placing the libraries at the corresponding place and restarting the domain, everything worked as intended. Now the data could be transmitted to SAP without any problems.

Small cause, big effect – it takes me some time to find the root cause of the reported exception, whose message is really misleading in my opinion. I would expect to find something like a ClassNotFoundException, if needed libraries cannot be found in the classpath. But never mind, finally it worked.

I hope I can save you some time with the post, if you are facing similar or the same error, when using SAP adapter in an Oracle Service Bus 11g or Oracle SOA Suite 11g environment.

Kommentar verfassen

Diese Website verwendet Akismet, um Spam zu reduzieren. Erfahre mehr darüber, wie deine Kommentardaten verarbeitet werden.

%d Bloggern gefällt das: