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

Question

Question

Best practice for moving a production 9.0.2 Avante Workflow and LF server to a new 9.2 server on new hardware.

Workflow Installation and Upgrades
Updated June 5, 2015
asked on November 13, 2014

Customer has a single server 9.0.2 installation on a Server 2003 box that we're migrating to a new 2012 R2 box. He's upgraded LF to 9.2 already but couldn't upgrade the WF because of Server 2003 incompatibility.

I know well how to migrate LF over to the new server but haven't had to move a running Workflow server before. The migration tools appear to be only for 8.x Workflow moving to a new 9.x server. I'm already at 9.0.2 on Workflow and there are currently running workflows.

How do I move Workflow to the new server?

We can do this with downtime but we can't break currently running workflows. They need to come back where they were on the new server.

0 0

Replies

replied on November 13, 2014

The latest word from the customer is "it's not going to be the end of the world if we lose the running workflows". In other words, if it makes the move stupid easy if I terminate all the running workflows then they're ok with that.

If that were the case would I just move the WF DB and reattach to new server and run WF configuration? Do I need to move the files in the WF working folder too?

0 0
replied on November 13, 2014

Are the workflows in the middle of moving files?

Are you moving the SQL instance used by WF too?

0 0
replied on November 13, 2014
  1. Install WF 9.2 on the new server
  2. Stop WF on the old server
  3. Move the SQL DB for WF if needed
  4. Configure WF 9.2 to use the SQL DB that the old WF server was using (the database will be updated during the configuration process)
  5. Make sure WF 9.2 works with the existing LFServer
  6. Put in redirects for the new LFServer in WF 9.2
  7. Stop WF, move LFS to the new server and attach the repositories
  8. Start WF, confirm it works
  9. Republish the Workflow rules with updated connection profiles pointing at the new LF Server.
  10. Confirm new workflows start correctly
  11. Remove the redirects (there's a bit of a performance hit associated with the redirects, so while steps 9-11 don't have to be done immediately after the move, they should be done)

 

Terminating running instances will really only save you step 6 since you will still have to update the connection profiles in all workflows to point to the new LFServer.

 

0 0
View 1 previous reply
replied on November 13, 2014

I think this'll likely work although I can't seem to configure workflow on the new 9.2 server.. i'm getting the same symptom as this post:

https://answers.laserfiche.com/questions/51324/unable-to-find-requested-net-data-provider-when-configuring-WF-server-at--911

0 0
replied on November 13, 2014

Did you check both versions of the .Net config file?

0 0
replied on November 14, 2014

as per http://forums.asp.net/t/1693277.aspx?+DbProviderFactories+section+can+only+appear+once+per+config+file+error

 

yes. the 4.x file had the error listed in it so I corrected it as per the article but even after reboot the symptom is the same. Have support case #163967 open. No resolution yet.

0 0
replied on November 14, 2014

I had to search for all instances of machine.config files across the entire machine as there were more than two of them and there was another that had the DbProviderFactories error as referenced above. Now I shall see if my workflow migration worked.

0 0
replied on June 5, 2015 • Show version history

Are any extra steps must be done if WF contains custom activities?

0 0
replied on June 5, 2015

Yes, you would have to make sure your customer DLLs are in the same place on the new machine as the old one. Or update the paths in the WF Admin Console under Server Configuration\Custom Activities.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...