Migrator for Notes to SharePoint 6.16 - User Guide

Notes tab

Notes tab

Table 3. Notes tab

Item	Description
Password for local Notes ID	This is the password for your local file. It will be stored in an encrypted format in the "UserOptions.config" file in the application data directory under: Quest/Migrator for Notes to SharePoint. To support Notes IDs that require more than one password, enter the passwords starting with a vertical bar character, with a vertical bar character separating each password and ending with a vertical bar character. For example: |password1|password2|password3|
Override default Notes.INI file	By default, Migrator for Notes to SharePoint will use the default Notes configuration file in use by your Notes client. In rare cases, you may wish to specify an alternate configuration file here
Configure Repository Database	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. The Quest Repository database is a Notes database where all the data for the Migrator for Notes to SharePoint Console is stored. If you kept the default settings during the installation of the console, it is QuestRepository.nsf. 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. • Database Server: Specify a local database by leaving it as (local), or a remote one by entering the IP address or host name of the database server, and clicking Select... to select the database. 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. • Database Path: QuestRepository.nsf is the default value. NOTE: If the name or location of the Repository changes, you must restart the Console for the changes in these fields to take effect.
Configure User/Group Resolution Server	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. • Directory Server: Notes name for the server from where you would like to scan directory information
Max Group Size	This property limits all group expansion operations to those groups that are smaller than the given number. During migrations, groups that are larger than the Max Group Size will not be written to SharePoint. A warning will be written to the migration log. The default is 100.
Process internal HTTP links as DocLinks	When migrating rich text fields that contain URL links to other QuickPlace/Quickr pages or Domino web pages, Migrator for Notes to SharePoint can detect these links and convert them to use the Link Tracking Service. Select this check box to turn this feature on. 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. NOTE: Enabling this feature is useful in cases where you have Notes documents that link to other Notes documents through Domino URL links rather than true Notes DocLinks. This is especially common in QuickPlace/Quickr and other web enabled Domino applications. Migrator for Notes to SharePoint will recognize URL links that start with the prefix you specify here and will attempt to locate the actual Notes document on the server you specify. If successful, Migrator for Notes to SharePoint will process the link as if it were a true Notes DocLink and make sure that it works correctly with the Link Tracking Service. NOTE: When performing a Doclink Scan, Quickr links are not included as Doclinks, even when this feature is enabled.
Strict data extraction	By default, Migrator for Notes to SharePoint will try to recover from certain errors while querying. If there is a problem reading an item, it will return NULL and automatically skip to the next item. If there is a problem reading a document, it will automatically skip to the next document. If you select this check box, an exception will be thrown when the first error is encountered. This may be helpful when trying to debug why certain data items were not processed.
Override default read cache size	By default Migrator for Notes to SharePoint reads up to 100 records at a time while sending data to SharePoint. In rare memory-constrained conditions, it may be helpful to override this setting to less than that (as low as 1). This may impact performance, but it will help keep the memory footprint down. To change the default size, select this check box and enter the desired size in the field to the right.
Compression Exclusions	This option allows you to specify any file extensions that should never be zipped during migration. This would typically include media files that are already well-compressed and would not benefit from zipping.

Discovery tab

Discovery tab

NOTE: This tab is only available when you open Options from the Console.

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.

 

Table 4. Discovery tab

