Chat now with support
Chat with Support

Metalogix Content Matrix 8.9 - 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 Configuring Content Matrix for Distributed Migration Frequently Asked Questions About Us

Enabling Debugging Mode

This section covers how to enable and use the debugging features of Metalogix Content Matrix Console. For more information on tests to perform, please contact Quest Support.

NOTE: This action only applies to Confluence, WordPress, Telligent and Other Blogs (XML-RPC) connections.

Enabling the Debug Feature

The steps for enabling the Debug feature will vary depending on the version of Metalogix Content Matrix being used.

Enabling the Debug Feature in v.5.0.1.01 and Later

1.On the system that the Metalogix Content Matrix Console is installed on, navigate to the AppData folder. An example of this location is:
<Drive>:\Users\<USER>\AppData\Roaming\Metalogix\Metalogix Content Matrix Console - Blogs and Wikis Edition.

2.Once in this folder location, select the EnvironmentSettings.xml file, and open it for editing (right-click and choose Edit).

3.In the EnvironmentSettings.xml file, set the EnableDebug value to "True".

Note: In some cases the EnableDebug entry may not be visible within the EnvironmentSettings.xml file. In this case, users can copy and paste another entry in the file, starting with <XmlableEntry> and ending with </XmlableEntry>. In the copied entry, replace the key entry with "EnableDebug" and set the value to "True."

Below is an example of a completed entry:

<XmlableEntry>
<Key Type="System.String, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">EnableDebug</Key>
<Value Type="System.String, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">True</Value>
</XmlableEntry>
 

4.After the value has been set, save and close the EnvironmentSettings.xml file.

5.Restart the console. The Debug option should now appear in the context (right-click) menu for any selected source content.

Enabling the Debug Feature in Versions Earlier than 5.0.1.01

1.Create a desktop shortcut to the console. Do this by navigating to the application directory (e.g. C:\Program Files\Metalogix Software Corp\Metalogix Content Matrix Console - Blogs and Wikis Edition), right-clicking on the Application file, and select Send to > Desktop (create shortcut).
 
SendToDesktopShortcut

2.Right-click on the new desktop shortcut and select Properties.

3.Select the Target field and append -debug to the end as seen below (including the space between):
 
ShortcutPropertiesTargetField

4.Click OK to close the Properties window.

After debug mode is enabled anytime the desktop shortcut is used the debug mode will open. To return the eRoom Edition to normal, users can either create a new shortcut, or remove the -debug from the target line in the shortcut properties.

Debugging a Connection

1.Launch the Metalogix Content Matrix Console using the modified shortcut (see above) and navigate to the source connection node that is experiencing issues using the Explorer View. Then right-click and select the Debug option.
 
Debug_BW
 

Note: If you do not see the Run Diagnostics option, you may not have enabled the debug setup option correctly. Please see the Enabling the Debug Feature section above.

 

Support for MediaWiki 'Category' Root Page

Question

Does Metalogix Content Matrix Console - Blogs and Wikis Edition support migrating MediaWiki "Category" pages?

Answer

Yes, migrating "Category" pages for a MediaWiki connection is supported.

Pages in MediaWiki can have "Category" values applied to them. Each category that is created has it's own a root page that users can access to modify and add additional content into. These pages are visible in Metalogix Content Matrix Console - Blogs and Wikis Edition's Items View and will also be visible in the Explorer View if the Show Pages option is selected. These category root pages have two sections. The top section of the page is for user defined content, and the bottom portion of the page is a MediaWiki generated section that list all of the other pages that belong to that "Category".

When Metalogix Content Matrix migrates these category root pages as a site migration, the top section of the page (the user defined content) is added to the page body. At the same time the bottom section of the page (the MediaWiki generated list of links to other pages in the category) is appended to the target page content as a list of links. These links are only updated at the time of migration and will not be updated when any subsequent changes are made in the target environment.

 

Using Proxies, Load Balancing or Alternate Access Mappings

Question

How does Metalogix Content Matrix deal with environments that use proxies, load balancing and/or alternate access mappings (AAM)?

Answer

Metalogix Content Matrix Console should not run into any issues with these three things. Metalogix Content Matrix uses a Metalogix Extensions Web Service that deploys over a whole farm, and functions identically to a regular SharePoint web service. SharePoint web service's get the benefits of IIS redirection, proxy pushing, and anything else that SharePoint can utilize, such as Alternate Access Mappings (AAM). Since the Metalogix Extensions Web Service acts the same as a SharePoint web service it also gets all of these benefits.

Basically, if you can access the regular native web services with all of your network configurations active, then you should also be able to reach the Metalogix Extensions Web Service, and migrate your content.

In the case for load balanced environments the Metalogix Extensions Web Service would need to be deployed through the target side SharePoint farm. When the Web Service is installed it automatically gets deployed to all the SharePoint instances within that farm, as a SharePoint solution. Once the Web Service is installed on the target server, then load balancing should no longer be an issue.

There are, however, some cases where proxy settings may not work correctly by default. In these cases it is possible to set some specific proxy settings for the specified connection. Please see the Configuring Proxy Settings page for more details, or the Manually Configuring Proxy Settings page if the proxy settings need to be manually configured.

Troubleshooting the Extensions Web Service

Question

I am having trouble installing the Metalogix Extensions Web Service. Are there any steps I can take to troubleshoot?

Answer

Yes, there are some steps you can take to troubleshoot installation issues for the Metalogix Extensions Web Service.

The first thing that you want to check is that the account that is being used to install the Metalogix Extensions Web Service has all the necessary permissions. This user account needs to be able to run the STSADM commands on the installing system, and also needs the following permissions:

·SharePoint Site Collection Administrator

·Farm Administrator

·Read/Write access to the Content Database (DB)

·Administrator on the installing system

In some cases users can receive a message saying "Could not deploy SharePoint solution: Cannot open SPAdminV4 service on computer." when they try to install the Metalogix Extensions Web Service. There are two possible methods for working around this issue.

1.Navigate to the folder containing the Metalogix Extensions Web Service installation EXE file. Right-click on this file and choose Run as Administrator. The Web Service should now be able to install. Some instances of Windows will automatically block services from being registered fully. In these cases, running as administrator should get around this issue.

2.In some cases, users are not able to use the Run as Administrator command, or this does not solve the issue, then there is a second workaround method that can be used. The alternate solution is to turn off the User Access Control (UAC) and reboot the server. This should allow the installing account to correctly install and deploy the Metalogix Extensions Web Service. Once installed and deployed you can re-enable UAC.

After the Web Service has been installed, there is a check that can be made to see if the Web Service can be detected on any given machine. For more information on running this check please see the After Installing the Metalogix Extensions Web Service section of the Installing the Metalogix Extensions Web Service page.

Related Documents