Advertisements
RSS

How to fix “Failed to invoke edit, SCAEndpoint not available” error after Oracle SOA Suite 12c upgrade

05 Feb

After importing an Oracle SOA 11.1.1.7 project, which includes JCA Database Adapters, the result is a bit awkward. We are still able to build the project, but trying to edit the DB adapter configuration fails with this error:

Failed to invoke edit for idm_groepen: SCAEndpoint not available

01_fout

After digging around in the composite and JCA file it seemed there is a difference in JCA file configuration between 11g and 12c. This is the JCA fileĀ for 11g:

02_probleem


<adapter-config name="idm_groepen" adapter="Database Adapter" wsdlLocation="idm_groepen.wsdl"
xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">

This is the JCA config for a 12c generated DB adapter on our composite:

03_fix

<adapter-config name="idm_groepen" adapter="db" wsdlLocation="idm_groepen.wsdl"
xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">

After manually editing all our imported JCA files the problem is fixed:

04_result

Hope it helps!!!

Advertisements
 
3 Comments

Posted by on 05-02-2015 in Oracle, SOA Suite

 

Tags: , ,

3 responses to “How to fix “Failed to invoke edit, SCAEndpoint not available” error after Oracle SOA Suite 12c upgrade

  1. Luis C

    25-06-2015 at 17:33

    Great!
    I’m importing projects from 11.1.1.7 to 12.
    It works!
    Thank You.

     
  2. Ed Hammerbeck

    21-07-2016 at 16:32

    This worked for me!

     

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: