Question

Data Source Changing Servers

Forms Workflow Laserfiche Administration

Updated April 14, 2022

asked on April 12, 2022

I am sorry if this is out there somewhere (I couldn't find it). I have a "Laserfiche Integrations" SQL Db where I pull information into forms and write to through workflow. The server is about to be moved and I am trying to find out in advance if just updating the datasource in the administrator console will automatically redirect all my forms and workflows or if I am going to have to test them all and make changes to re-establish the connectivity to my data sources.

LOGICALLY, it would seem that updating the master data source records in forms and workflow so they are pointing to the new location would mean the individual forms and workflows would not need to be touched, but since several of these are public forms (contracts, internal departmental inventory records, and billing adjustment requests from the public), I can't really afford to not know before we make the switch.

Has anyone had an external data source move and should I anticipate any issues?

1 0

Replies

replied on April 13, 2022

Updating the data sources will redirect all your workflows and forms process. Except for the ones attempting to contact the data source while you're making these changes.

If the old server is getting completely decommissioned, use a DNS alias on the new server with old server name as a temporary way of redirecting traffic trying to go to the old server. You can take down the DNS alias once all data sources are updated.

If you're using Windows ODBC data sources in Workflow, you could stop the Workflow services, update the data sources in Windows and restart Workflow.

2 0

replied on April 14, 2022

We had this same dilemma before moving our SQL databases to a new server. We solved it by giving the old sql server an alias, changing all the processes and connections to the new alias while the old SQL server was still in place, meaning all processes ran on the old connection, then smoothly transitions when connected to the alias. Then when we migrated the SQL server we gave the new SQL the same alias and everything ran seamlessly. Now, since we are using aliases we can do this in the future again with no issues.

2 0

replied on April 13, 2022

I think it should work too, as long as the data structure is identical, which it will be when moving a database. I also agree with Timothy Wade about testing first. We have a couple of sql server migrations coming up, so I'm very interested in this question. I plan to setup a test database on separate sql servers and test it myself, and I'll add another reply with my findings; however, it will probably be next week before I can do it.

1 0

replied on April 13, 2022

That's a good question, and like you, I think it should work. Unfortunately, I don't definitively know the answer.

Do you have the luxury of a modest amount of downtime for testing? If so, could you move a copy of the existing database to the new server, get the permissions set as needed, and then test the change with the system temporarily unavailable to production users?

Even if someone knowledgeable replies that it will work, I would feel more comfortable if I could test the change first.

0 0

replied on April 13, 2022

I have like 5 processes that will be affected. I am planning on choosing a time that will be least likely to impact use and unpublish the forms while we move, redirect, and test (lightly and quickly).

I felt confident that the change on the data source will ensure all the processes work, but can't say I'm not a bit nervous!

0 0

You are not allowed to follow up in this post.

Question

Question

Data Source Changing Servers

Replies

Sign in to reply to this post.