Question

Automatically Change Workflows Connection Profiles due to Server Change

Workflow Version 9 Version 10 Administration Installation and Upgrades

Updated May 27, 2016

asked on May 27, 2016

Our Laserfiche Workflow Server (9.1) has been running for years in the same machine (S1), monitoring 4 repositories in the same server. Workflows and repositories are being upgraded to a new server (S2) with version 10.1 . Once they are moved, the process of changing the connection profiles individually for each workflow (about 800 o them) is an overwhelming task. Since everything, but the server name, is changing, is there any way to automatically/semi-automatically change the connection profiles for every workflow?

**************************************

Example:

Profiles Details:

Name: ProfileName (no change)

Server: S1.abcd.com (will change to be S2.abcd.com)

Repository: RepositoryName (no change)

User Name: Workflow (No change)

Password: ****** (No Change)

************************************************

Would updating column [server_name] in table [connection_profiles] in my [workflow database[ solve my problem?

Please, advice. Thanks!

0 0

Replies

replied on May 27, 2016

Please don't update SQL tables directly. The connection_profiles is the list of repositories monitored by the WF Server. It won't solve your problem because the repository connection profiles are embedded (and encrypted) in the workflow definition XML.

Is S1 the WF Server or LF Server or both?

See this thread and this thread on moving servers.

0 0

replied on May 27, 2016

Hello Miruna,

S1 is both Workflow and LF Server.

0 0

replied on May 27, 2016

If it's being decommissioned after the move, you could DNS alias S2 as S1 so any running workflows will still find it. If not, then the instructions on the first thread mentioned in my post above should apply to you. The redirects mentioned in that thread will keep workflows running, but there is a minor performance penalty associated with them (since WF tries to log in with the old name and fails first, then checks for redirects). So while you can keep them in place indefinitely, I would still recommend updating the connection profiles in all workflow definitions as you check them and update them.

0 0

replied on May 27, 2016

Unfortunately, the old server won't be decommissioned. We will probably have to use the redirects until every workflow has been updated with the new connection. Any further information on the issue would be greatly appreciated.

Thank you for your support.

0 0

You are not allowed to follow up in this post.

Question

Question

Automatically Change Workflows Connection Profiles due to Server Change

Replies

Sign in to reply to this post.