Thursday, November 22, 2012

AIA/SOA 11g Project: Get rid of oramds error from Jdeveloper

I had a problem while opening the AIA 11g project using JDeveloper, when I opened the composite.xml I got error ‘Failed to find WSDL definition and/or locate WSDL file’. I clicked on details button to get more information and found below error.


- WSDLException: faultCode=PARSER_ERROR: Failed to read wsdl file at: "oramds:/apps/AIAMetaData/AIAComponents/BusinessProcessServiceLibrary/EBF/CommsProcessFulfillmentOrderBillingAccountListEBF.wsdl", caused by: java.io.IOException. : java.io.IOException: oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/apps/AIAMetaData/AIAComponents/BusinessProcessServiceLibrary/EBF/CommsProcessFulfillmentOrderBillingAccountListEBF.wsdl does not exist.



To get rid of these problems follow below steps.

1) Create new SOA application in JDeveloper, It will create below Application Resources.



2) Double click on adf-config.xml and click on Source tab.

3) Add below highlighted tag inside <metadata-namespaces>

<metadata-namespaces>
     <namespace path="/soa/shared" metadata-store-usage="mstore-usage_1"/>
     <namespace path="/apps" metadata-store-usage="dev_mds"/>
</metadata-namespaces>

4) Add below highlighted tags inside <metadata-store-usages>, with your system values and save it.

<metadata-store-usages>
     <metadata-store-usage id="dev_mds">
          <metadata-store class-name="oracle.mds.persistence.stores.db.DBMetadataStore">
          <property name="jdbc-userid" value="DEV_MDS"/>
          <property name="jdbc-password" value="devmds_password"/>
          <property name="jdbc-url" value="jdbc:oracle:thin:@hostname:port:sid"/>
          <property name="partition-name" value="soa-infra"/>
          </metadata-store>
     </metadata-store-usage>
..
</metadata-store-usage>

5) Open any .jpr AIA projects and open the composite.xml file. Now Jdeveloper will refer given MDS repository for all oramds reference and it will open without any error.


If you still facing the problem check your MDS configuration, by creating SOA-MDS connection as mentioned in Task 3 and Task 4 of below Oracle link.

http://docs.oracle.com/cd/E23549_01/doc.1111/e17364/bldgintflows.htm