6.1 - Discovery and Analysis

Follow

The execution tabs' options are slightly different depending on your choice of source system, please select from your source, below.

 

Meridio Source

6.1.1 - Discover Items 6.1.2 - Pre-migration Checks
6.1.3 - Processing 6.1.4 - Synchronization
6.1.5 - Reset Items 6.1.6 - Erase
6.1.7 - History  

 

6.1.1 - Discover Items

Select a migration task from the ‘Migration Tasks’ panel on the left. Click the “Discover” button in the ‘Discovery’ area.


If the task is being discovered for the first time, then user can click on "New Discovery".


FIGURE_65_-__START_DISCOVERY_FOR_SOURCE___ITEMS.png

 

Migration Accelerator will start discovering items from the source system and record their status in the staging database repository.


FIGURE_66_-__DISCOVERY_RUN_OF__SOURCE__ITEMS.png

 

Note: Any modification done to source items after discovery is done will not reflect in Migration Accelerator unless the Discovery is run again. Once a Discovery has been run, the subsequent Discovery runs will add new items and identify the deleted/renamed items. Subsequent Processing will then apply the changes.

 

6.1.2 - Pre-migration Checks

Pre-migration Check feature ensure and confirms erroneous items before actual migration.


FIGURE_67_-__PRE-MIGRATION__CHECKS.png

This feature performs the following checks against SharePoint Site Collection configuration based on the rule:

  1. Has Blocked Characters Rule – Checks for illegal characters in source file/folder name. For Example: "#%*:<?>/\|
  2. Has Blocked Extensions – Checks whether the file type is blocked by SharePoint configuration. Extensions such as .asp, .hta, .lnk etc will result in an error.
  3. Has Blocked Size – Checks whether the file size exceeds the maximum file size for Office365/SharePoint such as more than 2000 MB
  4. Has Blocked Item Length – Checks whether the length of item name exceeds the SharePoint limits. For Example, more than 250 Characters.
  5. Has Blocked Container Length - Checks whether the length of parent container exceeds the SharePoint limits. Container length is associated with folder (name) length only. For Example, more than 256 Characters.
  6. Has Blocked Item URL Length - URL length of the item with or more than 260 chars will be excluded from load and will result as an erroneous item.
  7. Has Blocked Container URL Length - Checks whether the length of container exceeds the SharePoint limits. Container length is associated with folder (name) length only. For Example, more than 256 Characters.
  8. Has too Many Child items – Checks whether the folder contains more items than what is permitted within SharePoint Document Library folders such as more than 5000 items.
  9. Blank Item Name - Checks whether the Item Name is blank.
  10. Duplicate Item Name - Checks whether the Item Name is duplicate.
  11. Item Name Mismatch - Checks whether the Item Name is duplicate.
  12. Content in Multiple Folder- Checks whether the Item Name is duplicate.
  13. Zero Item Size - Checks whether the Item Name is duplicate.

 

FIGURE_68_-__PRE-MIGRATION__CHECK.png

6.1.3 - Processing

After successful discovery of all items present in the source system, click the "Process" button in the ‘Processing area’ in order start migration of content. It will launch below processing parameters popup window to select different processing parameters.

FIGURE_69_-__CONFIGURE_PROCESSING__PARAMETERS.png

This popup screen will allow select below processing parameters before starting migration of content:

  1. Process to stage – The migration goes through below processing stages, so one has to select appropriate target processing stage from below list:
    1. Capture Metadata – This stage captures metadata of all the items from source system.
    2. Classify – This stage performs content classification of all items based on content type mapping defined in migration task settings. This stage may retrieve content if required in order to perform content classification.
    3. Filter – This stage applies item filter rule in order to skip certain items in migration.
    4. Extract – This stage performs an extract operation on source metadata if any.
    5. Transform – This stage mainly transforms source metadata to target metadata by executing different metadata mapping rules. This stage may retrieve content if required in order to perform transformation.
    6. Load – This stage retrieves content if not obtained in earlier stages and performs upload of content and metadata on target system.

  2. Type of items to process
    This option allows to select type of items to process. E.g. Whether to process Error items, which may have failed in earlier processing attempts.

  3. Throttling parameters
    This section allows to select below throttling parameters to be referred during processing.
    1. Maximum number of items to process – Allows to select maximum number of items to process in current processing
    2. Maximum number of threads – Allows to select maximum number of threads to be created to perform parallel processing in order to achieve necessary through-put.

Once all processing parameters are selected, click on “OK” button to start the migration or click “Cancel” button to cancel the processing.

Clicking on “OK” button, the Migration Accelerator will start processing each items based on the mapping rules defined. It will display the progress of migration in below screen.

 

FIGURE_70_-__PROCESSING_COUNT_OF__SOURCE__ITEMS.png

6.1.4 - Synchronization      

Proventeq Migration Accelerator supports one-way Synchronization from Meridio to Office365 /SharePoint.

If source contents are changed after particular task discovered and/or processed, then user needs to re-discover the same task to sync the updated items on the source system.

 

6.1.5 - Reset Items

The ‘Reset’ functionality is available to remove items loaded on to the target system by Proventeq Migration Accelerator.

From the ‘Processing’ area in the ‘Execution’ tab, click the ‘Reset’ button. This will pop up a “Configure Processing parameters” screen where user can select the number of items to reset and the number of threads to execute this action. Click the “Ok” button to initiate the Reset action.

 

FIGURE_71_-__RESET_OF__ITEMS.png

 

On completion of this process all relevant items will be deleted from the target system

Reset Items – Progress dialog

 
FIGURE_72_-__REST_TARGET__ITEMS.png

 

Warning: This action will delete all relevant content loaded by Migration Accelerator as part of that migration task. User can however re-run the load. This action will not delete any items that were not originally loaded by Proventeq Migration Accelerator.

 

6.1.6 - Erase

Clicking on “Erase” button deletes all the discovered items related to the selected Migration Task from database. Any data loaded to target will remain as it is. “Erase” will not delete items from target system. User may either require to “Reset” loaded items from target before clicking on “Erase” button or delete items from target manually, if “Erase” has already been done.

Start erase of selected task

FIGURE_73_-__START_ERASE_OF__SELECTED__TASK.png

Erase items

FIGURE_74_-__ERASE_ITEMS.png

 

 

6.1.7 - History

A ‘History’ button is available on each area for Discovery and Processing. Clicking on this button brings up a screen that list all the actions that were performed on that migration task along with date the action was performed and the outcome of that particular action.

 

 

Fileshare Source

6.1.1 - Discover Items 6.1.2 - Pre-migration Checks
6.1.3 - Standard Processing 6.1.4 - Advanced Processing
6.1.5 - Syncronization 6.1.6 - Reset Items
6.1.7 - Advanced Reset 6.1.8 - Erase
6.1.9 - History  

 

6.1.1 - Discover Items

Select a migration task from the ‘Migration Tasks’ panel on the left. Click the “Discover” button in the ‘Discovery’ area.


If the task is being discovered for the first time, then user can click on "New Discovery".


FIGURE_62_-_START_DISCOVERY_FOR_SOURCE_ITEMS.png

 

If the task is being discovered for the first time, then user can click on "New Discovery".

Migration Accelerator will start discovering items from the source system and record their status in the staging database repository.


FIGURE_63_-_DISCOVERY_FOR_SOURCE_ITEMS.png

 

Note: Any modification done to source items after discovery is done will not reflect in Migration Accelerator unless the Discovery is run again. Once a Discovery has been run, the subsequent Discovery runs will add new items and identify the deleted/renamed items. Subsequent Processing will then apply the changes.

 

6.1.2 - Pre-migration Checks

Pre-migration Check feature ensure and confirms erroneous items before actual migration.


FIGURE_64_-_PRE-MIGRATION_CHECKS.png

This feature performs the following checks against SharePoint Site Collection configuration based on the rule:

  1. Has Blocked Characters Rule – Checks for illegal characters in source file/folder name. For Example: "#%*:<?>/\|
  2. Has Blocked Extensions – Checks whether the file type is blocked by SharePoint configuration. Extensions such as .asp, .hta, .lnk etc will result in an error.
  3. Has Blocked Size – Checks whether the file size exceeds the maximum file size for Office365/SharePoint such as more than 2000 MB
  4. Has Blocked Item Length – Checks whether the length of item name exceeds the SharePoint limits. For Example, more than 250 Characters.
  5. Has Blocked Container Length - Checks whether the length of parent container exceeds the SharePoint limits. Container length is associated with folder (name) length only. For Example, more than 256 Characters.
  6. Has Blocked Item URL Length - URL length of the item with or more than 260 chars will be excluded from load and will result as an erroneous item.
  7. Has Blocked Container URL Length - Checks whether the length of container exceeds the SharePoint limits. Container length is associated with folder (name) length only. For Example, more than 256 Characters.
  8. Has too Many Child items – Checks whether the folder contains more items than what is permitted within SharePoint Document Library folders such as more than 5000 items.
  9. Blank Item Name - Checks whether the Item Name is blank.
  10. Duplicate Item Name - Checks whether the Item Name is duplicate.
  11. Item Name Mismatch - Checks whether the Item Name is duplicate.
  12. Content in Multiple Folder- Checks whether the Item Name is duplicate.
  13. Zero Item Size - Checks whether the Item Name is duplicate.

 FIGURE_65_-_PRE-MIGRATION_CHECKS_REPORT.png

 

