Activate and Deactivate Integrations
After integration design is complete, you can activate your integration. You can also deactivate 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
- 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.
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.-
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.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.
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.