Oracle Integration Cloud: Calling API Endpoints with OAuth 2.0 using the Client Credentials grant

This blog post outlines the configuration of an Oracle Cloud Infrastructure (OCI) confidential application for calling Oracle Integration Cloud (OIC) integrations via REST APIs secured by OAuth 2.0. It details prerequisites, steps for creating a REST-triggered integration, and testing API calls using Postman, focusing on client credentials grant type for authentication.

OCI Integration Fundamentals: Scope Fault Handler

This blog series explores key concepts and functionality within Oracle Integration. This post focuses on fault handling mechanisms to capture and manage integration faults. Global and scope fault handlers are discussed, emphasizing their importance in building robust integrations and promoting centralized error management. Fault handling is crucial for system reliability, enhancing user experience, troubleshooting, system resilience, error logging, and monitoring. The post demonstrates the impact of fault handling through a practical example involving email notifications in integration flow failures.

OCI Integration Fundamentals: Global Fault Handler

This blog series explores key concepts and functionality within Oracle Integration. This post focuses on fault handling mechanisms to capture and manage integration faults. Global and scope fault handlers are discussed, emphasizing their importance in building robust integrations and promoting centralized error management. Fault handling is crucial for system reliability, enhancing user experience, troubleshooting, system resilience, error logging, and monitoring. The post demonstrates the impact of fault handling through a practical example involving email notifications in integration flow failures.

OCI Integration Fundamentals: Versioning

The post discusses the significance of versioning for robust integration lifecycle management, particularly within Oracle Integration Cloud and OCI integration. It highlights semantic versioning, a method of version control for software development that operates on a Major.Minor.Patch model. The post shows through various examples that only one integration can be activated at a time for minor or patch version changes, while multiple integrations can be activated simultaneously for major version changes.