Converse agora com nosso suporte
Chat com o suporte

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

Command line options

Command line options

The Migrator for Notes to SharePoint command line interface can be very useful for scripting jobs from other programs or from scheduling tools such as Windows Scheduler or Domino agents.

NMSPCMD.EXE is installed in our bin directory (typically C:\Program Files (x86)\Quest\Migrator for Notes to SharePoint\Bin).

Migrator for Notes to SharePoint supports the following command line options, which allow it to run in batch mode:

NMSPCMD.exe -job <jobfile> <options> [ –source <connectionstring> ] [ –target <listOrLibraryUrl> ] [ –import <infile> ] [ –export <outfile> ] [-filesfolder] [ –log <logfile> ] [ -defaultuser <username> ] [ -mode Complete | ProvisioningOnly | ProvisioningAndSecurityOnly | RecoverLTS ] [ -unid <unids> ] [-options <optionsname>]

The parts in [ square brackets ] are optional overrides to the job options or global defaults. These overrides allow you to run the same job multiple times specifying different sources and targets each time.

The source can be any connection string that you see on the Notes, QuickPlace, Quickr or Domino.Doc tabs. The target should be the full path to the list or library.

Options in detail:

-job <jobfile>: Specifies the jobfile for a data migration job.
-source <connectionstring>: Overrides the Notes Data Source specified in the Job Definition.
-targetsite <siteCollectionUrl>: Overrides the SharePoint Target Site in the Job Definition.
-targetweb <subsitePath>: Overrides the SharePoint Target Web in the Job Definition.
-targetlist <listName>: Overrides the SharePoint Target List in the Job Definition.
-target <listUrl>: Overrides the SharePoint Target Site and List in the Job Definition.
-export <outfile>: Perform a partial migration job writing intermediate results to the named XML data file.
-import <infile>: Perform a partial migration job using the named XML data file as a data input.
-defaultuser <username>: The “If lookup mapping fails” user mapping option is overridden to be “Substitute the default user”, using the username that is passed as the default user.
-filesfolder <>: When used, the attachments will be written to a separate "_Files" folder rather than the default intermediate data file. The abbreviated “-ff” can be used as well.
-formula <>: This argument allows whatever formula specified in the current job to be overridden.
-view <>: This argument allows whatever view specified in the current job to be overridden.
-form <formName>: This argument allows you to migrate documents associated to specified forms. If specifying multiple forms, separate form names by commas and put the whole string in double quotes.
-mode Complete | ProvisioningOnly | ProvisioningAndSecurityOnly | RecoverLTS: This argument allows you to run portions of a job.
•
Complete: Run complete job.
•
ProvisioningOnly: Run provisioning only.
•
ProvisioningAndSecurityOnly: Run provisioning and security mapping only.
•
RecoverLTS: Recover the Link Tracking data.

-unid <unids>: Overrides the option "Select records/pages based on UNID" in the Source Data Definition. Separate multiple UNIDs using semicolons.

-options <optionsname>: Applies a saved options file by the options name.

NMSPCMD.EXE returns one of the following exit codes:

0 = Completed
-1 = Completed With Warnings
-2 = Completed With Exceptions
-3 = Job Failed
-4 = Job Could Not Be Run

These error codes make it possible for scripts to detect the results and respond accordingly. Note that the resulting XML log file will usually contain a LogSummary section that provides further details.

Examples:

1
Run a job:
NMSPCMD.exe -job "C:\temp\MigrateContacts.pmjob"
2
Override the source and target this time:
NMSPCMD.exe -job "C:\temp\MigrateContacts.pmjob" -source "database=names.nsf; server=eagle/Proposion" -target http://host:8080/dev/Contacts
3
Export to an intermediate XML file:
NMSPCMD.exe -job "C:\temp\MigrateContacts.pmjob" -export "C:\temp\ContactData.xml"
4
Import from an intermediate XML file and, whenever the automatic user mapping fails, substitute a specific user.
NMSPCMD.exe -job "C:\temp\MigrateContacts.pmjob" -import "C:\temp\ContactData.xml" –du “ACME\JoeUser”
5
Override both the view and formula:
NMSPCMD.exe -job "C:\temp\DocLibrary to List.pmjob" -view "($All)" -formula "subject='Florida'"

Connecting the Console to alternate Repository database

The Migrator for Notes to SharePoint Console now supports the ability to read a repository database argument from the command-line. Using the -rd command line option, you can launch the Console and specify an alternate repository database for the Console to connect to.

