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:

• Activate an Integration

• Reactivate Integrations after a Connection Update

• Deactivate an Integration

• Manage Tracing Levels on Integrations

Activate an Integration

Once you have completed design of your integration and resolved any errors, you can activate it to the runtime environment.

Note:

If you activate a new version of an existing integration, tracking instances or logs of the old version are not deleted. However, related artifacts are deleted and redeployment is performed on the back end. Monitoring data is also removed.

Understand Restrictions About the Number of Active Integrations

The number of active integrations per Oracle Integration instance cannot exceed 800. Active integrations are defined as currently active integrations and integrations whose activations are in progress.

• If you reach 90% of this limit, the following warning is displayed:

  You've number integrations which are either active or whose activation is in progress. 
  It is more than 90% of the allowed limit. 

• If you reach the limit of 800, the Activate or Activate & Schedule button to activate an integration is disabled and the following warning is displayed.

  You've reached the limit as there are 800 integrations which are either active 
  or whose activation is in progress. Deactivate or abort the activation of an integration 
  and try again.

  If you are nearing your limit, review and delete any older integrations that are no longer required.

Activate an Integration

1. In the navigation pane, click Design, then Integrations.
2. Hover over the integration to activate, then click Activate .
   The Activate integration dialog is displayed.
3. Select the level of tracing appropriate to your integration. This level describes the amount of data to capture in the activity stream. The tracing level has no impact on billing.

   WARNING:

   The Audit and Debug (Not recommended) tracing levels are not recommended for a production environment. These options may slow down your system and also present a security risk because sensitive information from the payload is logged.

   Element	Description
   Tracing	Select the level of tracing information to log to the activity stream. Production: Logs all actions with the exception of loops and invoke/logger actions inside of loops (up to 1000 iterations) to the activity stream. Data is retained in the activity stream for 32 days. Audit: Logs the same data to the activity stream as the Production option, along with wire payloads of triggers and invokes. Data is retained in the activity stream for eight days. Wire payloads are the payloads sent and received over the wire by Oracle Integration while communicating with third-party applications. These communications either happen through triggers (where Oracle Integration receives the initial triggering message) or invokes (where Oracle Integration sends and receives data). The data in these payloads is untranslated and in the same format understood by the external applications/services that send and receive these payloads. Debug (Not recommended): Logs the same data to the activity stream as the Production and Audit options along with all payloads and all actions inside loops (up to a 1000 iterations). Data is retained in the activity stream for 24 hours. After that time period elapses, all payload, activity stream, and business identifier data is purged and a minimal amount of instance information is retained for 32 days. Note the following: After 24 hours, Debug (Not recommended) is automatically reset to Production. Explicitly reset the tracing level to Production or Audit when debugging is complete. Do not rely on the 24-hour automatic reset. The actual reset may take longer than 24 hours if no messages are processed by a given integration. See View Minimal Details About Debug Tracing Level Instances for 32 Days. See Activity Stream Details.
   Allow to run again	This check box only appears for REST Adapter-triggered and AS2 Adapter-triggered integrations. Select this check box if you want to replay an instance of this integration during runtime. See Replay Integration Instances.
   Enable payload validation	Select to validate inbound JSON payload syntax during activation of REST Adapter trigger connection-based integrations. Validation consists of checking for duplicate keys in the payload.
   Edit/Add Schedule	Select to add or edit a schedule for this integration now. This invokes the page for adding or editing an integration schedule.

4. If integration activation is unsuccessful, the status of the integration changes to Failed in the Status column. Click the Open Details icon to see the error.
   If your integration includes a function that is not completely configured, an error message is displayed in the banner. You must complete configuration of this function before you can activate the integration. Click inside the integration and note the following errors/warnings:

   • An error icon is displayed on the function call action that uses the incomplete function. The Error panel on the right side of the integration canvas provides specific details about the incomplete function.

   • A warning icon is displayed on the mapper that uses the inputs and outputs of this function. After completing function configuration, you must verify the input and output mappings before activating the integration.

     If activation is successful, the status of the integration changes to Active in the row.

5. If integration activation is successful, an Active message is displayed in the Status column.
   Additional messages can also be displayed:

   • If you selected Audit during activation, an Audit Tracing message is displayed after Active.
   • If you selected Debug (Not recommended) during activation, a Debug Tracing message is displayed after Active.
6. For REST Adapter trigger-based integrations, click Actions , then Run to display the Configure and run page to run, test, and track instances for this integration. See Test Integrations from Outside the Integration Canvas.

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.

1. In the navigation pane, click Design, then Connections.
2. Find and update the necessary connection. The number of integrations that use that connection is displayed.
3. Click Test, then click Save.
   The list of active and inactive integrations that use the updated connection is displayed on the right.

   
   
   

4. 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).

5. Click Refresh periodically to view progress.
   When complete, details about the reactivated integrations are displayed.
6. Click Cancel to close the page.
7. 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. If you want to modify an active integration, you need to deactivate it first. If the integration contains a business event subscription, a message is displayed 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.

1. In the navigation pane, click Design, then Integrations.
2. Go to the row of the integration you want to deactivate.
   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.
3. Click Deactivate to deactivate the integration.
4. 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.

   When an integration gets 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.

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
• Set the Tracing Level Globally for All Integrations

Change the Tracing Level on an Active Integration

1. In the navigation pane, click Design, then Integrations.
2. Hover over the active integration on which to change the tracing level.
3. Click Actions , then select Tracing.
4. Configure the tracing level.
5. 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

1. In the navigation pane, click Settings, then Tracing.
2. 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.