Moving the DocLink Database to Another Server

  1. First make sure the following prerequisites are installed/configured on the new DB server:
    1. Server 2008, 2012 - install Application Server role from Server Manager, enable "COM+ Network Access", and "Distributed Transactions" (check "Incoming Remote Transactions", check "Outgoing Remote Transactions", and uncheck "WS-Atomic Transactions")
    2. Instance of SQL must have:
      • Collation set to "case insensitive", (SQL default) otherwise the database will not install.
      • SQL Authentication set to SQL Server and Windows (mixed mode)
      • COM Security settings configured as per the DL 32 Server Install Guide. Contact DocLink Support to request this guide.
    3. COM Security settings configured as per the DL 32 Server Install Guide. Contact DocLink Support to request this guide.
    4. Set the following services to start "Automatically":
      • Windows Distributed Transaction Coordinator (DTC) Service
      • MSSQLSERVER Service
      • SQL Server Agent
  2. As a precaution, on your production DocLink application system, log into the DocLink Smart Client. On the Administration tab, click on the System Settings tile, then Global Settings.  Take a screen shot of all entries listed in the window. You want to be sure that after your new DB server has been re-keyed (Step 6) any additional custom global settings used by DocLink are not accidently dropped or lost.
  3. On the new server, install a blank doclink2 database from the DocLink installation media (this will auto create the doclink20 SQL user). Restore a backup of your production DB as doclink2 on the new server. You will need to recreate the doclink20 SQL login manually.

    OR

    Detach your current production DB, copy it to the new server, and attach it to the new instance of SQL. You will need to recreate the doclink20 SQL login manually.
  4. Run the following script in SQL to resolve the orphan SQL user that results after the database restore: 
    USE doclink2;
GO
sp_change_users_login @Action='update_one', @UserNamePattern='doclink20', @LoginName='doclink20';
GO
        
  5. Since licensing is done on a per-server basis, you will need to delete all rows from the SystemLicensing table in the doclink2 database. Run the following script to truncate the table: 
    TRUNCATE TABLE [SystemLicensing]
        
  6. Log into the Smart Client. Fill in the registration form and submit it for new license keys. If no internet connectivity is available, the key request file can be emailed to Support@altec-inc.com. Please refer to the Licensing and Registration.pdf document for instructions.
  7. On the desktop of your production application server, open the DB Password Administrator (DBPwdTool.exe). This file is located in %Program Files (x86)%\Altec\doc-link3x.
    1. Right-click on it and choose 'Run as Administrator'.
    2. Change the DB server name.
    3. Click on the Test... button. You should get a message in the status bar that the DocLink database was found.
    4. Click OK to exit the editor and update the database setting.
    5. Restart all DocLink services.

    If there is a separate IIS server hosting the DocLink Remote Server components, repeat Step 7 on that server.
  8. On the DocLink database server, you will need to create a linked server in SQL from the new doclink2 DB server to your Accounting Application's DB server. This is necessary for the GL Smart Form.
  9. If you are using auto-indexes of any sort or Smart Forms, you will also need to update the Data Source:
    1. In Smart Client, navigate to Data Sources tile on the Administration tab.
    2. Double click on the data sources listed one at a time
    3. Modify the connection string to reflect the new database server name.
  10. Update the Web Manifest Utility. From the Application Server (or IIS Server):
    1. Go to Start > Programs > Altec > Web Manifest Utility. Alternatively, you can browse to %Program Files (x86)%\Altec\doc-link3x\Web.
    2. Update the DB server name.
  11. Look to see if there are any SQL Jobs set up on the old DB server and recreate them on the new server. Often there is a SQL job set up to refresh the AP data (cache tables) for the distribution stamp. Also check for any SQL jobs set up to do any automated tasks that are not scheduled within Event & Data Manager.

Moving the Document Store (IMStore)