Item	Description
Domain/Database Catalogs	This button opens the Configure Catalog Databases dialog box. This dialog box is where you define the location of the Database Catalogs or Domain Catalogs that you want to extract information from. The number on the button shows how many catalog databases are defined. To add a catalog click Add. To edit, select an entry and click Edit. To delete, select an entry and click Delete. Both Add and Edit opens the Configure Catalog Database dialog box • Server: If the server is local, this can be left blank • Database: Catalog name (default is catalog.nsf) NOTE: Not all organizations run the Domino Cataloger process, which keeps catalog.nsf databases updated with current information. If you are not sure, simply do a direct scan instead.
Direct Server Scan Locations	This button opens the Configure Scan Locations dialog box. This dialog box is where you define the location of the servers you want scanned during the database discovery. The number on the button shows how many items are defined. To add a server click Add. To edit, select an entry and click Edit. To delete, select an entry and click Delete. Both Add and Edit opens the Define Scan Location dialog box • Scan Server: If the server is local, this can be left blank • Scan Path: Leave this blank if you want Migrator for Notes to SharePoint to scan the entire data directory on the specified server.
Known QuickPlace Servers	This button opens the Known QuickPlace Servers dialog box. This dialog box is where you define the QuickPlace Servers that you want analyzed during the Discover QuickPlace Organization process. For more information, see QuickPlace/Quickr discovery To add a server click Add and enter the server name. To edit, select an entry and click Edit. To delete, select and entry and click Delete. To add several servers to the Known QuickPlace Servers list, copy them to your clipboard using a comma, semi colon, or a new line to separate each server name. Click the Paste button to copy them to the list.
Known Quickr Servers	This button opens the Known Quickr Servers dialog box. This dialog box is where you define the Quickr Servers that you want analyzed during the Discover Quickr Organization process. For more information, see Domino.Doc discovery To add a server click Add and enter the server name. To edit, select an entry and click Edit. To delete, select and entry and click Delete. To add several servers to the Known Quickr Servers list, copy them to your clipboard using a coma, semi colon or a new line to separate each server name. Click the Paste button to copy them to the list
Known Domino.Doc Servers	This button opens the Known Domino.Doc Servers dialog box. This dialog box is where you define the Domino.Doc Servers that you want analyzed during the Discover Domino.Doc Organization process. For more information, see Domino.Doc discovery To add a server click Add and enter the server name. To edit, select an entry and click Edit. To delete, select and entry and click Delete. To add several servers to the Known Domino.Doc Servers list, copy them to your clipboard using a coma, semi colon or a new line to separate each server name. Click the Paste button to copy them to the list.
Excluded User Names	This button opens the Excluded User Names dialog box. Add any user names that you do not want taken into account during any of the analysis (for example: You might not want the Administrator sessions or updates by scheduled Server agents taken into account when reporting on how frequently a database is used). The number on the button shows how many user names are defined. To add an excluded user, click Add and enter the user name. To edit, select an entry and click Edit. To delete, select and entry and click Delete. To add several users to the Excluded User Names list, copy them to your clipboard using a coma, semi colon or a new line to separate each user name. Click the Paste button to copy them to the list. If you change the excluded user list after doing a data scan, you can use the Recompute database details action to update the data in the Console without having to re-scan the Notes database.
Preferred Notes Servers	This button opens the Preferred Notes Servers dialog box. This dialog box is where you add the servers that you want in the Preferred list. The Preferred list determines which replica is chosen to be displayed on the Unique Replicas view in the case where the discovery process has discovered multiple replicas of the same database on different servers. The number on the button shows how many servers are defined. To add a server click Add and enter the server name. To edit, select an entry and click Edit. To delete, select and entry and click Delete. To add several servers to the Preferred Notes Servers list, copy them to your clipboard using a coma, semi colon or a new line to separate each server name. Click the Paste button to copy them to the list.
Domino Directory Servers	This button opens the Domino Directory Servers dialog box. This is where you define the servers used by the Discover Directory Entries process. This process scans Domino Directories to collect additional information about the Notes databases in your environment. In particular, it detects when databases are configured as Mail-in databases (that is, they have addresses that users can send mail to). The number on the button shows how many servers are defined. To add a server, click Add and enter the server name. To edit, select an entry and click Edit. To delete, select and entry and click Delete.

Analysis tab

Analysis tab

NOTE: This tab is only available when you open Options from the Console.

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.

 

Table 5. Analysis tab

Item	Description
Effort estimation units label	Controls what units should be displayed on the estimation tab of Database properties and Class rules.
Analysis time limit per database	Sets a limit for how much time Migrator for Notes to SharePoint will spend analyzing one database. If this time is exceeded, the scan will stop and an exception will occur. If you have Migrator for Notes to SharePoint set to log exceptions without interruption, it will immediately move on to the next database.
Cache Database Script	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.
Local Design Copies Folder	Defines where the database design copy is stored. For information on created a design copy, see the Analyze databases action.

Console tab

Console tab

NOTE: This tab is only available when you open Options from the Console.

 

Table 6. Console tab

Item	Description
Global Exclusions	During the discovery processes, certain information may be immediately excluded based on the configured Exclusion and Filtering rules defined in this tab. Setting Global exclusions will prevent certain information from being loaded into memory and may result in better performance. • Servers: This is where you specify servers to exclude. • Database Classes: This is where you specify database classes to exclude. For more information, see Notes databases • Template Names: This is where you specify template names to exclude. • Categories: This is where you specify categories to exclude. • File Names: This is where you specify file names to exclude. • Folders: This is where you specify folders to exclude. 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	For each of the below tasks that are checked, Migrator for Notes to SharePoint can automatically set a database’s status of the task to complete as it completes the task for the database. • Design Analyzed • Data Analyzed • Targets Identified • Migration Jobs Assigned • Content Migrated
Edit the list of Database Disposition choices	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. NOTE: Migrator for Notes to SharePoint does not take the indicated actions, such as deleting the database, for you automatically. Rather the decisions you make about each database are recorded and may be used for reporting, filtering and data export.
Limit console reports to this number of databases	Set this higher or lower to limit the number of databases processed by the console reports. This is a global default for all reports but individual reports may be customized to increase this limit.This value helps prevent the console from exhausting the available memory while rendering complex reports against a large number of databases. The default is 50,000. Choosing a value of 0, requires each report definition to be customized with its own upper limit before it will render any result.