Stop and Start an Oracle Integration Instance
You can stop and start Oracle Integration Generation 2 instances. After a stop request is initiated, the instance goes into a pausing state. During the pausing state, no new integrations and processes are started. In-flight integrations and processes continue until they either complete or reach a checkpoint. When the integrations and processes are no longer running, the instance goes into a completely paused state. During this state, Oracle Integration design time, settings, and monitoring capabilities are unavailable.
Note:
Oracle recommends the following:- Do not stop instances running in a production environment.
- Do not stop or start instances on a nightly basis. During routine maintenance patching, lifecycle operations are disabled. This may lead to a situation where the service instance cannot be started or stopped for several hours while the patching cycle completes.
- Start or stop an instance in either of two ways:
- On the Integration Instances page, go to the end of the row for the specific instance, and click . Note that an active instance is identified as Active and an inactive/stopped instance is identified as Inactive in the State column.
- On the details page of a specific instance, click the More Actions menu.
- Select the action to perform:
Note:
You can use the REST APIs to stop and start an instance. See Oracle Integration API. Oracle Integration APIs are available in the left navigation pane.