MDS – Meta Data store facilitates greater re-use of SOA artifacts such as XML Schemas, EBMs, WSDLs, DVMs, Fault Policies, Rule repositories and Service Data Objects (SDOs) among others.
Here we are going to discuss how to use Database based MDS for storing application specific artifacts mentioned above.
Each MDS repository can have multiple partitions. Partitions are logical separations in the tables to enable metadata from different applications to co-exist in the same physical repository schema without conflicting with each other. We can edit partitions in a repository using EM console or WLST commands.
Following SOA 11g MDS lesson, if you want to confirm whether SOA Metadata has been successfully deployed, here is how you can do it. The deployed SOA metadata will be available through soa-infra MDS partition on the server.
Step1: Create database connection to MDS schema.
File –> New –> Connections –> Database Connection
Create a DB connection to MDS schema, in my case DEV_MDS.
Step2: Create MDS connection to soa-infra partition.
Create File –> New –> Connections –> SOA-MDS Connection
Create MDS Connection
SOA Suite 11gR1 has a provision for sharing SOA artifacts through MDS – Meta Data Store. This facilitates greater re-use of SOA artifacts such as XML Schemas, EBMs, WSDLs, Fault Policies, Rule repositories and Service Data Objects (SDOs) among others. MDS can be file-based or database-based. Here are the steps to create and use file-based MDS in JDeveloper.
MDS is created under <jdeveloper-home>/integration/seed directory. Default folder “soa” is used to store common system soa artifacts. All custom artifacts are supposed to be stored under a folder called “apps”, since this folder already exists in server.