AIA Artifacts reference problem in JDeveloper using oramds

After finishing up with AIA 3.0 Installation when I starts building my component in JDeveloper on compilation I got errors which were pointing to my bpelprocess.wsdl and from there I come to know that one import is not proper which is actually pointing to AIA Artifact.

<wsdl:import namespace="http://schemas.oracle.com/bpel/extension"
              location="oramds/apps/AIAMetaData/AIAComponents/UtilityArtifacts/RuntimeFault.wsdl"/>

Solution

1.Check if the connection to MDS repositery is Created and if not then create a database connection to connect to the repository with either DEV_MDS or equivalent user.

2. Check if you have already created SOA-MDS connection (from resource palette) If not then create a new SOA-MDS connection. Make sure it uses the DB connection in step1 and also the partition is soa_infra. as by default its not soa_infra.

3. Now check for successful connection and installation of AIA Components by browsing AIAComponent files from MDS. These will be shown under /Apps/MetaData.

4. The last and very important step is to update adf-config.xml file in application home of your Jdeveloper(directory where .jws file exists). This will be used at design time to access files from MDS using oramds protocol. This is located in directory named %APPLICATION_HOME%/.adf/META-INF.
    
Add following line in adf-config.xml

      <metadata-namespaces>

          <namespace metadata-store-usage="mstore-usage_3" path="/apps" />

      </metadata-namespaces>

     <metadata-store-usage id="mstore-usage_3">

        <metadata-store class-name="oracle.mds.persistence.stores.db.DBMetadataStore">

         <property value="DEV_MDS" name="jdbc-userid" />

         <property value="welcome1" name="jdbc-password" />

         <property value="jdbc:oracle:thin:@hostname:port:sid" name="jdbc-url" />

         <property value="soa-infra" name="partition-name" />

     </metadata-store>

     </metadata-store-usage>

After updating file now you can recompile and this time you will surely end up with no errors.

You can now start accessing the artifacts like WSDLs, XSDs etc using oramds. 

eg:oramds/apps/AIAMetaData/AIAComponents/UtilityArtifacts/RuntimeFault.wsdl

MDS-01330: unable to load MDS configuration document

After successful installation  of SOA(11g) 11.1.1.5 on Oracle XE when I started the managed server I faced following exception which makes me worried.... and kept on thinking for few minutes ....do I need to reinstall everything but thanks God I got a solution.

I hope this helps to all who faced such an issue.

Exception

oracle.mds.lcm.exception.MDSLCMException: MDS-01330: unable to load MDS configuration document

MDS-01329: unable to load element "persistence-config"

MDS-01370: MetadataStore configuration for metadata-store-usage "soa-infra-store" is invalid.

ORA-04063: package body "DEV_MDS.MDS_INTERNAL_SHREDDED" has errors

ORA-06508: PL/SQL: could not find program unit being called: "DEV_MDS.MDS_INTERNAL_SHREDDED"

ORA-06512: at line 1.....

Solution   

1. First  of all drop SOA Suite schemas and associated tablespaces using RUC. 
2. Then go to command line (cmd) and set environment variable RCU_JDBC_TRIM_BLOCKS=TRUE
3. Run RCU again to re-create the SOA Suite schemas and tablespace

Now restart  server and this time there will be no error associated with "MDS-01330: unable to load MDS configuration document"