This button opens the Configure Repository Database dialog box. This dialog box is where you define the locations of the Quest Repository database and Task History Repository database. However, you can store your Task History data in a different database by specifying the database on the Task History Repository tab. By default, the Task History Repository database is the same as the Quest Repository one.
NOTE: The current version does not support multi-user access to the Repository database. You may use your Notes client to replicate your Repository database to a Domino server but you should not allow multiple users to update the database. A subsequent version of Migrator for Notes to SharePoint will support concurrent shared Repository usage.
| |||||
This button opens the Configure Domino Server Location dialog box. The Domino Directory server listed here is the one used for expanding groups when generating SharePoint Groups from ACL Groups. For more information, see Migration Targets tab. To manage the servers in the list, select Edit favorites... from the dropdown list, and add, edit or delete a server. | |||||
When this check box is selected, the Translations button is active. The Translations button opens the Configure Link Translations dialog box. This is where you specify the URL prefixes you want to convert and from which Domino servers. | |||||
Before you can start managing your migration process, Migrator for Notes to SharePoint must identify all of your Notes databases. The Migrator for Notes to SharePoint Console supports several modes of discovering Notes databases. Discovery occurs by reading the information in your organization's Database Catalog or Domain Catalog or by directly scanning the Domino server folders, or both. For more information, see Database discovery. The configuration on this tab is used during the database discovery process. This tab must be filled out before you can run this process.
The upper half of the Analysis tab stores the global option for picking which algorithms you want to use for automatically assigning database complexities. The following example says that we will use a weighted mix of Data Complexity (50%) and Design Complexity (100%) to compute the overall complexity recommendation. The database’s overall complexity recommendation is found in the Complexity tab of the Database Properties.
Allows you to cache database scripts to the path <MNSP_Home>\ScriptScan. When this option is checked, MNSP caches the scripts from an existing DXL file, instead of reading source Notes database and creating new scripts. | |
Defines where the database design copy is stored. For information on created a design copy, see the Analyze databases action. |
To add several values to one of the above exclusion lists, copy the values to your clipboard using a coma, semi colon or a new line to separate each value. Click the Paste button to copy them to the exclusion list. | |||||||||||||
Automatically set Migration Status fields as console operations are performed |
|||||||||||||
The disposition of a database indicates what you want to do with the database in the migration process (for example, 'Migrate to standard SharePoint targets' or 'End-of-life'). The database’s disposition is set in the Migration Status tab of the database properties. To edit the list of available database dispositions for a database, select the Database Disposition button to open the Database Disposition dialog box. To create a new disposition, click Add. To edit an existing disposition, select the disposition from the list and click Edit. To delete an existing disposition, select the disposition from the list and click Delete. | |||||||||||||
Choosing a value of 0, requires each report definition to be customized with its own upper limit before it will render any result. |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center