1. Developing SOA Applications with Oracle SOA Suite
  2. Getting Started with Oracle SOA Suite
  3. Managing Shared Data with the Design-Time MDS Repository
  4. Introduction to SOA Design-Time MDS Repository Management
  5. Introduction to the Default SOA Design-Time MDS Repository Connection

Introduction to the Default SOA Design-Time MDS Repository Connection

A file-based, SOA Design-Time MDS Repository connection named SOA_DesignTimeRepository is automatically included when you create a SOA composite application. The default directory location is $JDEV_USER_DIR/soamds.

This connection provides the following capabilities:

  • A file-based MDS Repository for use during design time. A database-based design-time MDS Repository is not supported.

  • Any MDS Repository can be browsed.

  • The default repository location can be modified to point to another folder or version control location.

  • All SOA-MDS operations use this SOA Design-Time MDS Repository.

  • A wizard enables you to share design-time artifacts from your SOA project with this MDS Repository, such as WSDL and schema files.

Note:

  • If you add shared data into the SOA Design-Time MDS Repository, and the repository is backed by a version control system, Oracle SOA Suite does not provide any operations to add this data to the version control system. You must add this shared data to the version control system.

  • If you have a Release 11g SOA composite application with a preconfigured SOA-MDS repository (/apps namespace) in the adf-config.xml file, all sharing and consumption operations are performed against the existing repository defined in adf-config.xml.