Chat now with support
Chat with Support

Metalogix Content Matrix 8.8 - Blogs and Wikis Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Source Blog and Wiki Structure Connecting to a Source Blog or Wiki Connecting to SharePoint Preparing for Your Migration Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Running Link Correction as a Post-Migration Task Log Files Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix
Registering Metalogix Command DLL Files Adding PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.Blog.Commands
Modifying Content Matrix Configuration and Settings Frequently Asked Questions About Us

Extract-LinksFromList

·IncludeSubWebs - Correct links in subwebs of target web.

·IgnoreQueryStrings - Ignore query strings in source URL (eg. '?pageId=2' in http://localhost/wiki/index.php?pageId=2).

·LogOptions - Specify logging options.

·EmailServer - An email server to use for sending job completion emails.

·EmailUserName - A user name to use when connecting to the specified email server. If not set, default credentials will be used.

·EmailPassword - A password to use for the specified user when connecting to the specified email server. If no user name is set, default credentials will be used.

·ToEmailAddress - A semicolon delimited list of email addresses to which the job completion email will be sent.

·FromEmailAddress - The email address of the mailbox from which the job completion emails will be sent.

·CCEmailAddress - A semicolon delimited list of email addresses to CC on the job completion email.

·BCCEmailAddress - A semicolon delimited list of email addresses to BCC on the job completion email.

·EmailSuccessTemplateFilePath - The absolute file path of the html template to use for the job completion email when the job is successful.

·EmailFailureTemplateFilePath - The absolute file path of the html template to use for the job completion email when the job fails.  

·EmailSubject - A custom subject for the job completion email.

·Transformers - The collection of data transformers which the action needs to run. Note that if the passed-in value for this parameter does not include transformers which are considered mandatory, they will be added automatically.

·Quiet - If set, the operation will not report progress to the PowerShell console.

·JobFile - The name of a job file to use for logging. If the file does not exist it will be created.

·Source - The source node for the actions.

·Target - The target node for the actions.

·JobDatabase - The connection string of a jobs database to use for logging. If the connection string is invalid, an exception is thrown. If both 'JobFile' and 'JobDatabase' parameters are specified, then the 'JobDatabase' parameter will take precedence and the job will only be written to the job database.

Modifying Content Matrix Configuration and Settings

You can configure and customize a number of Metalogix Content Matrix settings, including:

·distributed migration configuration

·proxy settings

·available actions and events

·client-side Managed Metadata batch size and metabase settings

·resource utilization settings

·default settings in configuration variable files

Configuring Content Matrix for Distributed Migration

Metalogix Content Matrix can significantly improve the time it takes to complete migration jobs by using a distributed migration model. This model essentially consists of a Metalogix Content Matrix Console Controller (Host), a central jobs repository or queue, and one or more loosely-coupled Metalogix Content Matrix Console agents.

Distributed Migration Illustration

By automatically selecting the jobs from a central repository, Metalogix Content Matrix Console agents are able to distribute the workload efficiently across the resource pool. The distributed model enables parallel processing of migration jobs that reduces migration time, and enables higher utilization, better workload throughput and higher end-user productivity from deployed resources.

Connection icon

Distributed Migration supports the following SharePoint connection adapters:

·Metalogix Extensions Web Service (MEWS)

·SharePoint Client Side Object Model (CSOM)

·CSOM using the Azure Pipeline

Distributed Migration Components

Distributed Migration is typically used for large migration projects and relies on the following three  components:

Controller (or Host)

This is the primary Metalogix Content Matrix Console that manages agents, the Distributed database and the migration jobs.

Distributed Database

A SQL Server database that contains the repository or queue of migration job definitions which the agents can execute.

NOTE:  The Distributed database cannot be a SQL CE database.

Agents

This is a physical or virtual machine that is remote from the Controller machine. It is connected to through the Controller to run jobs remotely. Once connected, the Controller will push an installation of the Metalogix Content Matrix Console onto the Agent machine, which is then configured to execute the migration jobs that are sent from the Controller. Any logging information would then be sent to the Distributed Database. When an agent is executing a migration job, any interaction with the agent such as changing a configuration setting is not recommended.

Related Documents