Activate and Deactivate Integrations

After integration design is complete, you can activate your integration. You can also deactivate integrations.

Topics:

• Activate an Integration

• Reactivate Integrations after a Connection Update

• Deactivate an Integration

• Enable or Disable Tracing on Active Integrations

Activate an Integration

Once you create an integration and the progress indicator shows 100%, you can activate that integration to the runtime environment. An integration shows as 100% and is eligible for activation after you have specified the source connection, the target connection, the data mappings, and the tracking fields.

Understand Restrictions About the Number of Active Integrations

The number of active integrations per Oracle Integration instance cannot exceed 700. 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 700, 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 700 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.

To activate an integration:

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.

1. In the left navigation pane, click Home > Integrations > Integrations.
2. Go to the row of the integration to activate.
3. Click the icon to activate the integration.
   The Confirmation dialog is displayed.
4. Select options appropriate to your integration. A warning message is displayed in the dialog if the number of activated integrations for this Oracle Integration instance is above 90% of the limit.

   Element	Description
   Contribute integration mappings to Oracle Recommendations	Click to enable the Oracle Recommendations Engine. Uses the collective intelligence to recommend which fields should be mapped while developing an integration. These recommendations are built based on the mappings contributed to Oracle Recommendations Engine anonymously. You can change this on the Recommendations page by selecting Settings > Recommendations in the navigation pane.
   Enable Asserter Recording	Click to capture payloads and record instances for playing back and testing, See Test Integration Instances.
   Enable tracing	Click to enable detailed tracing information in the activity stream. The tracing level has no impact on billing. When this checkbox is selected, detailed logging information about messages processed by this integration flow at runtime is collected. This can aid in troubleshooting issues. However, detailed tracing may also impact performance. To disable tracing, you must deactivate the integration, then reactivate it without selecting the Enable tracing checkbox. You can download the logs on the Dashboard page. If you want to enable payload tracing to log input and output payloads to the activity stream, click the Include payload checkbox. When this checkbox is selected, information from the payload is also written to the log files, which can be downloaded and viewed. For example, you see more detailed logging information about payload activity at several points in the integration flow, such as the payload prior to data mapping and the payload after data mapping. This action can present a security risk and also impact the performance of your system. This setting is not recommended for a production environment. See Activity Stream Logs Deleted. .
   Activate & Deploy	Click to deploy a REST Adapter trigger-based connection to Oracle API Gateway. This option is only visible if you configured a connection with the Oracle API Gateway. See Connect to Oracle API Gateway.

5. Select an activation option. The options available are based on the type of integration you are activating:
   1. Click Activate (if you are activating a nonscheduled integration).
   2. Click Activate and Schedule (if you are activating a scheduled integration).
      The Run integration_name page is displayed. Create a schedule for running this integration, and click Save. See Define the Integration Schedule.
   A status message is displayed in the banner at the top of the page. For example:
   
   Description of the illustration integration_activation.png
   
6. If integration activation is unsuccessful, an Activation Failed warning icon is displayed in the banner. If you click the icon, a dialog is displayed with the option to download details about the activation failure incident.
   
   Description of the illustration integration_active_fail.png
   
   1. 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.
7. Click the icon to display details about how to run, test, and track instances for this integration.
   For example:

   If you selected to enable tracing, the words TRACE ENABLED are displayed under the icon you clicked to activate the integration. If you click the integration instance on the Track Instances page, the menu includes an option called View Activity Stream for viewing payload details.

   To access the detailed trace logging information:

   1. In the left navigation pane, click Home > Monitoring > Integrations > Dashboards.

   2. Click Download Diagnostic Logs to download Oracle Integration logs and diagnostics logs.

8. View active integrations by clicking the integration name or selecting View from the menu. The active integration is displayed with a message saying View Only in the banner at the top.

Note the following details about read-only mode:

• No Save button is displayed.

• There are no Invokes, Actions, or Errors icons.

• You can click through multiple parts of the integration to view configuration details, such viewing the business identifiers under the Tracking link, viewing the source-to-target and target-to-source mappings in the mapper, and viewing the configurations on the pages of the connection wizards, but you cannot modify anything.

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 left navigation pane, click Home > Integrations > Connections.
2. Find and update the necessary connection. The number of integrations that use that connection is displayed in the banner.
3. Click Test, then click Save.
   The list of active and inactive integrations that use the updated connection are 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.
   • Reactivation cancels all existing scheduled integrations, including the schedule’s next run that's in a waiting state. The schedule must be restarted after deactivation to regenerate the canceled next run. Otherwise, the next run is skipped.
   • 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 integrations 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 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.

General integration activation information is also provided. See Activate an Integration.

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 left navigation pane, click Home > Integrations > Integrations.
2. Go to the row of the integration you want to deactivate.
   To view only active integrations, select Active in the filter. You can also filter by integration name or integration type (prebuilt, customized, or developed) to narrow down the list.
3. Click the icon to deactivate the integration.
4. Click Deactivate in the dialog that appears. A deactivation progress bar is displayed at the top of the dialog.

   Note:

   If you attempt to deactivate a scheduled integration, any active or paused schedule for this integration is also stopped as part of deactivation.

   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 as 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 execution during the deactivation. You can also observe the failed instances occurring after the deactivation request.

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.

Enable or Disable Tracing on Active Integrations

You can enable or disable tracing on activated integrations without re-activating them. You can perform these actions on individual integrations or globally on all integrations.

Caution:

Enabling tracing at the integration or global level impacts performance. Oracle strongly suggests that you don’t enable this 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.

1. In the navigation pane, click Home > Settings > Integrations > Tracing.
2. Select an option below to configure the tracing level. 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 Tracing from the menu of an individual integration on the Integrations page and choose to disable tracing or enable tracing and include the payload in the integration. If you enable tracing, details are displayed in the activity stream.
   Global Tracing On	Select to globally turn on tracing 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. The following message is displayed for all integrations on the Integrations page. TRACE WITH PAYLOAD Tracing details are displayed in the activity stream. If you attempt to disable tracing for an individual integration on the Integrations page by selecting Tracing from the menu, a dialog is displayed indicating that global tracing is currently enabled for all active integrations. You must first return to this page and select Integration Level to enable or disable tracing at the integration level.
   Global Tracing Off	Select to globally turn off tracing 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. If you attempt to enable tracing for an individual integration on the Integrations page by selecting Tracing from the menu, a dialog is displayed indicating that global tracing is currently disabled for all active integrations. You must first return to this page and select Integration Level to enable or disable tracing at the integration level.

   Tracing can impact the activity stream logs. See Activity Stream Logs Deleted.