Thursday, November 12, 2015

Issues in code migration from SOA 11g to SOA 12c


Issue 1:

Expected behaviour while migrating files with extension .componentType in 11g is merged with composite.xml

This doesn’t happen with few projects.

Resolution: Manually copy content of .componentType to composite.xml

Coloured content is part of .componentType file, should be copied to composite.xml

<component name="Check" version="1.1">
    <implementation.bpel src="Check.bpel"/>
     <!-- Paste here content of componentType file -->
    <property name="bpel.config.transaction" type="xs:string" many="false">requiresNew</property>
    <property name="bpel.config.oneWayDeliveryPolicy" type="xs:string" many="false">sync</property>
  </component>

 
Issue 2

Rename value of adapter from DB Adapter to db and JMS Adatper to jms in .jca files
 

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

 
Posted by at

9 comments:

  1. UnknownMarch 2, 2016 at 2:28 AM

    Even after correctly resolving both the issues, the composite.xml file of the project is not able to find the referenced objects and also giving the incorrect namespace definition errors for jca files.

    ReplyDelete
    Replies
    1. BajaranglalMarch 4, 2016 at 12:24 AM

      Can you post exact errors

      Delete
    2. UnknownMarch 6, 2016 at 10:06 PM

      composite.xml is showing warnings for 3 things:
      1. The bindings of the BPEL Process client, in which we have to specify the port, is showing warning that "Reference BPELProcess not found" and its callback (as I was constructing an async process) is showing warning "Reference bpelprocess_client_ep not found".

      2."Incorrect namespace definition for BPEL/BPELProcess.bpel"

      3."Incorrect namespace definition for Adapters/jmsReference_jms.jca"

      Delete
    3. UnknownOctober 21, 2016 at 6:55 AM

      Did you ever solve this? I am seeing exactly the same problem

      Delete
    4. BajaranglalOctober 21, 2016 at 7:03 AM

      Yes

      Delete
    5. kummiFebruary 13, 2017 at 10:53 PM

      Hello Manisha,

      Can you please check, whether you have established the connections to MDS from Jdeveloper?
      Please paste your adf_config.xml file here.

      Thanks
      Siva

      Delete
  2. AshwinOctober 13, 2016 at 1:29 AM

    Great Blog.

    ReplyDelete
  3. BajaranglalOctober 21, 2016 at 7:02 AM

    Yes

    ReplyDelete
  4. RajJune 14, 2017 at 11:09 AM

    What was your approach to solve the this error..
    1. The bindings of the BPEL Process client, in which we have to specify the port, is showing warning that "Reference BPELProcess not found" and its callback (as I was constructing an async process) is showing warning "Reference bpelprocess_client_ep not found".

    ReplyDelete

Subscribe to: Post Comments (Atom)