Step 5: Reviewing the Migration Results

The document type displayed after the title is based on the DocType_Name property of the original Info Pak document.

The Migration Wizard automatically verifies content from the Management Center. Running content verification activates the Info Pak child output on the server.

Optionally, if you want to execute content verification on a regular basis, use Microsoft Windows Task Scheduler to setup a task on the Server to periodically execute the ContentVerification.exe file. Refer to Scheduling Automated Tasks in the companion manual Administration for instructions on creating tasks on the server.

After migration is complete, perform the following quality assurance and configuration tasks:

1. Review the document check-in log (generated if you have checked documents into uPerform). This log is located in the following default location: C:\Users\[username]\AppData\Roaming\[applicationdirectory]\version X.xx\Logs\BatchCheckin. The log filename is prefaced with 'BatchCheckIn_' and is date- and timestamped.
2. Confirm that unintended documents have not been migrated.
3. Confirm the folder assignment of all documents.

Using the Info Pak Properties Specified in the uPerform Project

After migration, a link to Info Pak properties is displayed on the project properties page.

These Info Pak properties only exist after importing Web Architect data during migration. After initial creation, these properties can only be modified from the uPerform system.

If you are not modifying your Info Pak publishing options (for example, specifying to use websafe paths or specifying additional output formats) and the location of the published output does not change, you do not need to edit these Info Pak properties from within the Editor.

If your publishing options or location change, you must edit these properties. Click + to the left of Info Pak Properties to expand the properties list.

In the event you do modify publishing options and/or content location, you must modify the following properties:

1. The relevant child document type to add formats to the list
2. Content Location: You do not need to re-migrate data again if the content location is changed. Simply change the value of this field and run content verification.
3. Web Safe Paths: Change the value in this field if all documents are republished with a different websafe path setting in the Info Pak - Configuration tool and run content verification.

You cannot add new custom child document types or new assimilated document types from this interface. If you have new document types, you must execute a new migration.