1.From the Manage Queue dialog, select the job that you want to delete from the Distributed Migration Job list. The row selector icon and the highlighted row indicates the selected row.
NOTE: Only jobs with a status of Queued or Done can be deleted. Deleting a job from the queue will not remove or delete any of the logging information that has already been sent to the main Job list for the Agent Database.
2.Click Delete Job.
(If the button is disabled, check that the selected job has a status that is either Queued or Done.)
A dialog will display asking you to confirm the deletion.
NOTE: The refresh is applied to whichever job list Metalogix Content Matrix is currently connected to, whether that is the Agent Database (for the Distributed Migration feature) or via a standard connection.
To refresh the jobs list:
1.From the Manage Queue dialog, select a job in the Job List. The row selector icon and the highlighted row indicates the selected row.
2.From the Jobs List menu bar, choose File > Refresh.
If the status of the job has changed, the Status value will indicate the new status of the job.
As a post-migration task, Metalogix Content Matrix can correct Blog and Wiki Link objects when migrating them (pages, posts, and bookmarks) as items in SharePoint Links lists. Confluence Bookmarks migrate as items in a SharePoint Links list. If these links are pointing to an internal location they will be corrected to the new target location as part of a migration. Metalogix Content Matrix can also correct links in column data (for pages and posts) within document libraries and lists in SharePoint.
As part of a migration, Metalogix Content Matrix:
I.Creates a column called Migration Source URL within any of the lists or libraries that contain items that were migrated from the source. This generally only includes Posts and Wiki Pages lists, Pages libraries, Attachment document libraries, and Comments lists.
II.Extracts and maps source and target URLs to a "link dictionary" called LinksCache.sdf located in the folder \[DRIVE]:\Users\[USER]\AppData\Roaming\Metalogix\Metalogix Content Matrix Console - Blogs and Wikis Edition.
NOTE: While link extraction is performed automatically during the migration, it can also be performed as a post-migration task. This may be necessary, for example, if multiple users are performing migrations, to ensure that all source and target url mappings are captured in the LinksCache.sdf file before link correction is run. See Extracting Links for Link Correction for details.
Extracting links for link correction is done automatically as part of the migration. However, you may also choose to do it as a post-migration task.
If you choose not to extract links as a post-migration task, you can go directly to Running Link Correction.
When to Perform Link Extraction as a Post-Migration Task
As part of the link extraction process, link URLs are mapped between the source and target. This mapping is done as an automated process during migration. The source and target URLs are mapped and stored in a Link Dictionary file called LinksCache.sdf, which is used when the link correction action is run. This file is located at: [DRIVE]:\Users\[USER]\AppData\Roaming\Metalogix\Metalogix Content Matrix Console - Blogs and Wikis Edition.
In some cases, the automated process may not capture each source and target URL mapping. For example, if multiple users are running migrations, each user's copy of the LinksCache.sdf file will contain some of the URL mappings, and they will not be consolidated into one copy of the file. In this case, users can run the Extract Links action, which allows Metalogix Content Matrix to crawl the selected SharePoint target node to find any source URLs with values in the Migration Source URL column. If values are found, they will be written to the link dictionary, and mapped to the corresponding SharePoint URL.
If users want to remove all the existing mapping, they can close Metalogix Content Matrix - Blogs and Wikis Edition, navigate to this folder location and delete the LinksCache.sdf file, then restart Metalogix Content Matrix.
Users may also want to clear any existing link mappings without permanently losing them. In this case the current LinksCache.sdf file can be renamed and saved, and a new LinksCache.sdf file can be created. All of the existing mappings will still exist in the renamed file, and new mappings can be created in the new file. Should users want to switch back, they can rename the newer version of the file, and return the original file back to its original file name, LinksCache.sdf.
To extract links for link correction:
1.Select the SharePoint site collection, site, or list for which you want to extract links.
NOTE: While you can only run link correction at the site collection or site level, you can extract links at the list level as well.
2.Right-click and choose Link Correction > Extract Links.
An Extract Links Information dialog displays, explaining how the link extraction works.
Dismiss the information dialog to continue to the Extract Links Options dialog.
3.If you want to enable link extraction to search down through any sub-sites under the selected SharePoint site node, and run link extraction on their contents, make sure the Extract links from subwebs box is checked.
NOTE: This option is grayed out if link extraction is run on a SharePoint list or library.
4.If you want link extraction to ignore (and exclude) any query string URLs that it finds in the Migration Source URL column, check the Ignore query string in Source URL box.
5.If you want more detailed logging for some or all of the SharePoint objects on which the link correction will be run, switch to the Logging tab, check the Enable verbose logging box then check the appropriate options.
Now you can save or run the action.
When the action starts, a Job log will be created. The logs can be viewed (in progress or after the action is finished) by clicking [Details>>]. After the action has completed a note will be displayed in the bottom left corner of the dialog stating the number of completions, as well as any warnings or errors that may have been encountered (if there were any).