To use this feature, open a command prompt and launch the console using the following command:

mmc C:\NotesSharePoint\Migrator\MigratorConsole\migratorconsole.msc -rd=YourTemporaryRepository.nsf

The console will start with the database you specified. As long as you don’t save your configuration, your former repository will be used the next time you start the console without the “–rd” parameter.

To indicate an alternate repository is loaded, the Root Node label in the navigation tree will have the repository name appended. For example, "Migrator for Notes to SharePoint (TempRepository.nsf)".

Notes source data definition file format

Migrator for Notes to SharePoint stores Source Data Definitions as simple XML files (with a default extension of .PMSRC). You can edit these files using XML editors and even plain text editors. In addition, you can easily distribute them to other users.

By default, Data Definitions live in the DataDefinitions sub directory of your Migrator for Notes to SharePoint program directory, but you can change this location if you want to. See Customizing global options for more details.

Here is an example of a Source Data Definition file:

<?xml version=”1.0” encoding=”utf-8”?>
<Source Definition xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Name="Document Library"
Description="Standard Notes Document Library" Templates="StdR6WebDocLib; StdR50WebDocLib" ListTypes="Document Library">
<QuerySpec xsi:type="NotesQuerySpec">
<From />
<Search />
<Formula />
<Column ColumnType="Item" Value="Categories" Alias="Category" ReturnType="String" Option="Multi" />
<Column ColumnType="Item" Value="Date" ReturnType="Date" />
<Column ColumnType="Item" Value="DocType" ReturnType="String" />
<Column ColumnType="Item" Value="ExpireDate" ReturnType="Date" />
<Column ColumnType="Item" Value="From" ReturnType="String" />
<Column ColumnType="Item" Value="MainID" ReturnType="String" />
<Column ColumnType="Item" Value="ReviewerList" ReturnType="String" Option="Multi" />
<Column ColumnType="Item" Value="ReviewerLog" ReturnType="String" />
<Column ColumnType="Item" Value="ReviewTime" ReturnType="Number" />
<Column ColumnType="Item" Value="ReviewType" ReturnType="String" />
<Column ColumnType="Item" Value="Status" Alias="StatusCode" ReturnType="Number" />
<Column ColumnType="Formula" Value="@If(Status=1;'Submitted';Status=2;'In Review';Status=3;'Approved';'')" Alias="Status" ReturnType="String" />
<Column ColumnType="Item" Value="Subject" ReturnType="String" />
<Column ColumnType="Item" Value="Body" Alias="BodyText" ReturnType="String" />
<Column ColumnType="RichText" Value="Body" Alias="BodyHtml" Option="Html" />
<Column ColumnType="RichText" Value="Body" Alias="BodyMime" Option="Mime" />
<Column ColumnType="Attachment" Value="Body" Alias="BodyAttachments" Option="Multi" />
<Column ColumnType="OleObject" Value="Body" Alias="BodyEmbeddedObjects" Option="Multi" />
<Column ColumnType="Image" Value="Body" Alias="BodyImages" Option="Multi" />
</QuerySpec>
</SourceDefinition>

QuickPlace/Quickr source data definition file format

Migrator for Notes to SharePoint QuickPlace/Quickr mode stores Source Data Definitions as simple XML files (with a default extension of .QPSRC). You can edit these files using XML editors and even plain text editors. In addition, you can easily distribute them to other users.

By default, Data Definitions live in the DataDefinitions sub directory of your Migrator for Notes to SharePoint program directory, but you can change this location if you want to. See Customizing global options for more details.

Here is an example of a Source Data Definition file:

<?xml version="1.0" encoding="utf-8"?>
<SourceDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Type="QuickPlace" Name="QP Pages" Description="Standard QP Pages" Templates="MeetingRoom" ListTypes="Custom List; Generic List">
<QuerySpec xsi:type="QuickplaceQuerySpec">
<IncludePages>true</IncludePages>
<IncludeFiles>true</IncludeFiles>
<IncludeLinks>true</IncludeLinks>
<Folder />
<Forms />
<ExcludeForms />
<Formula />
<Column ColumnType="Item" Value="c_ProjectName" Alias="ProjectName" ReturnType="String" />
<Column ColumnType="Formula" Value="@Uppercase(c_Serialnumber)" Alias="SerialNumber" ReturnType="String" />
</QuerySpec>
</SourceDefinition>
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação