An Introduction to Oracle Fusion – a Solid Foundation for Service Inventory - Applied SOA Patterns on the Oracle Platform - page 131

follow the Rule Centralization too rigorously. The Rule Centralization must be strictly ob-
served for rule development, authoring, and testing, but physical implementation can be
divided between frameworks and application layers depending on the rulesets' complexity.
As any centralization, the rule centralization can implement the single point of failure and
definitely affects the Service Autonomy principle negatively, taking away business logic
(or part of it) from the business service. However, the last bit is the whole idea of increas-
ing business agility and Composability, and there are numerous positive customer use
cases where Oracle RE has been implemented in mission-critical, online-fraud prevention
and money laundering detection applications that handle and scan billions of transactions
or records daily. Thus, there are no doubts that Oracle RE can provide fast performance
and the highest level of reliability.
In general, Oracle RE is a standalone Java application that provides a very comprehensive
SDK and API for the rules' utilization from any element of infrastructure: DB or OSB.
Even if we do not have a rule-related activity for the request and response pipes in OSB, it
is quite possible to implement rules using Java calls on the RE API. Oracle rules can be
expressed by Rule Language ( RL ), which is a subset of Java and is relatively easy to use.
Oracle DB 11 g has packages that present built-in rule engine functionality; primarily,
DBMS_RULE_ADM and DBMS_RULE .
Oracle transformation and translation engine
As XML is the core standard in service-oriented computing, common to all frameworks,
the last but not least shared technical component discussed in the Oracle SOA Foundation
- runtime backbone section is Oracle XML Development Kit—a set of tools, utilities, and
modules, bundled with Oracle DB, JDeveloper, OSB, and SOA Suite. All operations with
XPaths, XQueries, XML nodes, XSDs, and XSLTs are possible because of the XDK func-
tions. Some core functionalities related to the latest versions of XML standards are listed
here:
• The JAXB-compliant XML class generator to generate classes from DTDs and
XML schemas on runtime and design time
• The DOM v 3.0 and SAX-compliant XML Parsers, full support for JAXP 1.3 in-
terfaces, and implements and access XMLType in Oracle DB
• XSLT v 2.0 processors for transformation or the rendering of XML
• XML schema processors for runtime and design time schema validation
• XML SQL utility, essential for XDB to convert SQL queries into XML
All core XML libraries are associated with an SOA project upon creation, but you can al-
ways verify the existing libraries or add new ones following Project Properties | Librar-