Workflow Failover Processing

Posted by Kevin Sweeney on Apr 1, 2014 4:59:45 PM

 

 

Workflow Failover Process Workflow Failover Process

 

Workflow failover is a critical component within redundant production network system designs.  Regardless of the marketplace,  whenever the processing of workflow requirements are concerned, what the end user cares about most is application availability.  This is how we live our lives.  When we want the information - we want it now and we want that information to be up to date and correct.

The end user does not really care about the world of computers, servers and networks required to bring them that information.  So what happens when a production server eventually goes offline as a result from either equipment failure or planned, preventative maintenance?  When this event happens, another production server should take over the workflow processing requirements.  But how does that switching from one server to another happen?

What is workflow failover?

In a production environment, typically there is one production workflow server processing all workflow requests.  And a second stand-by workflow production server waiting to process workflow instances in the event that the primary server fails.  This switching from primary to secondary servers is called "failover".   While some companies use a manual workflow failover mechanism to manage the failover process, cDevWorkflow uses an automated process.

What is manual workflow failover?

Manual workflow failover is exactly as the name describes.  When the primary workflow server fails, the person responsible for the server begins to receive a number of angry user phone calls, text messages and emails describing their application communication problems.   When this happens, a person, initiates the application on the secondary server.  Hopefully not to much work has been lost in the failover process.

What is automated workflow failover?

Automated workflow failover is based on known network systems communication or pulses.  Here it is the secondary server that is monitoring the health of the primary server by simply checking for a pulse.  The default setting for this cDevWorkflow automated workflow failover is to activate this feature whenever the primary server fails to respond after five (5)  minutes.  The default setting for this feature can be adjusted in order to properly fit the users balance of application availability and network performance.

 

Workflow FailOver Diagram Workflow FailOver Diagram

 

 

cDevWorkflow version 7.7 provides automated workflow failover monitoring and processing at no additional cost.

For more on workflow failover, click here

A small sampling of the Workflow Technology for BPM Solutions contained within our cDevWorkflow product offering can be found here: Workflow Technology That Works.

[hs_form id="9"]

Learn more about our Process Automation & IT, QA Services or Software Development products and solutions on the Web!  Visit us at: Innovative Process Solutions

Topics: workflow failover, Blog, Automated Failover Processing, bpm workflow automated failover processing, bpm automated workflow failover, bpm workflow failover, bpm workflow automated failover, manual workflow failover, workflow automated failover processing, automated workflow failover, bpm failover processing, automated failover, workflow failover processing