Tuesday, 15 September 2015

IBM BPM Advanced 8.5.5 - CWWBF0057E WSVR0102E and WSVR0195E seen when trying to stop a SCA Module

We saw this today: -

[15/09/15 16:28:39:474 BST] 00000159 AdminHelper   A   ADMN1010I: An attempt is made to stop the IRterieveProductEligitbilityEmulatorApp application. (User ID = defaultWIMFileBasedRealm/c03999)

[15/09/15 16:28:39:475 BST] 00000159 CompositionUn A   WSVR0192I: Stopping composition unit WebSphere:cuname=IRterieveProductEligitbilityEmulatorApp in BLA WebSphere:blaname=IRterieveProductEligitbilityEmulatorApp.

[15/09/15 16:28:39:478 BST] 00000159 ProcessContai E   CWWBF0057E: The application cannot be stopped because of existing process instances.: [com.ibm.bpe.database.ProcessTemplateB@35c52e15]

[15/09/15 16:28:39:481 BST] 00000159 ApplicationMg E   WSVR0102E: An error occurred stopping, IRterieveProductEligitbilityEmulatorApp

{1}

[15/09/15 16:28:39:481 BST] 00000159 CompositionUn E   WSVR0195E: Composition unit WebSphere:cuname=IRterieveProductEligitbilityEmulatorApp in BLA WebSphere:blaname=IRterieveProductEligitbilityEmulatorApp failed to stop.


This occurred when one of my team was attempting to stop/uninstall an Enterprise Archive (EAR) file, said EAR file contained an Service Component Architecture (SCA)  module, said SCA module contained a Business Process Execution Language (BPEL) component.

The message is pretty clear: -

[15/09/15 16:28:39:478 BST] 00000159 ProcessContai E   CWWBF0057E: The application cannot be stopped because of existing process instances.: [com.ibm.bpe.database.ProcessTemplateB@35c52e15]

The trouble is .... what do we do next ?

Well, this IBM Knowledge Centre article helps: -


In essence, one needs to use the Business Process Choreographer Explorer (BPC Explorer) : -

to locate, terminate and, perhaps, delete any existing process instances belonging to that particular BPEL component, before one can stop the SCA Module ( EAR file ) and delete / reinstall it.

So we logged into BPC Explorer as a user with WAS administration privileges, navigated to Process Instances > Administered by me and saw .... nothing, zip, nil, nada, niet, nien, zero :-(

The same was true when we logged in as wasadmin ....

Which was nice ......

Ah, yes, and the solution ?

Well, whilst wasadmin is a "super-user" ( by this, I do, of course, mean a user with the full WAS administration privileges ) in the world of WAS, in the world of BPM, there is one user with greater powers :-)

Yes, it's the Deployment Environment administrator ( deAdmin or similar ) is the user to which I refer ....

Once we logged in to BPC Explorer as deAdmin, we could see the two process instances, terminate them and then ( our choice ) delete them.

Once we did that, we were able to stop and uninstall the EAR / SCA module, and all was good.

It does, of course, raise the point .... in the world of IBM BPM, one cannot just assume that one can, as a WAS administrator, stop/uninstall an EAR file ....

There's always the potential of existing, running process instances, which need to be managed, BY THE BUSINESS, in terms of error handling, completion, migration, termination, deletion etc. and BPC Explorer is the place to go ....

Good to know :-)

No comments: