Question

2 workflow servers on 1 repository?

Workflow Version 10 How To

Updated March 28, 2022

asked on March 23, 2022

I have a large document migration I'm about to start. Every time I have tested importing and running my routing and filing workflow, it pretty much shuts down my regular production workflows. I'm pointing Import Agent at a folder and it's importing a ton of documents fast and my workflow kicks off on document creation. The concern is that when this is happening, all my production workflows are held up and I start getting calls.

So my question is, can I use my Dev workflow server to run the migration workflow, and leave my regular workflow server running the rest of the workflows? If I point my Dev Workflow server at a repository that already has a workflow subscriber monitoring, how could I ensure my production workflow server doesn't run on my import project?

0 0

Replies

replied on March 24, 2022

You can have multiple workflow servers pointed at a single repository and a workflow server pointed at multiple repositories.

In our environment we have one repository in particular that has two workflow servers constantly running to distribute the high volume of activity.

During our initial migration to Laserfiche we even had 3 WF servers pointed at a single repository.

I'm not sure what you mean when you say "ensure my production workflow server doesn't run on my import project" because each server has it's own rules and workflows.

As long as your servers don't have conflicting rules/workflows, they'll stay out of each other's way.

When setting up a second workflow server, you use the Attach instead of Add option, but your production server still can't run any workflows that only exist on your import project server.

Configuring Monitored Repositories (laserfiche.com)

3 0

replied on March 24, 2022

That's how I was hoping it would work. As long as I don't have overlapping starting rules, I should be fine. Thank you.

1 0

replied on March 23, 2022

Are you licensed for additional Laserfiche Server instances? For migration projects, I do the bulk import and indexing in a test/staging environment. Then when everything is in good order, run a workflow (still the test WF server) to replicate from there into production. For me, this avoids the issue of bogging down the production workflow environment.

2 0

replied on March 28, 2022

WF Servers process all activity coming from the repository that matches the events in their active starting rules. So both will see the events from your import by default.

If you want to prevent your production server from processing them, you should create a user specifically for the import process and then exclude it at the server level using the user exclusion filter. That way the production server will discard events generated by the import and you can have the second server process those.

Be aware that more Workflow servers means more repository activity, which in turn generates more SQL activity, so, depending on your setup and hardware, your production server may still be bogged down.

1 0

You are not allowed to follow up in this post.

Question

Question

2 workflow servers on 1 repository?

Replies

Sign in to reply to this post.