Oracle Integration Cloud – End-to-End Integration Design & Execution Guide

Oracle Integration Cloud (OIC) provides a powerful, scalable, and low-code platform for connecting applications, automating processes, and orchestrating data flows across enterprise systems. This document presents a comprehensive, step-by-step guide designed to help users understand, configure, and execute an integration workflow from start to finish.

The guide follows a structured 19-step format, where each step offers a clear explanation of its purpose, the actions required, and the impact it has on the overall integration flow. Screenshots and descriptive content illustrate how components such as triggers, loggers, assign activities, mappers, and invokes are configured within the Integration Designer.

Whether you are a beginner learning OIC for the first time or an experienced developer refining your automation practices, this manual provides a practical walkthrough of essential concepts—including initialization, data preparation, runtime visibility, orchestration logic, and monitoring.

By following these steps, you will gain a strong understanding of how integrations are constructed, validated, and optimized inside Oracle Integration Cloud, setting the foundation for building efficient, maintainable, and production-ready workflows.

Supplies

Required Tools & Access

Oracle Cloud account with Integration Cloud (OIC) access
Valid user credentials (username & password)
Permission to create and modify integrations
Access to associated applications (if invoking ERP, HCM, REST APIs, etc.)

Software and Environment

Web browser:
Google Chrome (recommended)
Microsoft Edge
Mozilla Firefox
Stable internet connection
OIC environment URL (provided by the administrator)

Project Assets

Screenshots for each step (19 total)
Input payloads or sample data (if required)
Integration naming and pattern selection plan
Workflow design notes (optional but recommended)

Skills Required

Basic understanding of Oracle Integration Cloud interface
Knowledge of integration concepts: triggers, invokes, mappings, assigns
Familiarity with logging and monitoring tools
Ability to interpret workflow diagrams and data structures

Step 1: Create a New Integration in Oracle Integration Cloud

This step explains how to perform ‘Create a New Integration’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

The process of creating a new integration in Oracle Integration Cloud (OIC) begins inside the Integrations workspace, where all integrations are designed and managed. As shown in the screenshot, the Integrations dashboard initially indicates that no integrations currently exist in the environment. This clean workspace is typical for new projects or newly provisioned environments.

To initiate the creation of a new integration, navigate to the top-right corner of the screen and click the Create button. This action opens a side panel that displays available integration patterns. OIC provides multiple integration styles to suit different business needs. In this case, the two primary options are Application and Schedule.

Application integrations are triggered by incoming events from connected applications.
Schedule integrations run automatically at predefined intervals.

Selecting the desired pattern allows you to begin assembling the workflow. The screenshot highlights the correct navigation and interaction pattern required to start building an integration. This foundational action is essential because it defines the overall structure, triggering mechanism, and execution behavior of the integration you are about to configure. By selecting the appropriate integration type at this early stage, you ensure that subsequent design steps align with the intended business process.

Step 2: Select the Appropriate Integration Pattern

This step explains how to perform ‘Select the Integration Pattern’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

After clicking the Create button in the Integrations workspace, Oracle Integration Cloud (OIC) displays a configuration panel that allows you to choose how your integration should begin. Selecting the correct pattern at this stage is essential, as it determines how the integration will be triggered and executed. The screenshot illustrates two available options: Application and Schedule.

The Application pattern is designed for event-driven scenarios where the integration is initiated when an external system or application sends a request or triggers an event. This is typically used for real-time API-driven workflows, where immediate processing is required in response to application activity.

On the other hand, the Schedule pattern is used when integrations must run at regular intervals or predefined times. This is ideal for batch processes, recurring data transfers, nightly jobs, or any automated workflow that does not depend on external triggers. When you choose the Schedule option, OIC allows you to define the exact frequency, timing, and execution parameters.

By selecting the integration pattern carefully, you ensure that the workflow functions according to your business requirements. This step not only influences when the integration runs but also determines the overall structure of the integration flow inside the designer. Making the correct choice ensures that subsequent configurations—such as triggers, loggers, mappings, and invokes—fit seamlessly into the workflow.

Once the pattern is selected, Oracle Integration Cloud transitions to the next stage of integration creation, where you define the name, identifier, and design components of the workflow. Completing this step establishes the foundation upon which your entire integration will be built.

