Exception Handling in Oic

Introduction

Oracle Integration Cloud (OIC) is a powerful platform for integrating applications, automating processes, and managing data flows. Exception handling is crucial in OIC to ensure integrations run smoothly, errors are captured gracefully, and systems remain resilient. This blog explores various error handling mechanisms in OIC, including global and scope fault handlers, error management in the console, and practical examples.

Types of Errors in OIC

Errors in OIC can be categorized into recoverable and nonrecoverable types. Recoverable errors allow for resubmission of failed messages, while nonrecoverable ones may require manual intervention or discarding. Common error sources include adapter invocations (e.g., APIInvocationError, ServiceException), runtime execution issues, and integration logic faults.

• Recoverable Errors: Can be resubmitted, such as temporary connection issues.
• Nonrecoverable Errors: Permanent failures, like invalid data formats.

Global Fault Handler

The Global Fault Handler is the last resort for unhandled errors in an integration. It catches faults that propagate from scopes or the main flow. You can configure actions like sending notifications, logging errors, or invoking other services.

In OIC, the Global Fault Handler is automatically available in orchestrated integrations. For example, you can add a notification action to email administrators about the fault details.

Scope Fault Handler

Scope Fault Handlers allow granular error handling within specific parts of the integration flow. Each scope can have multiple fault handlers for named faults and a default "catch-all" handler. If an error isn't handled in the scope, it propagates to the global handler.

Use cases include looping through records where one failure shouldn't stop the entire process. For instance, in a while loop processing multiple items, a scope handler can catch failures for individual items and log them, allowing others to proceed.

Managing Errors in the OIC Console

OIC provides a dedicated Errors page under Monitoring > Integrations > Errors. Here, you can:

• View error details, including messages, activity streams, and payloads.
• Filter by time, integration, error type, or instance ID.
• Resubmit failed messages (for asynchronous flows).
• Discard or abort errors, marking them as non-recoverable.

Best practices: Use filters for quick troubleshooting, monitor activity streams to pinpoint failures, and avoid discarding messages you might need to resubmit.

Examples of Exception Handling

Example 1: Scope Fault Handler in a Loop

Consider an integration with a while loop processing numbers from 1 to 5, invoking an FTP adapter that fails at number 3.

• Without scope handler: The flow fails, and the global handler sends an email.
• With scope handler: Catch the fault, send a specific email, and continue processing other numbers. The integration succeeds overall.

Configuration Steps:

1. Add a Scope action.
2. Inside the scope, add your loop logic.
3. In the fault handler section of the scope, add a notification or logging action.

Example 2: Handling Errors with Fusion ERP Integration

When integrating with Fusion ERP using the ERP Cloud Adapter, catch ServiceExceptions and map them to meaningful faults.

For a SOAP fault return:

    
Example 3: Global Fault Handler for Notifications

    
In the global handler, add a Notification action to email fault details, including error code, message, and stack trace.

Best Practices

• Use scopes for modular error handling to prevent full integration failures.
• Implement fault returns to provide meaningful responses to callers.
• Monitor and resubmit errors regularly via the OIC console.
• Log errors comprehensively for auditing and debugging.
• Test error scenarios thoroughly, especially with adapters like ERP or REST.

Conclusion

Effective exception handling in OIC enhances integration reliability and maintainability. By leveraging global and scope handlers, along with console tools, developers can build robust integrations. For more details, refer to Oracle's official documentation and community blogs.

References: Oracle Docs, A-Team Chronicles, and community blogs on OIC error handling.