Chat now with support
Chat with Support

Migrator for Notes to SharePoint 6.14 - 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

Migration Jobs

This tab contains the list of all the migration jobs defined for this database. From here you can edit or delete an existing job, create a new job, import a job from a file or export a job to a file. You can run one or all of the listed jobs.

2
Click Edit.
Click New.

For detailed information on defining a migration job using the Job Designer, see “Migrator for Notes to SharePoint Designer” on page 91.

For detailed information on running a migration job, see “Migration Jobs” on page 62.

Migration History

This tab contains the history of all of the migration jobs run for this database. It lists out each job with Date and Time the job was run, the status of the job and the description of the job. Double Clicking a job will open the log file for the job. This information is also viewable in the Task history node.

To migrate the failed items for a job, right click on the job entry, and select Migrated Failed Items. For more information, see Migrating failed items.

Applications

There are cases where one or more Notes databases can be grouped together as a single "application". This is particularly useful when treating multiple databases as a single application is important: namely QuickPlace, Quickr, and Domino.Doc. With these environments, recognizing the patterns of application organization can drive automatic assignment of migration jobs or automation of actual migration jobs.

Applications are "discovered" by running the Discover Quickr Applications, Discover QuickPlace Applications, and Discover Domino.Doc Applications actions. Once these applications are discovered, you can expand the Applications node and drill-down into the Quickr and QuickPlace server/place/room or Domino.Doc server/library/cabinet application hierarchies.

The nodes and sub-nodes displayed here are really just database nodes (the same ones shown in the databases views) except that they are displayed according to the rules of the application abstraction rather than as "plain" databases. To view information about the underlying databases, select the Properties action.

Classification Rules

This Console Tree node is where you can classify your Notes databases. Classification is based on a set of rules which appear as nodes under the Classification Rules node. There are two types of classification, Technical and Business. Both types are organized as a set of prioritized classes.

Each class includes a set of Rules that must match for a particular database in order for that database to be recognized as a member of the class. Each rule may specify that class members should be recognized by folder path, file name, template name, database title, database category, a database manager being listed in the database ACL, any user being listed in the ACL, a design element being used, or membership in a particular application type. A rule can contain one or more matching values and regular expressions may optionally be used. If a class contains more than one rule, the user may specify an AND or OR relationship.

The actual classification process occurs as soon as databases are discovered, when database information is retrieved from the Repository, or when the user refreshes a database view. If you have updated or created new classification rules, refreshing the database view will update the classes of all the databases using the current classification rules.

Rules are prioritized (applied in a predefined order); the first one that matches is used and subsequent rules are not tested. Technical classification and Business classification are computed independently.

Assigned classes are viewable in database views and the database property sheet. If the user manually overrides a database class, this choice is considered "locked" and should not be updated by the automatic classification process if the Locked check box is selected.

The console contains a set of predefined Technical classification rules reflecting well-known database types in typical customer environments. These may be changed or extended. You can also choose at any time to restore the defaults.

Once classes have been assigned to databases, this may be used as the basis for automatically assigning Triage decisions (such as the Complexity index of a database or whether the database should be migrated), effort estimates, target SharePoint destinations, and even the actual content migration jobs that need to be run. Note that while classes are assigned (or reassigned) every time you refresh your database views, the automatic Triage, Target Assignment and Migration Job Assignment only occur when the Apply class rules action is run by the user.

Under the Notes Database tree node are “by class” tree nodes. These nodes display the pre-defined classes and the databases that are members of each class. The By Technical Class tree node contains all of the defined technical classes. The By Business Class tree node contains all of the defined business classes. Select a class to see a list of the member databases in the results view.

Related Documents