Popular Posts

Saturday, September 27, 2025

Activate OIC Integrations as programatcally

How to Activate the Latest Version of an OIC Integration Automatically

How to Activate the Latest Version of an OIC Integration Automatically

In Oracle Integration (OIC), each integration can have multiple versions. When deploying updates, you often need to activate the latest version automatically instead of doing it manually. This blog will guide you through creating an OIC integration that uses REST APIs to fetch the latest version of an integration and activate it with just one call.

🔹 Why Automate Activation?

  • Speeds up DevOps and CI/CD processes.
  • Reduces manual effort and human error.
  • Makes deployments repeatable and reliable.

🔹 Key REST APIs Used

Purpose HTTP Method Endpoint
Get all versions of an integration GET /ic/api/integration/v1/integrations/{integrationId}/versions
Activate a specific version POST /ic/api/integration/v1/integrations/{integrationId}/versions/{version}/activate

🔹 Steps to Build the Integration

  1. Create a new App-Driven Orchestration Integration
    • Name it ACTIVATE_LATEST_VERSION.
    • Add a REST trigger with /activateLatest (POST method).
  2. Call the OIC REST API to Get Versions

    Use the REST Adapter to call the versions API and pass the integrationId (for example: MyIntegration).

  3. Extract the Latest Version

    Use an Assign or Mapper step to filter the highest version from the response JSON.

  4. Activate the Latest Version

    Use another REST Adapter invoke to call the /activate endpoint with the extracted version.

  5. Send Confirmation Response

    Return a response back to the caller with details of the activated version.

🔹 Sample Activation Request


POST https://<OIC_HOST>/ic/api/integration/v1/integrations/MyIntegration/versions/05.01.0000/activate

Authorization: Basic <base64-encoded-credentials>

Content-Type: application/json

  

🔹 Sample Response


{

  "name": "MyIntegration",

  "version": "05.01.0000",

  "status": "ACTIVATED"

}

  
Pro Tip: Instead of hardcoding, make your integration accept integrationId as an input parameter. This way, the same integration can activate the latest version of any OIC integration.

✅ Conclusion

By leveraging OIC REST APIs, you can fully automate the activation of the latest integration version. This approach is highly useful in CI/CD pipelines, automated deployments, and reduces manual dependency in production rollouts. Next time you promote an integration, let OIC activate the latest version for you—automatically!

Saturday, September 13, 2025

Can a Scheduled Integration in OIC return a value?

Using Scheduled Integrations in OIC to Send Back Values

Can Scheduled Integrations in OIC Send Back Values?

Understanding how Oracle Integration Cloud Scheduled Integrations handle values

🌐 Introduction

Oracle Integration Cloud (OIC) offers multiple ways to design integrations—app-driven, event-driven, and scheduled. One of the most common questions developers and consultants ask is:

“Can a scheduled integration send back a value?”

The short answer is: Yes, but with a different approach.

⚡ How Scheduled Integrations Work

A scheduled integration is designed to run automatically at a defined time using an iCal expression (for example, every day at 12:01 AM). Unlike app-driven integrations, scheduled flows do not wait for a request and return a response. Instead, they are self-triggered.

✅ Can It Send Back a Value?

Absolutely. But instead of returning the value to a caller, a scheduled integration can push the value to a target system, database, or file storage. Here are the common ways:

  • Insert or update the value in a database table
  • Send the value via a REST or SOAP API to another system
  • Write the value into a CSV/XML file on FTP or Object Storage
  • Deliver the value as an email notification
Example Use Case:
A finance team needs a daily “Total Voucher Value” pushed to an ERP system at midnight. A scheduled integration can:
  1. Fetch the transactions from ERP/Database
  2. Calculate the total value
  3. Send the result via REST API or drop it into FTP

🔑 Key Differences vs. App-Driven Integrations

  • App-Driven: Waits for a request → sends response back immediately
  • Scheduled: Runs on a schedule → pushes value to a system, not to a caller

🚀 Benefits of Using Scheduled Integrations

  • Automates repetitive tasks
  • Ensures consistency in reporting or reconciliation
  • Works without user intervention
  • Ideal for nightly jobs, batch processing, and compliance reports

💡 Best Practices

  • Use descriptive names for integrations (e.g., Send_Daily_Values)
  • Log all sent values for auditing
  • Handle failures with error hospital and alerts
  • Test the iCal expression carefully before production deployment

🎯 Conclusion

A scheduled integration in Oracle Integration Cloud cannot return values directly like app-driven integrations. However, it is a powerful tool for sending back values to external systems, databases, or storage in an automated way. This makes it a perfect fit for batch processes, reconciliation tasks, and scheduled reporting.

© 2025 Oracle OIC Insights Blog | All Rights Reserved

SQL to Get dates missing in a table for given date range

 WITH all_dates AS (     SELECT DATE '2025-01-01' + LEVEL - 1 AS dt     FROM dual     CONNECT BY LEVEL <= (DATE '2026-01-01...