1 Reply Latest reply on Dec 10, 2010 3:58 AM by 687626

    JCA Resource Adapter Location error

      Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'SOSAppADPSelect' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. SOSSamplePrj:SOSAppADP [ SOSAppADP_ptt::SOSAppADPSelect(SOSAppADPSelect_inputParameters,EmployeeCollection) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='jdbc/SOSConnDSXA'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to jdbc/SOSConnDSXA. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.

      I have created this jdbc/SOSConnDSXA in weblogic server i deploy the BPM SOA application into the server. when i run. its giving me this error. in one of the forum they have suggested giving the same datasource name and jndi name, even i tried with it, still the same. do i need to package jca rar file into earfile. where do i get the oracle jca rar file.
        • 1. Re: JCA Resource Adapter Location error
          What you specify in the connection-factory element of the jca binding is NOT the name of the data source to be used. Instead it is the name of the adapter's connection pool instance which is used to connect to the underlying EIS.
          This connection pool is configured in WLS Console ---> Deployment --> <Resource Adapter> (e.g. DB Adapter) --> Configuration --> Outbound Connection Pools --->
          Here you will see the the connection pools grouped by the adapter's connection factory. Exapnd the connection factory instance to list all the outbound connection pools available. Here you will have to configure a neww pool with the name ''jdbc/SOSConnDSXA' ( same name used in the <connection-factory> element: location.
          Once you create a new pool, you will find here the option to specify the name of data source to be used which you will have to configure.
          1 person found this helpful