Database Reference
In-Depth Information
The Oracle Rule Engine
For many OFM developers,
Rule Engine (RE)
is visualized as a decision component in
the SOA suite, shown as follows:
Indeed, this is the most common way of utilizing the power of business rules in composite
applications, expressing very complex conditions, combined in collections (rulesets). The
Decision component is the method of exposing the Decision services. The Decision com-
ponent is an SCA component that can be used within a composite wired to a BPEL com-
ponent or exposed directly as Service. In addition, the Decision components are used for
the dynamic routing capability of Mediator and Advanced Routing Rules in Human Work-
flow, Case Management, and BPM. The Decision component can be seen as a web service
wrapper for the decision function and ultimate endpoint for a subset of the rule dictionary.
The decision function in the rule dictionary can be presented as rules or decision tables.
This dictionary, acting as a central rule repository, contributes to the implementation of
the Rule Centralization SOA pattern.
Business Rule Designer is the frontend to define and author various rules in SOA Suite
and combines them in rulesets. The following screenshot demonstrates how a set of condi-
tions based on Facts extracted from the message XSD (imported from message header ele-
ments, but also can be from Java class or created explicitly in designer) can be linked to a
concrete action; in this case, the execution of a certain business process related to the user
request. The following screenshot gives a view of Business Rule Designer:
Search WWH ::
Custom Search