Migrator for Notes to SharePoint 7.1

Configuring Link Tracking Service

To configure the Link Tracking Service for a site collection

Open Migrator for Notes to SharePoint Services configuration page.

Select the site collection on which that you want to enable the Link Tracking Service.

Select Enable Quest Link Tracking Service check box.

Enter a database server and name. This is the SQL Server instance and name that contains the Link Tracking database. This value was set by the Migrator for Notes to SharePoint Services installer but may be overridden

Select a security authentication. These are the credentials that the Import Service or locally running instances of Migrator for Notes to SharePoint should use when accessing the Link Tracking database. This value was set by the Migrator for Notes to SharePoint Services installer but may be overridden.


	IMPORTANT: Use of Windows authentication is strongly recommended. To use SQL authentication, specify the credentials which will be used to connect to the database.

Select a Page Redirector Location to redirect users to the current location of the target document, and Redirection Behavior to determine if users should be redirected automatically (if possible) or if they should first see information about the target document.

Click the Update links in the Link Tracking Database link, if the location of your migrated documents has changed and update the references to the documents. For more information, see Link Tracking Updater.

Enter the old URL prefix of the documents as they currently appear in the Link Tracking database.

Enter the new URL prefix that you want to be the replacement for the above URL prefix.

Click Preview to preview the current references to documents as stored in the Link Tracking database and the proposed new references to the documents.

Click Update when you are ready to make the changes in the Link Tracking database. If you have lots of documents to update, you will see a status page that updates every few seconds and then a final results page.

Click Finalize/update links in migrated documents link, if you want to update your migrated documents to permanently, replace all Dynamic Links with Direct Links to the last known location of the target documents, or to change the location of your Redirector Page. For more information, see Link Tracking Updater.

Select the documents you want to migrate. Select:

All migrated documents: to update all migrated documents in the Link Tracking Database.

All documents migrated to a specific Web Application: to migrate the documents in a particular web application.

All documents migrated to a specific Site Collection: to migrate the documents in a particular site collection.

Select the links in the migrated documents to update.

Select what you want to do with the links to the migrated documents. Select:

Leave as Dynamic Links: to leave the Dynamic Links as they currently are.

Finalize with Direct Links: to replace the Dynamic Links with direct links to the migrated documents (that is, their new URLs in SharePoint).


	CAUTION: You should only perform this operation when you are sure that the documents your links are pointing to are indeed "final" and that they are not still moving around. If you have moved (or plan to move) these documents or otherwise change their external addresses, be sure to run the "Update links in the Link Tracking Database" tool before you finalize your links.

Replace with an Alternate URL: to change the Dynamic Link to reference a different Redirector Page or to a static URL. Be sure to use the {0} notation to encode the unique identifier of the target document in the link.

Select what you want to the do with link to the documents that have not been migrated. Select:

Leave as Dynamic Links: to leave the Dynamic Links the way they currently are. This is the recommended option.

Finalize with Direct Links: to change these Dynamic Links to Direct Links that point to the original locations of target documents in Notes/Domino.


	NOTE: notes://... URLs are not allowed in SharePoint Items. So finalizing such links in (for example) rich text fields in List Items renders them completely inoperable. It is safe, however, to finalize notes://... links in library files such as InfoPath or Word documents.

Replace with an Alternate Url: to change the Dynamic Link to reference a different Redirector Page or to a static URL. Be sure to use the {0} notation to encode the unique identifier of the target document in the link.

Click Preview to preview the current references to documents.

Click Finalize when you are ready to make the changes.

Click Save.

Configuring Import Service for a SharePoint site collection

To enable and configure the Import Service client settings for a site collection

From SharePoint Central Administration, select General Application Settings | Configure Migrator for Notes to SharePoint Services.

Select the site collection where you want to enable the Import Service.

Select the Enable Import Service check box.

Enter the Import Service Address. This is the URL that remote Migrator for Notes to SharePoint clients should connect to in order to migrate content to sites in this site collection. This value was set by the Migrator for Notes to SharePoint Services installer but can be overridden.

Enter an EndPoint Name. This is the Windows Communication Foundation (WCF) endpoint that remote Migrator for Notes to SharePoint clients should connect to in order to migrate content to sites in this site collection. Each of the choices listed here correspond to WCF binding that is configured in the Import Service’s web.config file and the remote clients config file. Migrator for Notes to SharePoint Services, Migrator for Notes to SharePoint currently supports two connection modes:

•

Secure HTTP (using Web Services Security)

•

Secure HTTP (using SSL for Security)

Enter an Application Pool Identity. The application pool identity is what the remote clients should check for when connecting to the Import Service. This is required by Windows Communication Foundation to prevent spoofing when running the Import Service with domain accounts. This may be left blank if using built-in accounts such as Network Service.


	NOTE: The application pool must have administrative rights on the local computer and any target SharePoint site you plan to migrate to. The application pool will also need read, write and run privileges for the Link Tracking database if Link Tracking is enabled.

