You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Workflow - Failover Clustering

posted on November 13, 2019

We have a Client that is implementing the Failover Cluster with Laserfiche. The part  that we are uncertain about is Workflow. Ideally, Client would like Workflow to be included as well. For this current setup, the Workflow and LFS are on different boxes.

Per the Laserfiche whitepaper entitled Enterprise Deployment: Failover Clustering Considerations for Laserfiche: it is

Supported for the Workflow Subscriber and Message Queuing as of Workflow 8.3. The password for WFUSER$ is no longer tied to the local computer on which the Workflow Subscriber is running, so the Subscriber can fail over without needing to be reconfigured. Workflow Message Queuing is based on Microsoft’s Message Queuing Services (MSMQ). Consult Microsoft’s resources on how to build a clustered MSMQ role.

 

If the Client setup the Clustered MSMQ role, what would be the next steps? If anyone has successfully implemented this, please share.

I have read several posts on answers here but there isn't much or concrete steps on how to achieve this.

Thanks in advance.

0 0
replied on November 18, 2019

Hi Karim,

I wouldn't necessarily recommend Windows Server Failover Clustering for Workflow Subscriber/MSMQ. The Workflow Engine does not support failover clustering so you still have a single point of failure. This makes overall availability gains... questionable.

Subscriber 1 ---> WF Engine 

Subscriber 2 --------^

You're likely better off protecting the servers at the hypervisor level using VMware High Availability (or equivalent).

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.