Migrating Access Request Settings
|
Navigation: How Content Matrix Handles Various SharePoint Components > Users and Permissions Migration > Migrating Access Request Settings |
Access Request Settings is an option within a site's permissions that allows SharePoint to specify a specific user's (usually the site administrator's) email and/or contact information. This happens when another user is requesting authorization to access that site, and is done through a link on the site in question. When enabling this checkbox, you should take into account the following considerations:
·This setting is only supported when performing the following actions: Paste Site Collection, Paste Site as Subsite, and Paste Site Content > All Site Content. This option is not supported for any other migration actions.
·Allow access requests must be enabled in the Access Requests Settings options on the target.
·In order to manage email triggers, the following flags have been added to the product's ApplicationSettings.xml file: EnableAccessRequestItemsNotifications (set to 'False' by default) and NotificationEmailAddress (set to 'CM@CM.CM' by default). The following table describes what flag values to set to achieve the desired outcome:
|
Desired Outcome |
EnableAccessRequestItemsNotifications setting |
NotificationEmailAddress setting |
|---|---|---|
|
An email is to be sent to the user whose email is specified in the Access Request Settings options on the target. |
True |
Any valid or invalid email address. |
|
An email is to be sent to a different email address than the one specified in the Access Request Settings options on the target. |
False |
The email address of the intended recipient. |
|
No notification emails are to be sent. |
False |
Any invalid email address (CM@CM.CM by default). |
BCS/BDC Data Migration
|
Navigation: How Content Matrix Handles Various SharePoint Components > BCS/BDC Data Migration |
Content Matrix can migrate content that is using Business Data Catalog (BDC) data or Business Connectivity Services (BCS) data. Both BDC and BCS data are connections to Line-Of-Business (LOB) content that is external to SharePoint. Content Matrix does not migrate this external data itself, but migrates the references to it that exist within SharePoint.
BDC data connections are used in SharePoint 2007 (only in MOSS, WSS 3.0 does not support BDC) and are generally read only connections. BCS data connections are used in SharePoint 2010 and later and are generally read/write connections. For a more basic description of what BDC and BCS are, please see the following MSDN articles:
Prerequisites for Migrating BCS and BDC Data
|
Navigation: How Content Matrix Handles Various SharePoint Components > BCS/BDC Data Migration > Prerequisites for Migrating BCS and BDC Data |
In order for BDC or BCS data to be properly migrated:
·the Definition for the external data must be created on the target before migration.
·The name of the external content type on the target must match the external content type from the source, and there should be only one external content type with this name on the target (in SharePoint 2010 and later there can be multiple external content types with the same name, but with a different name space).
·The appropriate account (depending on the connection type used), must have access to the external system:
§For the Local OM (Object Model) connection, the migrating user account
§For all other connection types, the application pool user account
·The Business Data Connectivity Service must be enabled and started on the target server before migration. This can only be done through a manual process, since the external data cannot be connected to or modified by Content Matrix.
This definition can be imported from SharePoint 2007, or it can be manually moved from SharePoint 2010 and later.
Types of BDC and BCS Data
|
Navigation: How Content Matrix Handles Various SharePoint Components > BCS/BDC Data Migration > Types of BDC and BCS Data |
There are three basic types of BDC and BCS data connections that exist in SharePoint, and all three can be migrated between on premises versions with Content Matrix, as described in the following table.
|
Data Type |
Description |
|---|---|
|
External Lists (SharePoint 2010 and later) |
In Content Matrix, BCS lists will appear as any other SharePoint list (listed under the SharePoint site), but will have a slightly different icon, as seen in the below image. Since this data is read from the external system, the available actions on its Explorer View node are limited. The Items View tab can be selected to view the items within the external list. The items in the External list will also have a slightly different icon, as well as a BDC Identity column to give the item ID within the external data. This ID is also an encoded reference in the external system. In the case of an external Database (DB) connection, this ID will contain a primary key value. NOTE: The Items View tab is not available for the DB connection. |
|
BDC/BCS Web Parts |
These are web parts within SharePoint that are connected to the external BDC or BCS data. Content Matrix will migrate these web parts the same as any other web parts, provided that the web part itself has been installed, and the definition has been created on the target before migration. Once the web part has been migrated it will be reconnected to the BDC or BCS data. EXCEPTION: Any web parts that have web part connections (which are connections between two web parts) will not have connections preserved in a migration. |
|
External Columns |
These are columns that have been added to lists and libraries in SharePoint. These columns contain BDC or BCS data that comes from the external connection (from the external content type), and this data has been associated with items in the lists. These columns will automatically be added to the target SharePoint list and libraries when they are migrated, so long as the definitions have been created on the target before migration |
