Oracle Identity Governance 12c: Develop Identity Provisioning Ed 1 — Lesson 1: OIG Provisioning Architecture, Application Onboarding, Forms, and Processes

Technical Scope

• OIG components, orchestration, provisioning, reconciliation, and request flow
• application instances, IT resources, resource objects, process definitions, and forms
• lookup definitions, child tables, mappings, statuses, and account lifecycle
• onboarding requirements, schema mapping, ownership, and design validation

Instructor Demonstration

Demonstrate OIG components, orchestration, provisioning, reconciliation, and request flow within an identity engineering team onboarding a business application for automated joiner-mover-leaver provisioning, reconciliation, approvals, exception handling, and auditable deployment, then capture the exact configuration, command, transaction, report, trace, or code evidence that proves the expected result.

Applied Workshop

Implement a controlled workshop covering application instances, IT resources, resource objects, process definitions, and forms and lookup definitions, child tables, mappings, statuses, and account lifecycle, then test a failure, exception, or business-control scenario involving onboarding requirements, schema mapping, ownership, and design validation.

1. Confirm the environment, identities, data, dependencies, controls, and expected result.
2. Complete the product-specific configuration, development, analysis, or business-process task.
3. Capture commands, configuration, output, logs, transactions, reports, or test evidence.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

The OIG Provisioning Architecture, Application Onboarding, Forms, and Processes result must be reproducible, traceable to approved inputs, and consistent with expected Oracle product or business-process behavior.

• The intended target, scope, and ownership are verified.
• The result is supported by reproducible evidence and expected-value checks.
• Security, performance, reliability, data quality, and support impact are reviewed.
• Unexpected behavior is investigated before acceptance or release.

Failure Analysis

Diagnose issues in OIG components, orchestration, provisioning, reconciliation, and request flow, application instances, IT resources, resource objects, process definitions, and forms, lookup definitions, child tables, mappings, statuses, and account lifecycle, or onboarding requirements, schema mapping, ownership, and design validation without making an unverified production change.

Learners isolate the smallest proven cause, apply a reversible correction, rerun validation, and record the preventive action.

Practical Outcome

Complete a validated implementation or analysis for OIG Provisioning Architecture, Application Onboarding, Forms, and Processes and defend the result with documented evidence.