So, the powers that be want to move the data you've got set up in U-LINC to a new server (or to an upgraded instance). You may be asking, "What do I need to do to make sure that all of my workflows will still work?" I'm glad you asked.
The first thing you need to do is to make sure the new databases are set up properly. The U-LINC windows service account and any SQL account that you use for configuration, application sources, or workflow actions need to be set up with the same permissions on the new server.
Next, you need to activate the new databases for use with U-LINC through the U-LINC Configuration Manager. This ensures that the master encryption key is set and that the U-LINC assemblies are installed on the new server.
The application sources in the U-LINC SharePoint site now need to be changed to point to the new server. When the application source is saved, it will re-create the U-LINC integration triggers using the correct encryption key.
Finally, you will need to modify the SQL connection strings to point to the new server in any workflows that use an Execute SQL statement. Republish those workflows and any new instances will be good. If any of these are currently running (either paused or awaiting a task completion), you should terminate them and restart if possible, or you may run into trouble down the road.
This should take care of most of your SQL server migration/upgrade issues with U-LINC. As always, make good backups and test everything first!
No comments:
Post a Comment