Migration Steps

Owned by Hannah Petty
Last updated: Aug 11, 2016Version comment
4 min read

In this section:

Pre-Migration Checklist

CompletedItemDescription
Prepare Users

During migration, users will be migrated to specific roles. Please ensure that the users you would like to migrate are assigned to a role in the ESS that will map to the desired active learning platform role. See the Overview above for role mappings.

Users in the Echo360 active learning platform

Please note that currently, in your active learning platform instance, once a User has been created they cannot be deleted, only made inactive.

Review available disk space for Intake Volume

The content migration processing will involve copying each Presentation’s existing media files to the Intake Volume upload directory for reprocessing. 

Increasing the available free disk space will allow more Presentations to be copied for media reprocessing by available EchoSystem Media Processors. 

Disk space recommendation

A migration job will only be able to run if the size of the media files for that job plus the current total disk used on the Intake Volume adds up to be less than 70% of total disk space on the Intake Volume. So if the Intake Volume has 30% or less disk space available then no migration jobs will start. This is in place to prevent migration jobs filling the Intake Volume disk and preventing new ESS captures from uploading to the Intake Volume for processing.


Add additional EchoSystem Media Processors to increase content migration and review Media Processor configurations.

Check Media Processor Configuration!

It is extremely important that this step is completed. Content Migration *will fail* if your Media Processor is not configured with enough disk space or the incorrect number of concurrent tasks.

Increasing the amount of EchoSystem Media Processors will increase the amount of concurrent content migration tasks, and decrease the time required for migration.

Please see Configure the Media Processor for information on configuring the number of Concurrent Jobs.

Each concurrent task that a Media Processor is configured for will require 60GB of free disk space on the volume it uses for media processing. Please see Manage the Media Processor and Manage Media Processor Defaults for additional details on adding and configuring processors.

For example

If a media processor is configured to process 6 recordings at a time then it must have 360GB of free storage space. If, however, it only has 180GB of free storage space then it would need to be configured to process 3 recordings at a time via the ESS Web UI. It is extremely important that media processors don't run out of disk space so their storage availability should be actively monitored.

Migration Steps

Step 1 – Log into your Echo360 active learning platform Institution instance as an Administrator

Your Institution will be provided an Echo360 active learning platform Institution instance and the administrator login details will be provided to your primary technical contact.

Please contact support@echo360.com to retrieve these access details.

 

Step 2 – Select the Configurations Menu Option

 

Step 3 – Select API Client Configurations to Create New Client

 

  1. Please fill in active learning platform API Client details of your choosing:
    1. Client label
  2. Please take note of the details as they will be required by the EchoSystem Server:
    1. Institution ID
    2. Client ID
    3. Client Secret
    4. Echo360 active learning platform URL (https://www.echo360.org) 

 

Please be aware that your Client Secret will be shown once and only once. You must make a note of this information.

 

Step 4 – Upgrade to EchoSystem 5.5

If you have not already done so, please follow the standard upgrade instructions to upgrade your EchoSystem Server to version 5.5.  Please see the upgrade instructions for more details on this procedure.  We also highly recommend that you review all of the Release Notes.

Step 5 – Navigate to Systems Tab > Hosted Services

 

  1. Make sure you click the "Add Echo360 active learning platform" button.

Do not navigate directly to the Migration tab

Please note that if you navigate directly to the Migration tab you will be presented with a warning message to first create an Echo360 active learning platform Provider record.

Step 6 – Add a new Echo360 active learning platform Provider Hosted Service entry

 

  1. Enter your Echo360 active learning platform API Client Configuration Details.
    1. Label
    2. Client Id
    3. Client Secret
    4. Echo360 URL (https://www.echo360.org)
    5. Institution ID 
  2. Ensure there are no leading or trailing whitespaces.
  3. Click the Save button.

 

Echo360 URL

Please be aware that when entering the Echo360 URL, you must include the protocol (https://).

 

Step 7 – Click on the Echo360 active learning platform Provider Hosted Service entry just created

Wait about 5 minutes and then click on the Test Server button to ensure the EchoSystem Server communication with your Echo360 active learning platform Institution instance is working correctly.

Potential Connection Delay

Please be aware that it may take approximately 5 minutes for the API values to properly update and allow communication between the ESS and Echo360. If you click on the Test Server button immediately after creating the Hosted Service Provider it may result in an error, even if the information has been entered and configured correctly.

Step 8 – Navigate to Migration Tab, and select the data objects to migrate to Echo360 active learning platform

 

  1. Select the EchoSystem Server data object type from the tab options presented.
  2. Check the individual records to migrate to Echo360 active learning platform.
  3. Select the Action Menu Option “Migrate”.
  4. Repeat for each EchoSystem Server data object type to migrate to Echo360 active learning platform.