Database Reference
In-Depth Information
<property name="oracle.composite.faultBindingFile"
type="xs:string"
many="false" override="may">oramds:/apps/
OraSOAPatterns/faultPolicies/fault-
bindings.xml
</property>
MDS is actively used not only in JDeveloper in conjunction with SOA Suite, but also in
the Oracle ADFs MVC patterns' development, the WebCenter Web 2.0 development plat-
form, and Fusion applications. Fusion Middleware control provides complete manage-
ment capabilities for MDS repositories such as registration, deployment artifacts, migra-
tion, exporting, labeling, versioning, backups/recovery, and deletion. The same manage-
ment functionality is also available through WLST.
Despite all the brilliant MDS repository's design and runtime features (even Design Time
@ Runtime lookup/discovery capabilities), it tends to be more of a developer's tool than
the enterprise service lifecycle support suite. To some extent, it can be seen as a UDDI,
which is also brilliant for Service metadata description and discovery. However, it can
mostly be viewed through programming interfaces built into UDDI APIs, providing a
little support for metadata classification, taxonomy, analytics, and end-to-end control.
Oracle has Enterprise Repository to cover all these requirements. OER is a part of Oracle
SOA Governance Suite, natively connected to MDS, UDDI instances, and the developer
tools. It would be quite difficult to find a single element of service lifecycle that is not
covered by OER. Please see the following list that details how OER covers common SOA
Governance requirements:
• First is Code Compliance Inspection with automated design-time compliance
evaluation against WS-I interoperability tests.
• Next is the Native Contract support, helping negotiate terms of use between the
service consumer and provider (see the figure under the
Establishing the Adapter
framework
section). Both the technical and SLA aspects of service contract are
covered in great detail. We probably do not need napkin drawings anymore. This
capability together with the Code Compliance Inspection is covered by the AIA
harvester and workbench.
• Once the contract and related Trading partners are defined, every single step of
the service lifecycle can be clearly defined.
• Business and technical policies can be defined and centrally stored in support of
the defined service lifecycle.
Search WWH ::
Custom Search