Task Manager and Task Action handler

The TaskManager or TaskActionHandler processes are the default process which gets deployed in to your bpel server when we install the SOA Suite however in many cases these process in Oracle BPEL Control fail to deploy after installing Oracle Application Server or after upgrading.

YOu can find the following issues along with this like

The domain.log file present in SOA_HOME/bpel/domains/default/logs will give compilation error and xml parser error.


Either the TaskManager or TaskActionHandler or may be both will not appear in the bpel console

Http://localhost:port/BPELConsole.

or a third case is when you will have the .jar files in failed state.

In that case file named bpel_TaskManager_1.0.jar.failed or bpel_TaskActionHandler_1.0.jar.failed will be present in the ORACLE_HOME/bpel/domains/default/deploy directory.

TO overcome this issue

Navigate to

SOA_HOME/bpel/domains/default/deploy folder and there change the

bpel_TaskManager_1.0.jar.failed to bpel_TaskManager_1.0.jar

and bpel_TaskActionHandler_1.0.jar.failed to bpel_TaskActionHandler_1.0.jar

Once done restart your server and these process will be automatically deployed in the server.

Now you will be able to see both the process in the bpel console.

One more thing that we have captured here is if we will copy any jar file in the

SOA_HOME/bpel/domains/default/deploy location it will be automatically deployed to the bpel server when it will start because it is the default location used by bpel process manager to deploy the process while starting.