Migrator for Notes to SharePoint 7.4 - User Guide

Managing migration jobs

Migrator for Notes to SharePoint Jobs consist of the following:

In other words, everything you entered on the "Notes", "SharePoint" and "Map Data" tabs combine to make a Job Definition.

For an ad-hoc data migration job, you never need to save Job Definitions to disk. However, there are several reasons you might want to save a Job Definition:

To save a Job Definition, click the Save Job button.

To load a Job Definition, click the Load Job button.

To dispose of the current Job Definition and start a new one, click the New Job button.

Migrator for Notes to SharePoint Job Definition files are formatted as XML text. For details on this format, see Job definition file format .

Appendix: Reference information

Notes connection string reference

Migrator for Notes to SharePoint connection strings are used when opening connections to Notes or Domino databases. The syntax takes the form of one or more "parameter=value" declarations separated by semicolons. For example:

Specify the Database or ReplicaID and optionally the Server parameters for the database to connect to. If both the Database and ReplicaID are specified, or if the AltServer is specified, multiple attempts to connect will be made before giving up.

Connection parameter names are not case sensitive; "Server" and "server" are equivalent.

Parameters

Database - Path to the desired database, including the ".nsf" extension. Paths should typically be relative to the Notes/Domino data directory, though full absolute paths can be used to access a local database.

As an alternative to specifying a database path in a connection string, developers can specify "$usermail" as an alias for mail file of the current user. For example, a connection string may include the parameter "database=$usermail". If a server is not specified in the connection string, then Migrator for Notes to SharePoint will attempt to open the user’s mail file on their default mail server. If a server (or "server=local") is specified, then Migrator for Notes to SharePoint will attempt to open the user’s mail file on the specified server first and then fail over to the user’s default mail server.

ReplicaID - Replica ID of the database as a 16 digit hexadecimal number. If both the database and replicaid are specified, multiple attempts to connect will be made before giving up.

Server - Name of server where desired database is located. This can be a short name or fully distinguished hierarchical name. Use "local" or simply omit this parameter when connecting to local database.

AltServer - Name of alternate server to be tried if database cannot be opened at server. This can be a short name or fully distinguished hierarchical name. Use "local" when connecting to a local database.

ImpersonateName - The fully distinguished user name you wish to use to access databases, for example "Joe Cool/Proposion" or "CN=Joe Cool/O=Acme". To enable impersonation for server databases, you need to edit the server's Server document. In the Domino Directory, go to the Security section, and add the user name (from the Notes ID that your .NET process will be using) to the "Trusted Servers" field. This requires Domino 6.0 or higher.

NameServer - Specifies which server to use for looking up users while validating user names and looking up the current user’s mail file. If the "NameServer" parameter is not specified, the default server (where the current database resides) will be used instead.

CacheSize - The number of records that will be loaded into memory at once by the data reader. This value will not impact final results but could impact the memory footprint and performance. The default is 10.