Oracle SOA Composite – Retire, Activate, Shut Down and Start Up

Overview

Once Oracle SOA composite are deployed on SOA server with multiple versions, we can easily manage their lifecycle with the help of Oracle Enterprise Manager. Oracle Enterprise Manager Fusion Middleware Control provides a rich user interface to manage, monitor and diagnose the SOA infrastructure.
In this post, I will discuss four actions apart from deploying and undeploying that you can perform on SOA Composites using Oracle EM Console. These actions include retiring, activating, shutting down and starting up the composite. On selecting a composite, you can see the Retire and Shut Down buttons enabled as shown in Figure 1.

Figure 1

Actions

Retire

· Retire Default Composite
If another active revision of this composite is found, it will be designated as the new default revision. Once retired, this composite revision will no longer process any incoming requests, and no new instances will be created. However, all currently executing instances will complete normally.
· Retire Non-Default Composite
Once retired, the composite revision will no longer process any incoming requests, and no new instances will be created. However, all currently executing instances will complete normally.
 

Activate

This will activate an already retired composite. It will start accepting new incoming requests and new instances will be created.
 

Shut Down

You will not be able to create new instances of this composite. In addition, processing of existing instances of the composite will stop.
 

Start Up

This will start the composites which are in shut down state.
 

Issue

If you try to perform some action on a composite instance which is in Shut Down state, you will get the following error:

<May 12, 2014 10:49:20 AM IST> <Error> <oracle.soa.services.workflow.task> <BEA-000000> <<.> Workflow Service Engine callback to SOA mesh failed.

Callback operation onTaskCompleted from ci/CIBusinessRule!1.0/CIBusinessRuleHumantask to CIBusinessRule/CIBusinessRuleHumantask.TaskService_1 failed with error: Message Router for ci/CIBusinessRule!1.0*soa_5196ff1f-b4cb-429a-a302-bd4aea651c37 is not able to process messages. The composite state is set to "off".  The composite can be turned "on" by using the administrative consoles.

Check the underlying exception. Ensure that the SOA composite is configured correctly.

ORABPEL-30081

Workflow Service Engine callback to SOA mesh failed.

Callback operation onTaskCompleted from ci/CIBusinessRule!1.0/CIBusinessRuleHumantask to CIBusinessRule/CIBusinessRuleHumantask.TaskService_1 failed with error: Message Router for ci/CIBusinessRule!1.0*soa_5196ff1f-b4cb-429a-a302-bd4aea651c37 is not able to process messages. The composite state is set to "off".  The composite can be turned "on" by using the administrative consoles.

Check the underlying exception. Ensure that the SOA composite is configured correctly.

        at oracle.bpel.services.workflow.fabric.WorkflowServiceEngine.doCallback(WorkflowServiceEngine.java:1822)

        at oracle.bpel.services.workflow.task.impl.WorkflowCallback.postToFabric(WorkflowCallback.java:440)

        at oracle.bpel.services.workflow.task.impl.WorkflowCallback.onTaskComplete(WorkflowCallback.java:129)

To resolve this error, you must start the composite before performing any action on the human task.
I hope this post will help people in managing the lifecycle of SOA Composite applications with ease.