" BUILD FAILED" with "ORABPEL-12517 AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error." and "ORABPEL-12529...due to Missing class" when Deploying a BPEL Process via JDeveloper (Doc ID 1289980.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle(R) BPEL Process Manager - Version 10.1.3.1 to 10.1.3.5.0
Information in this document applies to any platform.
***Checked for relevance on 26-Jun-2013***

Symptoms

When deploying a BPEL Process via JDeveloper, you see the following:

[deployProcess] Deploying process <PATH2PROJ>\output\<myProcess>.jar

BUILD FAILED
<PATH2PROJ>\build.xml:79: A problem occured while connecting to server "domain.com" using port "80": <myProcess>.jar failed to deploy. Exception message is: Could not initialize activation agent.
An error occured while initializing an activation agent for process "<myProcess>", revision "1.0".
Please ensure that the activation agents are configured correctly in the bpel deployment descriptor (bpel.xml).
oracle.tip.adapter.fw.agent.jca.JCAActivationAgent: ORABPEL-12517
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter was unable to activate the endpoint :{} due to the following reason: ORABPEL-12529
ManagedConnectionFactory problem.
Could not instantiate ManagedConnectionFactory oracle.tip.adapter.db.DBManagedConnectionFactory due to:
Missing class: oracle.tip.adapter.db.DBManagedConnectionFactory
Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
Loader: oracle.bpel.common:10.1.3
Code-Source: /<SOA_HOME>/bpel/lib/orabpel.jar
Configuration: <code-source> in /<SOA_HOME>/j2ee/oc4j_soa/config/server.xml
This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
The missing class is not available

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms