Oracle SOA Suite 12c: Build Composite Applications Ed 2 — Lesson 3: Business Rules, Human Workflow, and Fault Handling

Technical Scope

• decision services, dictionaries, rulesets, facts, and rule testing
• human tasks, participants, outcomes, notifications, and escalation
• fault policies, catch and throw, compensation, retries, and rejected messages
• long-running process state, exception ownership, recovery route, and business audit

Instructor Demonstration

The instructor will analyze and reconcile decision services, dictionaries, rulesets, facts, and rule testing in the context of an order-orchestration composite coordinating services, adapters, rules, human approval, and recoverable transactions. The demonstration captures commands, configuration, transactions, output, logs, plans, or screenshots that prove both the intended behavior and the control boundary.

Applied Workshop

Learners complete a controlled exercise covering human tasks, participants, outcomes, notifications, and escalation and fault policies, catch and throw, compensation, retries, and rejected messages, then introduce a realistic exception involving long-running process state, exception ownership, recovery route, and business audit. They record assumptions, exact steps, expected and observed results, a reversible correction, and the evidence required for operational acceptance.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration, development, analysis, or business-process task.
3. Capture reproducible technical or transaction evidence and compare it with the expected value.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

Acceptance for Business Rules, Human Workflow, and Fault Handling requires the result to be reproducible, traceable to approved inputs, consistent with the relevant Oracle or platform behavior, and supported by checks for security, data integrity, reliability, performance, and recoverability.

• The intended target, scope, and ownership are verified.
• Expected-value and negative-path checks pass.
• Security, reliability, performance, data quality, and support impacts are reviewed.
• Unexpected behavior is resolved before acceptance.

Failure Analysis

When the result differs from expectation, learners isolate the smallest proven cause across decision services, dictionaries, rulesets, facts, and rule testing, human tasks, participants, outcomes, notifications, and escalation, fault policies, catch and throw, compensation, retries, and rejected messages; they avoid speculative production changes, preserve evidence, apply the lowest-risk correction, rerun the test, and document prevention.

Practical Outcome

Complete and defend a validated result for Business Rules, Human Workflow, and Fault Handling with a reusable implementation record or runbook.