Step 3: View and Access Existing Integrations

This step explains how to perform ‘View and Access Existing Integrations’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

Once an integration has been created or after any configuration activity, Oracle Integration Cloud (OIC) displays all available integrations within the Integrations workspace. The screenshot shows a newly created integration named FOAS_FIRST_INT_SC, which appears in the list along with critical information such as version number, style, last updated timestamp, and its current status.

The Integrations list acts as the central management interface where developers and administrators can quickly review all ongoing workflows. Each integration entry includes a visual indicator representing its pattern—such as the calendar icon for a scheduled integration. This allows users to easily distinguish between scheduled, application-driven, or event-based orchestrations.

In this interface, OIC also provides several action buttons next to each integration. These options allow you to edit the integration, activate or deactivate it, clone it for new use cases, monitor its runtime behavior, or delete it if no longer required. The presence of the Draft status icon indicates that the integration has been created but not yet activated, meaning it is still in the design phase.

Accessing an integration from this list is as simple as clicking its name. Doing so opens the Integration Designer, where you can configure loggers, mappings, invokes, and other workflow components. This centralized listing makes it easy to navigate between multiple integrations in larger environments, ensuring efficient management of projects and automation workflows.

Viewing the integrations list regularly is also important for tracking progress across development cycles, monitoring versions, and ensuring that updates have been applied correctly. This step provides a clear overview of your integration inventory, helping you maintain structure and organization in your OIC workspace before moving ahead to more advanced configuration steps.

Step 4: Add a Logger Action to the Integration Flow

This step explains how to perform ‘Add a Logger Action’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

After opening the integration in the Integration Designer, the next step is to begin shaping the workflow by adding actions that control how data is processed during execution. The screenshot shows the integration canvas with the Schedule trigger already placed at the start of the flow. To enhance visibility and track execution behavior, Oracle Integration Cloud (OIC) allows you to add Logger actions at any point within the integration.

The Logger action is commonly used to record messages, variable values, timestamps, or custom expressions during runtime. These log entries appear in the activity stream, helping developers and support teams trace how data moves through the integration and detect issues quickly.

In the Actions palette on the right side of the screen, the Logger option is located alongside other powerful tools such as Map, Note, Notification, and error-handling features. By selecting the Logger icon, you can drag and drop it into the integration flow directly beneath the Schedule trigger. This allows you to capture information immediately after the integration begins execution.

The tooltip in the screenshot describes the Logger’s purpose clearly—OIC logs messages to both the activity stream and diagnostic logs, serving as an essential debugging and monitoring tool throughout development. Whether the message is static text or dynamically generated using expressions, the Logger provides transparency into the integration’s behavior at runtime.

Adding a Logger at this stage helps establish a clear audit trail, particularly valuable during testing and troubleshooting. As the integration grows more complex, with additional invokes, mappings, and conditions, these loggers serve as checkpoints that confirm each step is running as intended.

By incorporating the Logger action thoughtfully, you create a strong foundation for monitoring your integration’s lifecycle, ensuring accuracy, transparency, and ease of maintenance throughout the automation process.

Step 5: : Configure the Logger Action

This step explains how to perform ‘Configure the Logger Action’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

Once the Logger action has been added to the integration flow, the next step is to configure it so that it captures meaningful and informative messages during runtime. The screenshot shows the Integration Designer with the Logger component selected, displaying its configuration panel on the right side of the screen.

Configuring a Logger involves defining when it should execute and specifying the message that should be recorded in the activity stream. OIC provides two logging options—Always or When tracing level is set to Audit. Choosing the Always option ensures that the logger fires during every execution, regardless of the tracing level defined at activation.

Within the configuration panel, you will see a text box labeled Logger message. This field allows you to type a custom message or construct a dynamic expression by dragging variables from the left-side input sources panel. The screenshot shows available variables such as startTime, tracking variables, and other schedule-related metadata.

By combining static text with dynamic variables, you can produce meaningful runtime logs. For example, you may log events like the beginning or ending of the integration or display variable values that help trace execution flow. This practice significantly improves debugging efficiency and provides clarity when reviewing transaction history.

Additionally, the configuration panel offers access to functions and expression builders, enabling you to create advanced log messages. Whether you need to format strings, concatenate values, or apply conditional logic, OIC gives you full flexibility to structure the message exactly as required.

Completing the Logger configuration establishes an important checkpoint in the workflow. This ensures that when the integration runs, clear and informative messages appear in the monitoring dashboard, helping you validate flow execution and diagnose any issues quickly.

Step 6: Add the First Activity to the Integration Flow

This step explains how to perform ‘Add the First Activity to the Integration Flow’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

After configuring the Logger action, the next step in building your integration is to begin adding the activities that perform the actual processing logic. In the screenshot, the Add Activity button appears directly below the Logger in the integration canvas, indicating that the workflow is ready for its next functional component.

Clicking the + symbol opens a panel containing various activity options such as Map, Assign, Switch, For Each, and Invoke. These activities form the core structure of your integration, allowing you to transform data, apply conditions, call external services, loop through lists, or perform calculations.

Before selecting the appropriate activity, it is important to understand the flow requirements. In many OIC integrations, the next step after logging information is to map input values, prepare data structures, or invoke an external application. The design you choose here must align with the purpose of your integration and the business logic it aims to automate.

The screenshot highlights the flow in its current state—starting with the Schedule trigger, followed by the Logger, and now awaiting a new activity. At this stage, the integration is still in a simple and clean structure, making it easy to set the correct foundation before additional logic is added.

By selecting the Add Activity option, Oracle Integration Cloud ensures a smooth transition from basic initialization steps to the core actions of your automation process. Each new activity contributes to building a complete integration that executes reliably from start to finish.

Adding the first activity is a critical step because it determines how data begins to move and transform within your integration. From here, the workflow will expand into a fully functional process that can interact with external systems, process business rules, and manage data flows efficiently.

Step 7: Configure the Second Logger for Enhanced Tracking

This step explains how to perform ‘Configure the Second Logger’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

As your integration flow evolves, adding multiple Logger actions at key points in the workflow provides valuable visibility during execution. The screenshot shows the configuration panel for a second Logger, positioned further down the integration sequence. This Logger enhances tracking by capturing additional information after subsequent activities are executed.

When the Logger is selected, the configuration pane on the right displays the options for defining the logging behavior. Similar to the earlier Logger, you can choose whether this message should execute Always or only when the tracing level is set to Audit. Selecting Always ensures that the message appears consistently for every integration run, making it a dependable checkpoint during debugging and validation.

The Logger message field allows you to specify the exact text or expression that OIC should record at runtime. You can build dynamic messages by dragging variables or elements from the input source structure shown in the left panel. This includes fields derived from earlier steps, schedule metadata, or results from previous activities in the flow.

The design canvas in the screenshot indicates that this logger is situated after a Map (Primary) action. This placement suggests that its purpose is to confirm the successful execution of the mapping logic or to log transformed values for downstream processing. Logging at this stage is particularly useful when multiple transformations occur within a single integration, helping identify where potential issues may arise.

Configuring this second Logger strengthens the observability of your integration by adding an additional validation point. When the integration runs, monitoring tools will display this log entry, providing insight into the condition of the workflow at this specific stage. This ensures transparency, simplifies troubleshooting, and contributes to a more resilient and maintainable integration design.

Step 8: Add an Assign Activity to Populate Data Fields

This step explains how to perform ‘Add an Assign Activity’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

After setting up the necessary loggers in the integration flow, the next step is to introduce an Assign activity. The screenshot shows the Assign component being added to the workflow, positioned after the earlier actions. Assign activities are crucial when you need to create variables, initialize values, or prepare data structures before invoking external services.

By clicking the + icon beneath the previous logger, you open the activity selector panel. From there, choosing the Assign action allows you to create and update variables directly within the flow. This is particularly useful when your integration requires temporary storage of values, manipulation of input data, or construction of payloads needed for later steps.

The screenshot also displays the input and output sections associated with the Assign activity, showing variables that can be used or updated. These include schedule parameters and other metadata generated by the start event. Inside the Assign configuration window, you can drag fields from the input structure to the output variable area or manually define custom expressions using OIC’s expression builder.

Assign activities enhance the flexibility of your integration by enabling you to take full control of data manipulation. Common use cases include:

Setting default values
Combining multiple fields into a single variable
Performing basic calculations
Preparing request payloads for API calls
Initializing flags or counters for conditional logic

Placing the Assign action at this stage helps establish a clear data-preparation phase within the flow. It ensures that all downstream components—such as map actions, invokes, or conditions—receive correctly structured and validated data.

By incorporating Assign activities thoughtfully, you improve the accuracy, maintainability, and reliability of your integration design. This step lays the foundation for further logic and processing in the automation workflow.

Step 9: Configure the Assign Activity to Set Output Values

This step explains how to perform ‘Configure the Assign Activity’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

After adding the Assign activity to your integration, the next step is to configure the specific values or expressions that should be assigned to output variables. The screenshot displays the Assign configuration panel, where the input structure appears on the left and the output variable fields appear on the right.

In this configuration window, you define how data should be manipulated or initialized before it moves forward in the workflow. The Assign activity allows you to drag and drop fields directly from the input tree or manually enter expressions to populate output variables. This flexibility makes Assign a powerful tool for preparing values that will be required by downstream activities such as mapping, conditional logic, or invoke calls.

The screenshot shows several input attributes, including dayOfMonth, dayOfWeek, month, year, and other schedule-related metadata. You can assign these values to corresponding variables or combine them to form new computed outputs. The Assign configuration also supports the use of functions, enabling you to format dates, concatenate strings, or perform arithmetic operations.

When configuring an Assign action, it is important to ensure that each output variable receives a value appropriate to its type and purpose. Incorrect assignments may lead to mapping errors or unexpected behavior during execution. Therefore, careful planning and precise configuration help maintain stability and ensure the integration runs smoothly.

By completing this step, you establish a solid data foundation that prepares your workflow for subsequent logic. Configuring the Assign activity enhances clarity, control, and structure within the integration, supporting efficient data processing throughout the rest of the automation sequence.

Step 10: Add a Second Assign Activity for Additional Data Preparation

This step explains how to perform ‘Add a Second Assign Activity’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

As your integration workflow progresses, additional data preparation may be required to support downstream logic or external service calls. The screenshot shows the integration canvas with a second Assign activity being added below the previous components. This placement indicates that further variable initialization or value manipulation is necessary before the integration continues.

To add this activity, click the Add Activity (+) button beneath the earlier Assign or Logger actions. From the action palette, select Assign, which opens a new configuration window where you can create and modify variables. Multiple Assign activities in a single integration are common when different phases of the workflow require distinct data-handling operations.

In complex integrations, separating logic across multiple Assign components helps maintain clarity and improves maintainability. Each Assign can focus on a specific group of values—such as formatting timestamps, preparing API payloads, or organizing metadata for conditional routing. This granular structure reduces confusion and allows other developers to understand the flow more easily.

Adding a second Assign activity also enables you to enhance the data pipeline by refining intermediate values or creating new variables that may not have existed at the beginning of the integration. These new values can later be used in mapping, decision branches, or external service invocations.

By strategically inserting this second Assign component, your workflow becomes more structured, transparent, and easier to troubleshoot. It ensures that all necessary data transformations occur incrementally and logically, helping your integration run smoothly and predictably from start to finish.

Step 11: Add an Assign Activity to Initialize Custom Variables

This step explains how to perform ‘Add an Assign Activity to Initialize Custom Variables’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

After the Schedule trigger is configured, OIC allows you to insert your first variable initialization step using the Assign action. The screenshot displays the Integration Designer with the Assign action highlighted in the Actions palette on the right. This activity is essential for setting up default values or preparing variables required for subsequent decision-making in the integration flow.

To add this step, click the Add Activity (+) icon located after the Schedule element. From the available actions, select Assign, which opens a new editable component on the integration canvas. Assign activities enable you to create and initialize variables using OIC’s expression builder, making them fundamental for scenarios involving data manipulation or conditional routing.

The tooltip in the screenshot explains that Assign is used to “assign values to variables using the expression builder.” This functionality allows developers to define variables that will later be used in Switch conditions, arithmetic operations, or dynamic message generation.

