OIC Common Service to Submit CCS Batch Jobs and Monitor Job Status | Extract file from Oracle CCS to Object Storage

Working...

Objective

Create a reusable common service in Oracle Integration Cloud (OIC) to submit batch jobs to CCS, monitor their execution status, and retrieve the generated files from the Object Storage bucket.

Proposed Flow

Main Integration → Submit Job → Monitor Job Status → Process Output

1. Submit Batch Job

Invoke the CCS API to submit the batch job.

Capture the Job ID returned by CCS.

2. Check Job Status

Use the Job ID to periodically check the job status.

Continue polling until the job reaches a terminal status, such as Success or Failure.

Implement a timeout and retry mechanism.

3. Handle Successful Execution

Once the job succeeds, identify the output files generated by the batch job.

The files are stored in the configured OCI Object Storage bucket.

Retrieve the required file details or file contents for further processing.

4. Handle Failed Execution

Capture the failure status and available error details.

Log the error and notify the calling integration or trigger the required error-handling process.

Architecture Diagram

       Calling Integration

                |

                v

       OIC Common Service

                |

                v

       Submit Job to CCS

                |

                v

        Capture Job ID

                |

                v

       Check Job Status

                |

          +-----+-----+

          |           |

       Running      Terminal

          |           |

          |      +----+----+

          |      |         |

          |   Success    Failure

          |      |         |

          |      v         v

          |  OCI Object   Log Error

          |  Storage      / Notify

          |      |

          +------+

         Poll Again

         While Running

Key Design Considerations

• Reusability: The common service should accept the required job parameters so multiple integrations can use it.
• Polling: Configure an appropriate polling interval and maximum wait time.
• Job tracking: Maintain the Job ID and execution status for monitoring and troubleshooting.
• Object Storage: Ensure the generated files are available in the expected bucket and location.
• Error handling: Handle submission failures, job failures, timeouts, and Object Storage access errors separately.

Expected Outcome

A centralized OIC common service that submits CCS batch jobs, monitors their execution, and handles the generated files in OCI Object Storage based on the final job status.