Enter a file path to the Shared Files folder.


	NOTE: To improve performance during migration, a shared folder can be used when transferring data to the Import Service. If the shared folder option is used, attachments are extracted to disk files instead of loading them all into memory during the data transfer. This is crucial when transferring large files that can take up more memory than what is available. This field is optional. If no shared folder is defined, the data will be transferred as encrypted bits in memory.

This shared folder needs to be accessed by both the clients and the server; the clients will copy files to that location, and then the server will access those files when writing to SharePoint. Specify the path to this folder in the Shared Files folder path field. If clients need to use a different path to access this shared folder (for instance, a UNC path), specify this path in the Shared Files Client Access Path field. This field is optional. For more information, see Import Service shared folders.

If you want to test your import service settings, click the Test Import Service Settings link.


	NOTE: Be sure to turn off your pop-up blocker for the site before clicking the Test button


	NOTE: User and Group Mapping can be performed by the client rather than the Service. If you prefer to have the client perform the mapping, the below User and Group Mapping configuration is not required. You will need to turn on client mapping using the SharePoint tab of the Global Options of the Console or Designer.

Select an input translation for the User Mapping.

Notes names can come in different formats (Canonical, Abbreviated, Common). If your input data (from Notes) is in one format and your XML mapping file or ADSI query is using a different format, you should specify a translation option.

Select a mapping source.

SharePoint tracks "users" as numeric indexes into the SharePoint Site Collection Users list. When using the "Preserve Created/Modified Identities" option in your Job Definition, or when attempting to migrate a Notes name field to a SharePoint User field, Migrator for Notes to SharePoint Services will attempt to map Notes names to Site Collection User identities based on the rules configured here. There are currently three options for doing this:

•

Treat input as Login Name - The input data provided must equate to a valid Windows login name. Simple name translations are provided (for example, reformat the Notes name "Joe Cool/NMSP" to "NMSP\Joe Cool".

•

Use ADSI/LDAP Lookup - Use the input data (most likely the Notes Name) as the basis for an Active Directory (or other LDAP) lookup to find the correct Windows login name. If you select this option, the following parameters can also be specified:

•

ADSI path: You should specify the path to the Active Directory (or other LDAP) server that contains the user mappings. You can actually use any ADSI path here including "GC://" for the global catalog and "WinNT://" for the local metabase.

•

Query String: You should specify a valid query string for finding the user based on the Notes Name. For example, if your policy is to store the Notes Name in the Description field of Person records in Active Directory, you might specify "(&(ObjectClass=Person)(description={0}))" as the Query String.

•

ADSI login name and ADSI password: If your directory requires authentication for searching, you can specify that here.

•

Use Text File Lookup - Use the input data (most likely the Notes Name) as the basis for a lookup in an XML or comma-delimited text file to find the correct Windows login name. In practice, most organizations that have both Notes and Active directory will have the mapping of names stored somewhere and it is usually a simple matter to write a script to generate a simple mapping file. If you select this option, the following parameters can also be specified:

•

Path: The location of the mapping file.

•

Format: The mapping file can be formatted as an XML file or a Comma Delimited file. An example of each format is shown below:

<?xml version="1.0" encoding="utf-8" ?>

</userMappings>

</groupMappings>

</identityMappings>

Joe Cool/NMSP, NMSP\jcool

Max Smart/NMSP, BUNTING\mike

If translating, enter an output translation.

If you want to test the user mapping settings, click the Test User Mapping Settings.

Select an input translation for the Group Mapping.

Select a mapping source. For more information, see Select a mapping source..

If translating, enter an output translation.

If you want to test the group mapping settings, click the Test Group Mapping Settings.

You can enable SSL and logging with the Import Service.

Enabling SSL for Import Service

To enable SSL transport

If you do not already have one, create a self-signed server certificate.

In the IIS, add a site binding of HTTPS type for the Import Service with the certificate file.

Install the certificate on the client computer.

From your browser, enter https://<YOUR_DOMAIN_NAME>/ImportSession.svc

You can find your domain name from Server Certificates in IIS Manage. You must enter your domain name exactly how it appears in the Issued To column.

Click Continue to this website (not recommended).

Click Certificate Error next to the address bar.

Click View certificates.

Click Install Certificate.

Follow Certificate Import Wizard steps and accept all defaults to add the certificate.


	NOTE: If you do not perform these steps, the following error message appears: “Unable to connect to the Migrator for Notes to SharePoint Import Service ‘ https://<YOUR_DOMAIN_NAME>/ImportSession.svc’. Could not establish trust relationship for the SSL/TLS secure channel with authority <YOUR_DOMAIN_NAME>”.