Activate and Deactivate Integrations

After integration design is complete, you can activate and set the tracing level for your integration. You can also deactivate integrations.

Topics:

Reactivate Integrations after a Connection Update

You can reactivate all active integrations together that use the same adapter connection after a connection update. This eliminates the need to manually deactivate and reactivate each integration individually to reflect the updated adapter connection. This functionality works for all adapters.

Note:

A maximum of 50 integrations can be reactivated after a connection update.

In the navigation pane, click Design, then Connections.
Find and update the necessary connection. The number of integrations that use that connection is displayed.
Click Test, then click Save.
The list of active and inactive integrations that use the updated connection is displayed on the right.
Click Save & Reactivate to apply the connection changes to all active integrations. Note the following:
- You cannot select individual integrations to reactivate; all are reactivated.
- Any active schedule integrations are temporarily paused and enter a failed state. The schedule restarts after reactivation completes. However, schedule integrations that are currently in-flight enter a failed state and are discarded.
- Any integrations using this connection that are currently listed as inactivate remain in that state.
- If you click Save, your connection changes are saved, but no integrations are reactivated.
- Deactivation of an integration that subscribes to business events does not unsubscribe the business events.
The page is refreshed to show integration activation progress (for example, the number of integrations that have been reactivated and the number of integrations remaining to be reactivated).
Click Refresh periodically to view progress.
When complete, details about the reactivated integrations are displayed.
Click Cancel to close the page.
If any integration reactivations failed, go to the Integrations page to investigate.

Deactivate an Integration

You can deactivate an integration in Oracle Integration to stop it from processing any new messages. You can also individually deactivate an integration in a project. If you want to modify an active integration, you must deactivate it first. If the integration contains a business event subscription, a message appears asking if you want to delete the event subscription.

Deactivation is equivalent to undeployment of a project, which means all existing history, monitoring, and runtime data are lost. Oracle Integration does not support the notion of starting and stopping projects. With asynchronous patterns, the queue for the deactivated project is deleted and all messages associated with this queue are also deleted. Therefore, if there are pending requests unprocessed, they are lost after deactivation. The previous version is deactivated and all existing history, monitoring, and runtime data is lost.

To view only active integrations, select Active in the Status field of the Filter filter. You can also filter by integration name, time last updated, integration creator, status (all, draft, configured, active, activating, and failed), type (all, developed, accelerator type, and recipe), or style (all, application, schedule, and event) to narrow down the list.

Decide where to start:
- Work in a project.
  1. In the navigation pane, click Projects.
  2. Select the project name.
  3. Click Integrations .
  4. In the Integrations section, find the specific integration to deactivate.
  5. Click Actions , and select Deactivate.
    The Deactivate integration panel opens.
- Work outside a project.
  1. In the navigation pane, click Design, then Integrations.
  2. Find the specific integration to deactivate.
  3. Hover over the integration to deactivate, then click Deactivate .
    The Deactivate integration panel opens.
Click Deactivate in the dialog that appears.

Note:
Deactivation of an active, schedule integration is not allowed. You must stop the schedule, then retry.

Integration deactivation can take time to complete after you initiate the request. During this time period, there may still be in-flight or queued requests being processed. These processing instances fail when the corresponding integration artifacts and resources are removed and undeployed.

You can observe different processing errors for the failed instances depending on the point of processing during the deactivation. You can also observe the failed instances occurring after the deactivation request.

If deactivation fails and the integration state is displayed as Deactivation Failed, retry the deactivation. An integration in this state cannot be edited or activated.

When an integration is successfully deactivated, all its data get undeployed from runtime. This results in nonterminal instances (which are visible on the Instances and Errors pages) getting aborted. Instances in queued, in progress, in error (recoverable type), and other states all move to the aborted state. The existing terminal instances (succeeded, aborted, and in error (nonrecoverable type) remain unaffected.

Deactivate an Integration with Business Events

If the integration to deactivate contains a business event subscription, a message is displayed asking if you want to delete the event subscription. If you select to delete the event subscription, the integration does not receive any events after it is reactivated.

This image shows the Deactivate Integration. The integration name and version number are shown. Below that the Delete Event Subscription checkbox is shown. A help icon appears in the upper right. The Cancel and Deactivate buttons appear in the lower right.

If you do not want to delete the event subscription, the events in this integration are resent if the integration is activated within six hours.

Manage Tracing Levels on Integrations

You can change the tracing level on an active integration without having to deactivate and reactivate it. You can also set the tracing level globally for all integrations.

Caution:

Changing tracing to the audit or debug level impacts performance. Oracle strongly suggests that you don’t enable the debug or audit option in production environments. Including the payload in tracing impacts the performance of your system and may violate your company’s data retention rules by storing sensitive information in the payload trace. Understand the impact of the various options before making a selection. See Activate an Integration.

Change the Tracing Level on an Active Integration

In the navigation pane, click Design, then Integrations.
Hover over the active integration on which to change the tracing level.
Click Actions , then select Configure activation.
Configure the tracing level.
Click Save.
The tracing level is changed in the active integration.

The message under Active in the Status column changes for this integration. For example, if you changed the tracing level from Production to Audit, the message Audit Tracing is displayed after Active once integration reactivation completes.

Set the Tracing Level Globally for All Integrations

In the navigation pane, click Settings, then Tracing.

Select an option to configure the tracing level, and click Save. The tracing level has no impact on billing.

Element	Description
Integration Level	Select to enable or disable tracing at the individual integration level on the Integrations page. This enables you to select Actions and then Tracing for an individual integration on the Integrations page and select to disable tracing or enable tracing and include the payload in the integration. This is the default selection.
Global tracing on at audit level	Select to globally enable tracing at the audit level for all activated integrations. After selecting and saving this option, you cannot enable or disable tracing at the individual integration level on the Integrations page. Two other changes occur: When you access the Integrations page, a message is displayed indicating that tracing is enabled at the audit level for all active integrations and you cannot enable or disable it at the individual integration level. If you select Actions , there is no Tracing option available for selection. To enable or disable tracing at the individual integration level again, you must select Integration level, then Save.
Global tracing on at debug level	Select to globally enable tracing at the debug level for all activated integrations. After selecting and saving this option, you cannot enable or disable tracing at the individual integration level on the Integrations page. Two other changes occur: When you access the Integrations page, a message is displayed indicating that tracing is enabled at the debug level for all active integrations and you cannot enable or disable it at the individual integration level. If you select Actions , there is no Tracing option available for selection. Note: Regardless whether debug tracing is set globally or on a single integration, the tracing level is automatically reset to production after 24 hours. To enable or disable tracing at the individual integration level, you must select Integration level, then Save.
Global tracing off	Select to globally disable tracing for all integrations. After selecting and saving this option, you cannot enable tracing at the individual integration level on the Integrations page. Two other changes occur: When you access the Integrations page, a message is displayed indicating that tracing is disabled for all active integrations and you cannot enable it at the individual integration level. If you select Actions , there is no Tracing option available for selection.