Viewpoint
Sign in
Sections Project Migration
Manual informationProject MigrationApplication version 7.0 December 16, 2021 · Document version 7.0 (August 2021)
Source title

Viewpoint ™ Project Migration Guide

Application version

Application Version: 7.0 December 16, 2021

Document version

Document Version: 7.0 (August 2021).

Rights and trademarks

© 2021 Conduent, Inc. All rights reserved. Conduent and Conduent Agile Star are trademarks of Conduent, Inc. and/or its subsidiaries in the United States and/or other countries. Other company trademarks are also acknowledged.

Latest revision

1.1 | August 27, 2021 | Rebranded adhering to the latest Conduent brand central documentation standards/guidelines. | Technical Writer

Document conventions

Convention

Explanation

Bold

For file names, commands, fields, menus, options, and window names.

Courier New

Commands as you should type them.

Lucida Console

Example output generated by the system.

Italics

For configuration variables, including variable portions of file names and URLs. Also indicates a document name.

Note / Blue Callout

The Blue Callout text indicates information that is of special interest or importance, an idea that could be useful or additional information about a product or a feature.

The Caution icon along with the text indicates actions that can lead to problems in system operation or configuration settings if the instructions are not followed properly.

Revision history

This section tracks the initial creation of the document after each major version thereafter.

Ver:

Date

Description

Reviewed / Approved By

1.0

Apr 12, 2013

Initial Version

Team

1.1

August 27, 2021

Rebranded adhering to the latest Conduent brand central documentation standards/guidelines.

Technical Writer

Migrating Viewpoint Projects#

The following steps outline the process for migrating a Viewpoint Project from one location to another. This typically involves relocating the Processing database, Review database and corresponding files.

  1. Copy the entire project folder to the new location on the file server. The same instructions will apply, if the project is being moved to a new location on the existing file server or a completely new file server.
  2. Restore a backup of the Processing database to the new Processing SQL Server.
  3. In the Projects table of the LDControl database on the Processing SQL Server, add a new record for the migrated project. For ease of use, you may copy the record from the old SQL Server to the new server. All or some of following fields need to be modified such as, CompanyID, DBServer, DBName, ReviewDBServer, ReviewDBName, FileServer, and PartnerLDControl.
  4. Copy the Update Processing Paths query from this document to a new query window for the restored Processing database. Throughout the query, you will see the following two strings that must be updated.
    1. \\OldServer\OldShare\OldFolder
      • This needs to be updated with the info from the recently restored DB. The ‘update’ line will indicate the table, and the ‘set’ line will indicate the field name. While updating this info in the query, you only need to include the portion before file type indicator. For example, if the DB has ‘\\Files03\data3\P00000\EFile’ only include ‘\\Files03\data3\P00000’
    2. \\NewServer\NewShare\NewFolder
      • This needs to be updated to match the new file share info. Only update the ‘matching’ portion from 4a. For example, ‘\\ABC01\data1\P00000’
  5. Restore a backup of the Review database to the new Review SQL Server.
  6. In the Projects table of the LDControl database on the Review SQL Server, add a new record for the migrated project. For ease of use, you may copy the record from the old SQL Server to the new server. All or some of following fields will need to modified such as CompanyID, DBServer, DBName, ReviewDBServer, ReviewDBName, and FileServer.
  7. Copy the Update Review Paths query in this document to a new query window for the restored Review database. Throughout the query, you will see the following two strings that must be updated.
    1. \\OldServer\OldShare\OldFolder
      • This needs to be updated with the info from the recently restored DB. The ‘update’ line will indicate the table, and the ‘set’ line will indicate the field name. When updating this info in the query, you only need to include the portion before file type indicator. For example, if the DB has ‘\\Files03\data3\P00000\EFile’ only include ‘\\Files03\data3\P00000’
    2. \\NewServer\NewShare\NewFolder
      • This needs to be updated to match the new file share info. Only update the ‘matching’ portion from 7a. For example, ‘\\ABC01\data1\P00000’
  8. Now that both the Processing and Review databases have been restored, security rights for the linkage between the two needs to be enabled.
    1. On the Processing SQL Server, expand the Security node and then expand the Logins node. Right-click the VPLink account and select Properties. In the Login Properties windows, select User Mapping on the left. Check the corresponding Review database in the top grid and then check vp_user in the bottom window. Click OK.
    2. On the Review SQL Server, expand the Security node and then expand the Logins node. Right click the VPLink account and select Properties. In the Login Properties windows, select User Mapping on the left. Check the corresponding Processing database in the top grid and then check vp_user in the bottom window. Click OK.
  9. After performing all the above steps, you can test the results. Right click a document in the Processing application and try to open the Text, TIFF, etc. Similarly, in Review go to a document and check that the various viewers are displaying the file or not. You should also run a keyword search to insure that the index paths are updated correctly.

