Working...
Objective
The objective is to retrieve Oracle Integration Cloud (OIC) Gen3 project details and their integrations, identify the highest integration version or retrieve all versions, and export the results to a configured SFTP folder.
The solution uses three scheduled integrations — SCH, MAIN, and CHILD — to support both scheduled processing of configured projects and ad hoc processing of selected projects.
High-Level Architecture
1. Lookup Configuration
Project names · SFTP paths · Processing configuration
2. SCH — Scheduler Integration
Receives adhoc parameters or starts scheduled processing
3. MAIN — Orchestration Integration
Determines the project list and invokes CHILD for each project
4. CHILD — Project Processing Integration
Calls OIC Factory APIs, processes integration versions, and generates output data
5. SFTP Output Folder
Stores project integration details for review and reporting.
Input parameters
Processing Type: SCHEDULE or ADHOC
Project Names: Comma-separated project names for ad hoc execution.
Version Selection: HIGHEST or ALL
Status Filter: Optional status filter, if required.
Processing steps
Receive the input parameters.
For SCHEDULE processing, invoke MAIN with the schedule configuration.
For ADHOC processing, pass the project names, version selection, and status filter to MAIN.
MAIN handles project selection and invokes CHILD for processing.
2. MAIN — Project Orchestration Integration
MAIN determines which projects need to be processed.
Processing steps
Check the processing type received from SCH.
If the type is SCHEDULE, read the configured project names and corresponding SFTP paths from the lookup.
If the type is ADHOC, split the comma-separated project names received from SCH.
For each selected project, invoke the CHILD integration and pass:
Project name or project identifier
Version selection: HIGHEST or ALL
Status filter
Target SFTP folder path
Continue processing the remaining projects and handle individual project failures appropriately.
Invoke the relevant OIC Factory APIs to retrieve integrations belonging to the project, including the available version information.
Apply the requested version selection:
HIGHEST: Select the highest available version for each integration.
ALL: Include all available versions for each integration.
Apply the requested status filter, if applicable.
Map the response into the required output structure.
Write the integration details to a Stage File.
Write the generated file to the configured SFTP folder.
Return the processing result to MAIN, including success or failure details.
Implementation note: Confirm the available version fields and API response structure for your OIC Gen3 environment. Version selection should be based on the actual version values returned by the API, not on string comparison alone.
6. Error Handling and Monitoring
Log the project name and processing type for each execution.
Capture Factory API failures and SFTP write failures.
Ensure one project's failure does not unnecessarily prevent other projects from processing.
Return the final status from CHILD to MAIN.
Generate an execution summary containing the total projects processed, successful projects, and failed projects.
Conclusion
This three-integration design separates scheduling, orchestration, and project-level processing. It supports both scheduled and ad hoc execution, configurable version selection, and centralized SFTP output, making the solution reusable for OIC Gen3 project inventory and version reporting.
No comments:
Post a Comment