Placing the Assign step immediately after the Schedule trigger helps establish a structured data flow. Setting default values at the beginning ensures that the integration behaves consistently, even when inputs are missing or dynamically generated at runtime. This initialization step becomes the baseline for all operations that follow.

Once the Assign action is added, you are ready to configure it further by defining variable names and expressions inside the configuration panel. This preparation step plays a key role in ensuring the integration runs predictably and aligns with your business logic.

Step 12: Add an Assign Action to Initialize Default Variables

This step explains how to perform ‘Add an Assign Action to Initialize Default Variables’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

In this step, we begin preparing the integration to handle operations dynamically by initializing default variables. The screenshot shows the Assign action being selected from the Actions palette. Assign activities are essential when you want to store values, prepare default parameters, or create placeholders for later computation.

By dragging the Assign action into the integration canvas, you begin establishing the foundational data structure. This default Assign action is typically used to initialize variables such as operation type, numerical values, or indicators that will guide conditional logic in downstream components.

Oracle Integration Cloud allows you to create as many variables as needed within an Assign. These initialized values help ensure that no field remains empty during execution and that each branch of the workflow operates with the correct data. Establishing default variables here enables the integration to behave predictably even when certain inputs are missing from request parameters.

This step prepares your integration for further enhancements, including conditional routing and arithmetic operations that depend on these initial values.

Step 12: Configure the Assign Action and Define Initialization Values

This step explains how to perform ‘Configure the Assign Action and Define Initialization Values’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

After placing the Assign action on the canvas, the next step is configuring it with a meaningful name and assigning values to the variables it will maintain. The screenshot shows the configuration panel where the Assign action is named Assignments1, following best practices for clarity and consistency.

The configuration screen provides fields for entering a description and defining one or more variable assignments. Each variable created inside the Assign action can be used later in the integration flow for operations such as addition, subtraction, conditional routing, or logging.

To configure variables:

Click the "+" symbol to add a new variable.
Enter a meaningful variable name (e.g., var_result, default_operation).
Choose the operation type, usually Assign.
Provide a default value appropriate to the workflow needs.

These initial values ensure that the integration has a consistent base state before any dynamic operations begin. Proper initialization also helps avoid runtime errors caused by null values and strengthens the reliability of downstream logic.

Once all variables have been defined, the Assign action becomes a stable starting point that supports Switch conditions, arithmetic logic, and other advanced operations added later in the flow.

Step 13: Configure Additional Assign Activity for Calculated Values

This step explains how to perform ‘Configure Additional Assign Activity for Calculated Values’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

The screenshot for this step shows another Assign activity named Sum_Assign, which is used to compute or store calculated results. Here, variables such as P_NUM1, P_NUM2, and P_OPERATION become input sources, allowing the Assign activity to build dynamic expressions based on user selections.

In the configuration panel, a variable named var_result is defined. This variable will store the outcome of the operation—such as addition, subtraction, multiplication, or division—depending on the conditions defined in the workflow.

The Assign activity enables you to:

Write expressions using numeric variables
Use arithmetic operations
Concatenate or format values
Prepare results for logging or output

By configuring this Assign action, you ensure that the integration produces meaningful output based on the values provided by the user at runtime. This step is crucial because it transforms the integration from a static workflow into a dynamic calculation engine capable of handling multiple operations.

The Assign activity in this step serves as the computational core of the workflow, setting up the variable that will later be logged, validated, or routed through different branches of the integration.

Step 14: Implement a Switch Activity to Control Conditional Logic

This step explains how to perform ‘Implement a Switch Activity for Conditional Logic’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

Once the input variables and result placeholders are configured, the next step is to introduce conditional evaluation using the Switch activity. The screenshot shows a Switch block named checkOperation, followed by three separate routes and an Otherwise route.

The Switch activity allows you to evaluate the operation type entered by the user—such as ADD, SUB, MUL, or DIV—and then route the workflow to the specific Assign block that handles that operation.

For example:

Route 1 may handle ADD logic
Route 2 may handle SUB logic
Route 3 may handle MUL or DIV logic
Otherwise handles invalid or undefined operations

