Converse agora com nosso suporte
Chat com o suporte

Migrator for Notes to SharePoint 7.1 - User Guide

Migrator for Notes to SharePoint Migrator for Notes to SharePoint Console
Overview Console configuration using the setup wizard Advanced configuration options Database discovery QuickPlace/Quickr discovery Domino.Doc discovery Discover directory entries Import database records Notes databases Applications Classification Rules Classification Rule Properties SharePoint Targets Scheduled tasks Reports Task history Link Analyzer/Updater/Finalizer License
Migrator for Notes to SharePoint Designer Migration jobs Appendix: Reference information

SQL Server

This is where you select the target SQL Server database and tables that will be the destination of migrated data. It is also where you select (or create) a Data Target Definition file that describes how data should be written to this database.

c
if you want to generate a new table that does not exist in the SQL database described on the SQL Server tab, select Create Tables. The new table will be based on the Data Fields in your Target Data Definition. The Add Table Fields checkbox is automatically selected as you select Create Tables.
e
select the Migrate attachment icons as image files check box to allow the original attachment icons in Notes to appear in SharePoint.
5
From the Data Fields tab, click Load from SQL Server database. This will automatically create Field definitions for all the writable fields found in the database tables you selected. Similarly, the Load from Source Fields button will automatically create Field definitions for all the columns in your Source data definition.
You can also add (or modify) fields one at a time by clicking Add (or selecting an item in the list on the left of the page) and then editing the properties in the dialog box on the right of the page.

Folder

This is where you select a target folder created on a local drive to migrate data.

4
From the Data Fields tab, click Load from SharePoint List. This will automatically create Field definitions for all the writable fields found in the SharePoint List you selected. Similarly, the Load From Source Fields button will automatically create Field definitions for all the columns in your Source data definition.
You can also add (or modify) fields one at a time by clicking Add (or selecting an item in the list on the left of the page) and then editing the properties in the dialog box on the right of the page.

Mapping data

The Map Data tab is where you describe how the fields in your Data Source Definition map to the SharePoint fields in your Data Target Definition. In most cases, the Auto Map function will do the mappings for you, but you can also override the defaults.

If you have selected Source and Target Data Definitions, a default set of field mappings will be generated for you using the AutoMap Names property for the target data field definitions. You can refresh these mappings by clicking the Auto Map button.

If you have multiple source fields that you are mapping to one target Note field using the target field’s AllowMultipleSources property, the order of the concatenated fields depends on the order of the fields in this field mapping table.

1
Click Add.

Setting up user mapping and security mapping

SharePoint tracks "users" as numeric indexes into the SharePoint Site Collection Users list. When Migrator for Notes to SharePoint encounters user names, it will attempt to map them to Site Collection User identities based on the mapping rules in your Global Settings. For more information, see Customizing global options. This can occur:

On a per-job basis, you can decide what happens if no user mapping is found for a particular Notes name. The record can be rejected or defaults can be applied depending on the If user mapping fails setting.

The details of how user mapping occurs is controlled by the Global Options.

Migrator for Notes to SharePoint 's security mapping options will map various access control properties of the source Notes database, QuickPlace, Quickr, or Domino.Doc cabinet to the equivalent constructs in SharePoint.

The Map Notes Users to Domain Users option will cause any Notes users listed in the source database's Access Control List to be added to the target SharePoint list or library. The Notes user names are mapped to Site Collection identities based on the rules configured in the tool's User Mapping and those Users are granted access to the target SharePoint list or library.
The Map Notes Groups to Domain Groups option will cause any Notes groups listed in the source database's Access Control List to be added to the target SharePoint list or library. The Notes group names are added to the Site Collection as external groups and are granted access to the target SharePoint list or library. Each group name must correspond to an actual Domain group.
The Expand Notes Roles to SharePoint Groups option causes a new SharePoint Site Collection Group to be created for each Role defined in the Notes database ACL.
The Expand Notes Groups to SharePoint Groups option allows you to take what was once a Domino Directory group (scoped to the entire Notes Domain) and convert it to a SharePoint group (scoped to just one Site Collection). As part of this conversion, the tool will query the Domino Directory for any groups listed in the ACL, extract all its members (expanding any sub-groups as needed), and add those members to the new SharePoint group.
If the Map Reader/Author fields option is set, then any Reader Names or Author Names items encountered in a particular Notes document will cause a permission list to be generated on the corresponding SharePoint record. This new permission list will only grant read access to the users and groups named in the Reader Names field and will only grant edit access to the users and groups named in the Author Names field.
Convert to original notes:// URLs (for use with the Notes client) - When generating HTML or MIME documents from Notes Rich Text fields, any DocLinks, ViewLinks, and DatabaseLinks that are encountered are converted to "Notes URLs" (for example notes:///85256B20007EED50/38D46BF5E8F08834852564B500129B2C). On machines where the Notes client is installed, such a URL allows Notes to open to the correct document, view, or database.
Use the Quest Link Tracking Service - This option utilizes the Link Tracking Service, which ensures that Notes DocLinks continue to work before, during and after the migration process, regardless of the order of document migration. The service maintains a record of every document that is ever migrated and guarantees that users clicking on an intra-document link will always get redirected to the current location of the document.
Convert to a link to the specified URL - This option replaces each DocLink with a link to a fixed generic web page.
Convert to http:// URLs (for use with the Domino server) - This option prompts you for an additional field URL for Converted DocLinks. To allows you to map the "notes:///" portion of the Notes URL to point to a Domino web server where the linked-to database exists. For example, if you specify "http://proposion.com/" in the URL for Converted DocLinks field, the URL would be changed to "http://proposion.com/85256B20007EED50/38D46BF5E8F08834852564B500129B2C".
Convert to original notes:// URLs (plain text) - When generating HTML or MIME documents from Notes Rich Text fields, any DocLinks, ViewLinks, and DatabaseLinks that are encountered are converted to "Notes URLs" in plain text (for example notes:///85256B20007EED50/38D46BF5E8F08834852564B500129B2C).
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação