1. Objective
In Oracle Integration Cloud (OIC), changing the tracing level for integrations individually can be time-consuming, especially when multiple projects are involved.
To simplify this process, we can create a common reusable service that updates the tracing level of all activated integrations across selected OIC projects.
The service supports three modes:
- AUDIT – Enables audit-level tracing.
- DEBUG – Enables detailed payload tracing for troubleshooting.
- PRODUCTION – Disables payload tracing to minimize unnecessary logging.
The solution uses two integrations within an OIC project: Main and Child.
2. High-Level Architecture
- Scheduler / Adhoc Trigger: Input: Execution mode, project names (adhoc), and tracing level
- Main Integration: Determines the project list based on execution mode
- Adhoc Uses comma-separated project names from the input
- Scheduled Fetches project names from the lookup
- Child Integration:
- Retrieves integration details for each project
- Update Tracing Level: Processes each activated integration using the requested tracing level
3. Lookup Configuration
Maintain the project names in an OIC lookup. No SFTP path is required.
Project Name
Customer_Utilities
Finance_Utilities
HCM_Utilities
The Main integration reads this lookup only during scheduled execution. During adhoc execution, it uses the project names provided as input.
4. Main Integration
The Main integration orchestrates the entire process.
Processing steps:
- Receive the execution mode and requested tracing level.
- Check whether the execution is adhoc or scheduled.
- For adhoc execution, accept comma-separated project names and split them into individual project names.
- For scheduled execution, retrieve project names from the lookup.
- Iterate through the project list.
- Invoke the Child integration for each project, passing the project name and tracing level.
Example adhoc input
Execution Mode : ADHOC
Project Names : Customer_Utilities,Finance_Utilities
Tracing Level : DEBUG
For scheduled execution, the project names are obtained directly from the lookup.
5. Child Integration:
The Child integration is responsible for retrieving integration details and updating tracing settings for each project.
Processing steps:
- Receive the project name and target tracing level from the Main integration.
- Call the OIC Factory REST APIs to retrieve the integrations belonging to the project.
- Retrieve integration details, including activation status and available version information.
- Identify activated integrations.
- For each activated integration, invoke the appropriate supported API operation to update its tracing configuration.
- Map the requested tracing level to the corresponding tracing flags.
- Handle individual failures and continue processing the remaining integrations wherever possible.
Note: you can follow below blog . Here we have shown how to get project lists from lookup and how to get integration list for each project.
Tracing-level mapping
The following mapping reflects the approach shown in the provided XSLT screenshot.
The exact flag values should be validated against the API operation and OIC release being used.
API used to update tracing level:
API - /ic/api/integration/v1/integrations/{Integrationld|Version}?enableAsyncActivationMode=true&integrationInstance={ServiceInstanceName}
Security - Oauth2.0
Request Body -
{ "tracingEnabledFlag": true, "payload TracingEnabledFlag": true, "replay": { "canReplay": false }, "payload": {"validate": false }}
Headers - X-HTTP-Method-Override: PATCH
Response -
{ "apiDeploymentInprogress": false, "compatible": false, "links": [], "lockedFlag": false, "payload": { "validate": false }, "payload TracingEnabledFlag": true, "replay": { "canReplay": false }, "scheduleApplicableFlag": false, "scheduleDefinedFlag": false, "tempCopyExists": false, "totalEndPoints": 0, "tracingEnabledFlag": true}
Screnshots for Updating Tracing level:
6. Error Handling and Logging
- For better operational visibility, implement the following:
- Log the project name and integration name being processed.
- Track successful and failed tracing-level updates.
- Handle API errors, authentication failures, and integrations that cannot be updated.
- Continue processing other integrations when an individual update fails.
- Generate a summary with total integrations processed, successful updates, and failed updates.
7. Benefits
- Centralized management: Update tracing levels across multiple OIC projects from a single service.
- Reusable design: Support both adhoc and scheduled execution.
- Reduced manual effort: Avoid changing tracing settings for each integration individually.
- Flexible configuration: Manage project names through a lookup and pass the target tracing level at runtime.
- Improved monitoring: Track update results and identify failed operations.
Conclusion
The Main–Child integration pattern provides a reusable way to manage tracing levels across OIC projects. The Main integration determines the projects to process, while the Child integration retrieves their integrations and updates the tracing configuration of activated integrations.
This common service helps OIC teams switch between audit, debug, and production-oriented tracing with minimal manual intervention.
