Database Reference
In-Depth Information
projects in order to avoid clashes. The common location can be configured on the applica-
tion level by setting the correct path to the shared MDS location
$applica-
tion_home/.adf/META-INF/adf-config.xml
, as follows:
<metadata-store
class-name="oracle.mds.persistence.stores.file.FileMetadataStore">
<property
value="C:\Users\SergeyPopov\workspace\CIO_PE\SCA\MDS"
name="metadata-path"/>
<property value="soa" name="partition-name"/>
</metadata-store>
Of course, you can set in a more clever way as
${oracle.home}/integration/…
Certainly, you could have several metadata stores defined in
adf-config.xml
, each
with its own metadata storage usage namespaces and paths. The storage in the previous
example is file-based, but DB can be used as well with some additional benefits (for in-
stance, faster and more complex runtime queries). So, in general, it looks like some sort of
version control for the following:
• BPEL, BPMN (
http://www.oracle.com/ocom/groups/public/@otn/documents/
• XML-related artifact such as XSLT, XSD, XQuery, any XML fragments, and
XPaths
• Human Workflows
• Business Rules
• Web artifacts such as Portlets, JSF pages, and ADF components
The beauty of this approach is that you can reference and access your MDS-shared arti-
facts using the
oramds:/apps/…
path from any SOA components (BPEL, Mediator,
and so on) for
domain value maps
(
DVM
), policies, XML mappings, and so on. For in-
stance, here is an example of fault policies binding in the SCA project's
compos-
ite.xml
:
<property name="oracle.composite.faultPolicyFile"
type="xs:string"
many="false" override="may">oramds:/apps/
OraSOAPatterns/faultPolicies/fault-
policies.xml
</property>
Search WWH ::
Custom Search