Forum Stats

  • 3,873,729 Users
  • 2,266,635 Discussions


SOA suite composite interdependency

calvinIsMe Member Posts: 23
edited Jun 16, 2013 1:06PM in SOA Suite Discusssions
Hi All,

I am facing a typical problem. We have AIA FP on top of SOA suite 11g ( Here when we call a provider ABCS ( a BPEL composite) from EBS (a mediator composite) rather than providing direct endpoint in the reference we refer the concrete WSDL from MDS. The reason is if after restart all EBS composite becomes disabled as it does not find the reference of provider ABCS (in many cases provider ABCS is loaded after EBS).
This is working quite well for us. But lately I am seeing too many concrete WSDL are loaded in MDS. Where contents are same only endpoints are different.
What is the best practice of managing this? is there any way we can manage the composite loading order during server restart?



  • Lalit
    Lalit Member Posts: 87

    The best practice is to keep the abstract WSDLs in MDS.
    During design time( while creating the EBS in jDeveloper ), refer the WSDL in MDS rather tha giving the endpoint directly.
    In composite.xml, give the actual endpoint.

    Find and example as below in composite.xml of an EBS where the provider name is InvokeIRUSyncProjectListPrimeveraProvABCS( The bold one is actual endpoint and the italic one is the one in MDS).

    <reference name="InvokeIRUSyncProjectListPrimeveraProvABCS"
    <interface.wsdl interface=""/>
    < port=""
    <property name="weblogic.wsee.wsat.transaction.flowOption"
    type="xs:string" many="false">WSDLDriven</property>

    If u follow the process above, there will be no problem during restart of servers.
    Kindly note that always keep the ABSTRACT wsdl in MDS rather than concrete one
  • Lalit
    Lalit Member Posts: 87

    Plz mark ur question as answered and also helpful or correct  so far as my reply is considered

This discussion has been closed.