Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Script Analysis tab

The Script Analysis tab is automatically populated with you scan design scripts (see Scan Design Scripts ).

This tab contains the following:

Last Script Scan

Gives details, such as date and time of scan, number of lines of script scanned, and size of DXL. Click Show Summary to open the Script Scan Viewer so you can see the scan details of the database design objects.

Database Script Scan

Allows you to run the script scan again by clicking Script Scan.

Script Scan Configuration

Allows you to add or remove database objects.

To remove objects, right-click an object and select Remove Include Objects or click the Remove All button. To add objects, right-click IncludeObjects and select Add Include Object to add one object, or click the Add All button to add all include objects. To change an include object, click an object, and click Edit to select another object.

You can add or remove Categories or Search Terms.

To add a category, right-click a scope and select Add Category. To add a search term, right-click a category and select Add Search Term. A script name such as SearchTtem635629750611275480 is added, but you can edit it. To remove a category, right-click a category and select Remove Category. To remove a search term, right-click a script, and select Remove Search Term.

Once you have added or removed categories or search terms, click Save, then Close. Click Script Scan to run the scan again.

Design Analysis tab

The Design Analysis tab is automatically populated by the Design Scan process. To update the information on this tab, rerun the process using the Scan Design button on the top right of this tab.

This tab contains the following:

Design Element Summary

Forms: Number of forms used in the database
Views/Folders: Number of views/folders used in the database
Agents: Number of agents used
Total: Total number of design elements
Design Details button opens the Design Element Details dialog box

Design Details

From the Design Element Details dialog box (click Design Details), you can view the design elements of the database organized by type.

To exclude particular design elements from the Complexity tab calculations, highlight the elements in the dialog box and click Exclude. The elements that have been flagged for exclusion will have a red ‘X’ next to them. To re-include an element, select it and click the Exclude button again. An example for needing to exclude elements is if you know you are not going to be migrating any web only design elements. Then you don’t want them part of the design complexity analysis so you would filter out all the web-only design elements. Use the Quick Filter as a quick way to Exclude multiple elements. You will need to rerun the Recompute database details for the design analysis to be updated for the database.

You can also select a Notes Form that you want migrated to an InfoPath or Nintex form template. Select the Form you want migrated and click the Export to InfoPath Template button, or right-click and from the context menu select the menu item Export to InfoPath form template.

For detailed information on this process, see Generate InfoPath form template .

Measure deviations from template or similar database

This is where you can measure deviations in design between the current database and another database (typically a design template or another database that you suspect is based on a common design). Identifying similar databases can be very useful when planning your migration process. To select a template or similar database to compare to, check the box and click the Select button. The Default button will automatically find the template database based on the template name, if there is one. You can assign the reference database automatically during the Auto Triage process by setting up a Class Rule and using the fields on the Auto Triage tab.

If both databases have had a Design Scan done than you get a comparison of the two databases immediately. Or, if you press the Scan Design button, both databases will be scanned immediately.

Design Element Delta: Difference in design between the current database and the reference.
Percent Match: Percentage the database matches the reference
Difference Details: To see the detailed differences, click this button.

Class Template Matching

The Class Template Match Details dialog shows all the partial matches as well as the best fit match. To associate the technical class of one of the matches to the current database, highlight the class name and click Set as Technical Class for Database.

Best Fit: The technical class template that best matches the database in regards to design.
NOTE: For a technical class template to be considered in the Best Fit analysis, it’s property, Include in “Best Fit” testing for all databases, must be checked in the Class Template Tab of the Technical Class Properties sheet. For a quick way to include all the Notes databases and templates that you want as technical class templates for Best Fit analysis, use the Create Technical Class database action.
Percent Match: Percentage the database’s design matches the best fit class template’s design.
Details: To see the class template match details, click this button.

Complexity tab

Once a design scan and/or data scan is completed, a summary of data patterns in use are displayed in this tab. The global complexity settings from the Global Option’s Analysis tab are used in the complexity computations in this tab.

This tab contains the following:

Microsoft Design Element Index (DEI)

If the Microsoft Design Element Index is defined as a factor to use in the automatic complexity assignment as defined in the Analysis tab of the Global Options, then this section will be filled out using the published DEI algorithm.

Average: Average number of the Index
Max: Maximum number of the Index
Calculations: This button will open a dialog box that shows the detail calculations of the Index

Data Complexity

This information is populated when the Scan Data is run.

Computation: Overall data complexity recommendation of the database using the algorithms defined in the Analysis tab of the Global Options.
Details: To view the data details click this button. This will take you to the Data Analysis tab which shows a summary of similar data record counts summarized by Form Used.
Data Scan: This button runs the data scan against the database to populate the Data Complexity. This process can also be run from the database actions list in the database context menu. For more information, see Scan Design Elements.

Design Complexity

This information is populated when the Scan Design is run.

Computation: Overall design complexity recommendation of the database using the algorithms defined in the Analysis tab of the Global Options.
Details: To view the design details click this button. This will take you to the Design Analysis tab which shows a list of all interesting design elements in the database with basic information about each.
Design Scan: This button runs the design scan against the database to populate the Design Complexity. This process can also be run from the database actions list in the database context menu. For more information, see Scan Design Elements.

Overall Complexity

The database complexity rating based on a scale of 1 to 5, 5 being the most complex. There are three ways this number may be set:

This number will be automatically computed and filled in when the Design and Data Scans are run. A weighted average of the algorithms will be used, depending on the preferences you set in Advanced configuration options. You should always treat automatic calculation as an approximate indicator of complexity and perform a detailed analysis of databases before performing the actual migration.

Migration Effort tab

Databases that qualify to be members of the given class can have their migration effort automatically set using the information defined in this tab. To do this, you must run the Apply class rules action for the databases once this tab is filled out.

Include estimates already credited to template or similar database

If checked, the numbers entered below should not reflect the analysis, development and testing effort that is expected for the original database template (the reference database on the Design Analysis tab). The effort estimates for the reference database will be displayed alongside the incremental effort required for this databases instance. If the database does not have a reference database defined for it, click the Set database link to define one.

Analysis work

Enter a number that represents the analysis work effort.

Development of new targets

Enter a number that represents the development of new targets effort.

Development of new migration jobs

Enter a number that represents the development and content migration effort.

Provisioning and content migration

Enter a number that represents the provisioning and content migration effort.

Testing and verification

Enter a number that represents the testing and verification effort.

Totals

Estimate total.

Locked

Select this check box to keep the manual numbers from being over-ridden every time a scan is run.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation