Manage Active Applications

After an application is activated, you might need to change its status or mode. For example, you might need to shut down an application temporarily or retire an application indefinitely.

In the Oracle Integration navigation pane, click Processes, then click Process Applications, and then click Activate.

In the Actions column, click Options Options icon for the application you want to manage.

You can select to retire (or activate), deactivate, and shut down (or start up) an application. You can also view the web services exposed and consumed by the application.

Description of management-app-actions.png follows
Description of the illustration management-app-actions.png

Retire and Activate Applications

Retire and Activate are opposite actions. Retiring an application retires an active application and you can no longer create a new instance from that application version. Instances that are already created continue to run and new requests for existing instances are accepted. Activating an application brings it back from the retirement stage. The Manage Active Applications page reflects the new status in the Mode column (Active or Retired).

Activate activates a retired application revision. Note the following behavior with this option:

  • All applications are automatically active when activated.

  • Other revisions of a newly activated application remain active (that is, other revisions aren’t automatically retired). If you want, you must explicitly retire them.

Deactivate an Application

When you deactivate an application version:

  • All running and completed dynamic process instances and tasks of the deactivated application version are deleted.
  • All running structured process instances and tasks of the deactivated application version are marked as Stale indicating that they are no longer active. All completed structured process instances remain as it is and continue to be marked as Completed.

Note that Stale and Completed structured process instances can be removed permanently through archive and purge. See Archive and Purge Data.

Shut Down and Restart Applications

Shutting down an application is possible only after starting an application. Once an application is shut down, any request related to the application is rejected and no new request can be processed. All instances are stopped. You can restart the active application revision that was shut down. This action enables new requests to be processed (and not be rejected). No recovery of messages occurs. The Activate page reflects the new status in the Status column (On or Off).


Shutdown shuts down a running application revision. Any request (initiating or a callback) to the application is rejected if the application is shut down. However, the behavior differs based on which component is used. For example, a web service request is rejected back to the caller.

View Information About Web Services

To view information about the web services used by a active application, click Web Services.

  • The Exposed tab displays the web services URLs that the active application is exposing.

  • The Consumed tab displays the web services that the currently active application connects to.