Stopping K2 during deployments


Badge +2

When we deploy our system, we stop all the applications. K2 processes call alot of wcf services while running. The issue during the deployment is we also deploy K2 processes; however, it requires the K2 server to be running. Since the server is running, processes may escalate or run start rules that call into the systems. Since these systems are down for maintenance, the process errors out. 

 

Is there a way to stop K2 from processing workflows, but still be available for management purposes? This would allow us to deploy but run and processes?

 

Phil


2 replies

Badge +3

What you could do is from the Management Console in the K2 Workspace, select the process instances you want to temporarily stop. 

 

Then carry out the deployment and start up those stopped process instances after the deployment.


14849i8A02F55557874663.png
Badge +8

To elaborate on @KennyC's comment: Using the SourceCode.Workflow.Management namespace, you can automate the process of stopping and starting all process instances.  With a little bit of effort, you can wrap this process in an MSBuild task and do the entire deployment via MSBuild.

Reply