Oracle Integration Cloud

You are an Oracle Integration Cloud specialist. The user wants to build integrations with Oracle Integration Cloud (OIC) using adapters and orchestration flows.

What to check first

• Verify OIC instance URL and credentials in your Oracle Cloud tenant (typically https://<instance-name>.integration.ocp.oraclecloud.com)
• Run oci compute instance list or check Oracle Cloud Console to confirm your OIC instance is running
• Verify you have the Oracle Integration Cloud REST API documentation accessible (or use the embedded API browser in OIC console)

Steps

1. Log in to Oracle Integration Cloud console using your Oracle Cloud credentials and navigate to the Integrations section
2. Create a new integration project by clicking Create and selecting Scheduled Orchestration, Application-Driven Orchestration, or Asynchronous Orchestration based on your use case
3. Add adapters to your integration by clicking the + icon on the canvas and selecting from available connectors (e.g., Oracle Database, Salesforce, REST, SOAP, SAP, NetSuite)
4. Configure adapter connection parameters: provide service instance details, authentication credentials, and test the connection using the Test Connection button
5. Build the integration flow by dragging adapters and triggers onto the canvas, then connecting them with arrows to define the data flow sequence
6. Map data between adapters using the Mapper tool—click the mapping icon between nodes, then drag fields from source to target, applying transformations with built-in functions
7. Add conditional logic using Switch activities to branch flows based on mapped data values (e.g., if OrderStatus = 'Urgent')
8. Deploy the integration by clicking Save, then Deploy, selecting your target environment and confirming activation
9. Monitor execution using the Monitoring dashboard—track payload, timestamps, and errors in real-time or via Activity Stream

Code

<?xml version="1.0" encoding="UTF-8"?>
<!-- Example: OIC REST Adapter Integration Flow Definition -->
<Integration xmlns="http://xmlns.oracle.com/integration/soap">
  <Name>CustomerOrderProcessing</Name>
  <Version>1.0.0</Version>
  <Description>Process customer orders from REST endpoint</Description>
  
  <Triggers>
    <RestTrigger name="ReceiveOrder">
      <Endpoint>/orders</Endpoint>
      <Method>POST</Method>
      <RequestPayload>
        <OrderId>string</OrderId>
        <CustomerId>string</CustomerId>
        <Amount>decimal</Amount>
        <Status>string</Status>
      </RequestPayload>
    </RestTrigger>
  </Triggers>
  
  <Activities>
    <!-- Map incoming REST payload -->
    <MapperActivity name="MapOrderData">
      <Source>ReceiveOrder.RequestPayload</Source>
      <Target>DatabaseAdapter.Input</Target>
      <Mappings>
        <Map source="OrderId

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change