6.1.3 - Standard Processing

After successful discovery of all items present in the source system, click the "Process" button in the ‘Processing area’ in order start migration of content.

The Migration Accelerator will start processing each items based on the mapping rules defined.

FIGURE_66_-_PROCESSING_ITEMS.png

6.1.4 - Advanced Processing  

After successful discovery of all items present in the source system, click the "Process" button in the ‘Processing area’. Select specific container from Container Selection for processing.

 

FIGURE_67_-_ADVANCED_PROCESSING.png

 
After clicking on “OK” button, The Migration Accelerator will start processing the items within the selected container and recursively for any child containers, based on the mapping rules defined for selected container.

 

6.1.5 - Synchronization

Proventeq Migration Accelerator supports one-way Synchronization from File Share to Office365 /SharePoint 2013/2016.

If source contents are changed after particular task discovered and/or processed, then user needs to re-discover the same task to sync the updated items on the source system.

 

6.1.6 - Reset Items

The ‘Reset’ functionality is available to remove items loaded on to the target system by Proventeq Migration Accelerator.

From the ‘Processing’ area in the ‘Execution’ tab, click the ‘Reset’ button. This will pop up a “Configure Processing parameters” screen where user can select the number of items to reset and the number of threads to execute this action. Click the “Ok” button to initiate the Reset action.

 

FIGURE_71_-__RESET_OF__ITEMS.png

 

On completion of this process all relevant items will be deleted from the target system

Reset Items – Progress dialog

 
FIGURE_72_-__REST_TARGET__ITEMS.png

 

Warning: This action will delete all relevant content loaded by Migration Accelerator as part of that migration task. User can however re-run the load. This action will not delete any items that were not originally loaded by Proventeq Migration Accelerator.

 

6.1.7 - Advanced Reset

The ‘Reset’ functionality is available to remove items loaded on to the target system by Proventeq Migration Accelerator.

From the ‘Processing’ area click the ‘Reset’ button. This will pop up a “Configure Processing Defaults” screen where user can select specific container or number of Items to reset items from that container.

Advanced Reset - Configuration

FIGURE_70_-_ADVANCED_RESET_-_CONFIGURATION.png

 

Advanced reset target items container selection

FIGURE_71_-_ADVANCED_RESET_TARGET_ITEMS_CONTAINER_SELECTION.png

After clicking on “OK” button, reset process will remove all the items from target system.

FIGURE_72_-_ADVANCED_RESET-_TARGET_ITEMS.png

 

6.1.8 - Erase

Clicking on “Erase” button deletes all the discovered items related to the selected Migration Task from database. Any data loaded to target will remain as it is. “Erase” will not delete items from target system. User may either require to “Reset” loaded items from target before clicking on “Erase” button or delete items from target manually, if “Erase” has already been done.

Erase of target items

FIGURE_73_-_ERASE_OF_TARGET_ITEMS.png

Erase items

FIGURE_74_-__ERASE_ITEMS.png

 

 

6.1.9 - History

A ‘History’ button is available on each area for Discovery and Processing. Clicking on this button brings up a screen that list all the actions that were performed on that migration task along with date the action was performed and the outcome of that particular action.

Oracle UCM Source

6.1.1 - Discover Items 6.1.2 - Pre-migration Checks
6.1.3 - Standard Processing 6.1.4 - Advanced Processing
6.1.5 - Syncronization 6.1.6 - Reset Items
6.1.7 - Advanced Reset 6.1.8 - Erase
6.1.9 - History  

 

6.1.1 - Discover Items

Select a migration task from the ‘Migration Tasks’ panel on the left. Click the “Discover” button in the ‘Discovery’ area.


FIGURE_62_-_START_DISCOVERY_FOR_SOURCE_ITEMS.png

 

If the task is being discovered for the first time, please click on "New Discovery".

Migration Accelerator will start discovering items from the source system and record their status in the staging database repository.


FIGURE_63_-_DISCOVERY_FOR_SOURCE_ITEMS.png

 

Note: Any modification done to source items after discovery is done will not reflect in Migration Accelerator unless the Discovery is run again. Once a Discovery has been run, the subsequent Discovery runs will add new items and identify the deleted/renamed items. Subsequent Processing will then apply the changes.

 

6.1.2 - Pre-migration Checks

Pre-migration Check feature ensure and confirms erroneous items before actual migration. User can click on Run button to start the pre-migration check for selected task.

 

FIGURE_46_-__PRE-MIGRATION__CHECKS.png


FIGURE_64_-_PRE-MIGRATION_CHECKS.png

This feature performs the following checks against SharePoint Site Collection configuration based on the rule:

  1. Has Blocked Characters Rule – Checks for illegal characters in source file/folder name. For Example: "#%*:<?>/\|
  2. Has Blocked Extensions – Checks whether the file type is blocked by SharePoint configuration. Extensions such as .asp, .hta, .lnk etc will result in an error.
  3. Has Blocked Size – Checks whether the file size exceeds the maximum file size for Office365/SharePoint such as more than 2000 MB
  4. Has Blocked Item Length – Checks whether the length of item name exceeds the SharePoint limits. For Example, more than 250 Characters.
  5. Has Blocked Container Length - Checks whether the length of parent container exceeds the SharePoint limits. Container length is associated with folder (name) length only. For Example, more than 256 Characters.
  6. Has Blocked Item URL Length - URL length of the item with or more than 260 chars will be excluded from load and will result as an erroneous item.
  7. Has Blocked Container URL Length - Checks whether the length of container exceeds the SharePoint limits. Container length is associated with folder (name) length only. For Example, more than 256 Characters.
  8. Has too Many Child items – Checks whether the folder contains more items than what is permitted within SharePoint Document Library folders such as more than 5000 items.
  9. Blank Item Name - Checks whether the Item Name is blank.
  10. Duplicate Item Name - Checks whether the Item Name is duplicate.
  11. Item Name Mismatch - Checks whether the Item Name is duplicate.
  12. Content in Multiple Folder- Checks whether the Item Name is duplicate.
  13. Zero Item Size - Checks whether the Item Name is duplicate.

 

6.1.3 - Standard Processing

After successful discovery of all items present in the source system, click the "Process" button in the ‘Processing area’.

The Migration Accelerator will start processing each items based on the mapping rules defined.

FIGURE_66_-_PROCESSING_ITEMS.png

6.1.4 - Advanced Processing  

After successful discovery of all items present in the source system, click the "Process" button in the ‘Processing area’. Select specific container from Container Selection for processing.

 

FIGURE_48_-__ADVANCED__PROCESSING.png

 
After clicking on “OK” button, The Migration Accelerator will start processing the items within the selected container and recursively for any child containers, based on the mapping rules defined for the selected container.

 

6.1.5 - Synchronization

Proventeq Migration Accelerator supports one-way Synchronization from Oracle UCM to SharePoint 2013/2016/ SharePoint Online.

If source contents are changed after particular task discovered and/or processed, then user needs to re-discover the same task to sync the updated items on the source system.

 

6.1.6 - Reset Items

The ‘Reset’ functionality is available to remove items loaded on to the target system by Proventeq Migration Accelerator.

From the ‘Processing’ area in the ‘Execution’ tab, click the ‘Reset’ button. This will pop up a “Configure Processing parameters” screen where user can select the number of items to reset and the number of threads to execute this action. Click the “Ok” button to initiate the Reset action.

 

FIGURE_71_-__RESET_OF__ITEMS.png

 

On completion of this process all relevant items will be deleted from the target system

Reset Items – Progress dialog.

 
FIGURE_72_-__REST_TARGET__ITEMS.png

 

Warning: This action will delete all relevant content loaded by Migration Accelerator as part of that migration task. User can however re-run the load. This action will not delete any items that were not originally loaded by Proventeq Migration Accelerator.

 

6.1.7 - Advanced Reset

The ‘Reset’ functionality is available to remove items loaded on to the target system by Proventeq Migration Accelerator.

From the ‘Processing’ area click the ‘Reset’ button. This will pop up a “Configure Processing Defaults” screen where user can select specific container or number of Items to reset items from that container.

 

FIGURE_51_-__ADVANCE_RESET_TARGET__ITEMS.png

 

 

After clicking on “OK” button, reset process will remove all the items from target system.

FIGURE_72_-_ADVANCED_RESET-_TARGET_ITEMS.png

 

6.1.8 - Erase

Clicking on “Erase” button deletes all the discovered items related to the selected Migration Task from database. Any data loaded to target will remain as it is. “Erase” will not delete items from target system. User may either require to “Reset” loaded items from target before clicking on “Erase” button or delete items from target manually, if “Erase” has already been done.

Erase of target items

FIGURE_53_-__START_ERASE_OF__SELECTED__TASK.png

 

Erase items

FIGURE_74_-__ERASE_ITEMS.png

 

 

6.1.9 - History

A ‘History’ button is available on each area for Discovery and Processing. Clicking on this button brings up a screen that list all the actions that were performed on that migration task along with date the action was performed and the outcome of that particular action.

 

 

Was this article helpful?
0 out of 0 found this helpful

Comments