Inside each route, an Assign activity is used to compute and store the correct result in var_result. This structured and organized routing ensures accurate calculations and prevents errors if unexpected user values are entered.

The Switch also improves maintainability, allowing developers to easily add new logic or modify existing conditions without altering the entire flow.

Step 15: Add a Switch Action to Introduce Conditional Logic

This step explains how to perform ‘Add a Switch Action’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

The screenshot shows a Switch activity being added to the integration, indicating that the workflow now requires branching logic based on evaluated conditions. The Switch action allows developers to create multiple execution paths depending on variable values, payload content, or other runtime parameters.

By clicking Add Activity (+) and selecting Switch, the designer inserts this component below the Logger. Within the Switch configuration, you can define one or more conditions that determine which branch executes. Common uses include routing based on status codes, flag values, or data validation outcomes.

Adding conditional logic at this stage allows the integration to behave dynamically, adapting its behavior to different scenarios encountered during execution. This creates a more flexible, robust, and intelligent workflow capable of handling multiple business conditions.

Step 16: Add or Insert an Action Between Existing Activities

This step explains how to perform ‘Insert an Action Between Steps’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

The screenshot for this step displays the option to insert an activity between existing workflow components. This is a powerful feature in OIC that allows developers to refine or restructure logic without disrupting the entire flow. A vertical “plus (+)” icon appears between activities, indicating where a new action can be placed.

Inserting an activity at this stage is often necessary when:

Additional data preparation is required
A new logger needs to track intermediate behavior
A transformation must occur before the next invoke
Validation logic must be added

By clicking the plus icon, you gain access to all activity options, allowing you to seamlessly integrate new processing logic exactly where it belongs in the workflow.

This flexibility ensures that your integration remains adaptable, maintainable, and logically structured even as requirements evolve.

Step 17: Validate Assigned Output Values in the Integration Flow

This step explains how to perform ‘Validate Assigned Output Values’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

The screenshot shows the configuration panel of an Assign activity where multiple output fields are displayed. At this stage of the integration design, it is crucial to ensure that every assigned value is correctly mapped and that the output variables reflect the intended structure. This step focuses on validating and confirming the correctness of all assignments before the integration continues to downstream actions.

In the Assign configuration window, the right panel displays the output variable structure, while the left panel shows the input fields and metadata available for mapping. Each field—such as dayOfMonth, year, month, hours, and similar attributes—represents data captured from earlier steps, often originating from Schedule metadata or calculated expressions.

During this validation phase, review each assignment closely:

Ensure every output field has a corresponding and meaningful value.
Confirm that numeric fields are assigned numeric content and string fields receive appropriate text or expressions.
Verify that no required fields are left unmapped, as this can cause downstream errors.
Make sure expressions used in assignments compile without syntax issues.

The Assign activity plays an important role in preparing data for later actions such as mapping, invoking external APIs, or conditional routing. Correctly configured output variables ensure that your integration behaves predictably, executes smoothly, and avoids unexpected failures during runtime.

By validating these assignments, you create a stable foundation for the remainder of the integration flow. This careful review step enhances reliability and ensures that the next stages of your workflow receive clean, accurate, and properly structured data.

Step 18: Add the Final Logger to Complete the Workflow

This step explains how to perform ‘Add the Final Logger’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

The final screenshot shows a Logger being added at the end of the integration flow. This Logger acts as the closing checkpoint, capturing messages that confirm the flow has executed correctly up to its last step.

By placing a Logger here, you ensure the integration concludes with a verifiable output, making runtime monitoring easier and enabling reliable troubleshooting if issues occur.

Step 19: Save and Prepare the Integration for Activation

This step explains how to perform ‘Save and Prepare the Integration’ inside Oracle Integration Cloud. Follow the instructions carefully to complete the workflow.

The final screenshot shows the completed integration with all components added. At this point, you must save your work using the Save button. Saving preserves the entire workflow, allowing you to proceed to activation.

This step is critical because OIC requires a valid, saved integration before it can be activated and executed. After saving, you can move to monitoring, activation, or testing steps depending on your project requirements. Completing this step ensures your integration is fully built and ready for deployment.

Introduction: Oracle Integration Cloud – End-to-End Integration Design & Execution Guide