Note: When migrating large projects, users may experience some slowness when highlighting documents in Review. In an effort to avoid this behavior before it arises, it is recommended to re-index the entire project and update post to Review. This step is not required and can be performed as needed, if highlight speed degradation begins to show.

Update Processing Paths#

--Update Processing Paths—

-- Set the parameter @OldPath and @NewPath before running these queries --

DECLARE @OldPath nvarchar(max)

set @OldPath = '\\OldServer\NewShare\ProjectFolder'

DECLARE @NewPath nvarchar(max)

set @NewPath = '\\NewServer\NewShare\T00001'

--Query 1--

update Media

set EFileRootPath = replace (EFileRootPath,@OldPath, @NewPath),

TextRootPath = replace (TextRootPath,@OldPath, @NewPath),

HTMLRootPath = replace (HTMLRootPath,@OldPath, @NewPath),

--PDFRootPath = replace (PDFRootPath,@OldPath, @NewPath),

--Doublecheck PDFRootPath field is nonexistent

TIFFRootPath = replace (TIFFRootPath,@OldPath, @NewPath),

--XMLRootPath = replace (XMLRootPath,@OldPath, @NewPath),

--Doublecheck XMLRootPath field is nonexistent

SlipsheetRootPath = replace (SlipsheetRootPath,@OldPath, @NewPath),

IndexRootPath = replace (IndexRootPath,@OldPath, @NewPath)

--Query 2--

update [index]

set IndexPath = replace(IndexPath,@OldPath, @NewPath)

Update Review Paths#

--Update Review Paths—

-- Set the parameter @OldPath and @NewPath before running this query --

DECLARE @OldPath nvarchar(max)

set @OldPath = '\\OldServer\NewShare\ProjectFolder'

DECLARE @NewPath nvarchar(max)

set @NewPath = '\\NewServer\NewShare\T00001'

IF object_id('tempdb..#DISABLETRIGGER_ReviewEDoc') IS NULL BEGIN create table #DISABLETRIGGER_ReviewEDoc (col int) END

IF object_id('tempdb..#DISABLETRIGGER_ReviewEDocRedact') IS NULL BEGIN create table #DISABLETRIGGER_ReviewEDocRedact (col int) END

IF object_id('tempdb..#DISABLETRIGGER_ReviewEDocRedactSection') IS NULL BEGIN create table #DISABLETRIGGER_ReviewEDocRedactSection (col int) END

update ReviewEDoc

set M_EFileRootPath = replace(M_EFileRootPath,@OldPath, @NewPath),

M_TextRootPath = replace(M_TextRootPath,@OldPath, @NewPath),

M_HTMLRootPath = replace(M_HTMLRootPath,@OldPath, @NewPath),

-- M_PDFRootPath = replace(M_PDFRootPath,@OldPath, @NewPath),

M_TIFFRootPath = replace(M_TIFFRootPath,@OldPath, @NewPath),

-- M_XMLRootPath = replace(M_XMLRootPath,@OldPath, @NewPath),

M_SlipsheetRootPath = replace(M_SlipsheetRootPath,@OldPath, @NewPath),

i_indexpath = replace(i_indexpath,@OldPath, @NewPath)

update Delivery

set FolderRootPath = replace (FolderRootPath, @OldPath, @NewPath)

update DeliveryDoc

set SystemNativePath = replace(SystemNativePath,@OldPath, @NewPath),

SystemTextPath = replace(SystemTextPath,@OldPath, @NewPath),

SystemSlipSheetPath = replace(SystemSlipSheetPath,@OldPath, @NewPath),

SystemTIFFPath = replace(SystemTIFFPath,@OldPath, @NewPath)

update ReviewEDocRedact

set RedactPath = replace (RedactPath, @OldPath, @NewPath)

update ReviewEDocRedactSection

set RedactFileName = replace (RedactFileName, @OldPath, @NewPath)

drop table #DISABLETRIGGER_ReviewEDoc;

drop table #DISABLETRIGGER_ReviewEDocRedact;

drop table #DISABLETRIGGER_ReviewEDocRedactSection;