Migrating to Enterprise
Enterprise Test Environment
 

This document outlines the steps required to create a Maplewood Enterprise test environment to validate data and the Enterprise migration process before the move to a production environment.

Copy the legacy files

  1. Create a new share on the SQL Server for Maplewood Enterprise (i.e. MWEnterprise)
  2. Set up permissions to allow school and division users access to change the data
  3. Create a new folder under mwenterprise called programs and copy all the folders from the live programs folder
  4. Create a new folder under the share called Legacy. This is the folder that will have a temporary copy of the legacy data that will be used to migrate to Enterprise. Within the folder create a folder called Central and Schools.
  5. Create a script using robocopy (found in the Windows Server resource kit) to copy the live Central Office folder to the\\servername\mwenterprise\legacy\central folder
  6. Create a script using robocopy to copy the live schools folder to the \\servername\mwenterprise\legacy\schools folder. To speed up the copy, make sure to exclude large and unnecessary files (e.g.: *.MWB for backups).

Set the testing legacy paths and databases

  1. Run Destlo to change the Central Office structure file on \\servername\mwenterprise\legacy\central
  2. Create a shortcut to \wpr\CpUtil32.exe with the Start In being the testing legacy Central Office structure file location. Run this shortcut, select Create Schools File and specify the location of the schools folder (\\servername\mwenterprise\legacy\schools) and then click Create. Exit this program.
  3. Create a shortcut to \wpr\mwadm32.exe with the Start In being the testing legacy Central Office structure file location. Run this shortcut (you can rename the shortcut to Central Office) then go to File - Setup to verify that all the expected schools are there, and have the correct path defined. While you are in Central Office you should run Web Updates to make sure you have the latest programs.
  4. After the schools have been verified, go back into the shortcut to CoUtil32.exe and select the option to Update School Structure Files. Change the program path and data path by choosing those options and entering the appropriate information into the path fields.
  5. The legacy database is now set up; however, the test environment is still using the achievement databases (Classroom Manager) in the live environment. To ensure the achievement databases are not impacted when using the test environment we will need to create a copy of the databases or create a empty set. For testing we recommend creating new databases for the test environment. To create new achievement databases for the test environment create a shortcut to \wpr\MwEnIm32.exe and add -ClsMgrDB at the end of the target line. Please double-check with Maplewood to make sure you have the latest version of this program. The Start In path should be to the Central Office structure file. Once the program loads you will have the opportunity to specify the database prefix and server information. We recommend using Demo_Clsmgr_ as the prefix.
  6. Either use Destlo32.exe or create shortcuts to all or some of your testing legacy schools, and make sure that the structure files are all pointing at the testing paths and testing Classroom Manager databases.

Run the test migration

  1. Please note that at this point if any school is using Maplewood Library, additional steps are required. Please contact Maplewood.
  2. Once a copy of the live environment is set up under the legacy folder you are ready to run the Enterprise Migration. The Enterprise Migration uses the information in the Central Office structure file to determine where the school data is, and it also changes the way data is being written. To ensure the original structure file is not changed we need a copy of the structure file in a new folder that will be used specifically for the migration. Please create a folder under the \\servername\mwenterprise\legacy\central called pr.migrate and copy the Central Office structure file to that location.
  3. The final step is to actually run the migration. To do so, create a shortcut to \wpr\EnDaMi32.exe and change the Start In path to \\servername\mwenterprise\legacy\central\pr.migrate. Run the shortcut. During this process you will be asked for the name of the Enterprise database as well as a SQL Server account with sa permissions.
  4. After the database is created, select all schools, select all import options (checkboxes) and specify 50 as the number of years of past students to import (this is the maximum). Make sure to check the Board Setup and Include Board Files boxes.
  5. Before clicking Import, please make sure that you have allotted a significant amount of time for this process and that you are logged on to a server that will not time you out. Enterprise migrations usually take approximately 30-60 minutes per school. For larger school boards this could mean it will take several days for the migration to complete.

Create the testing Enterprise environment

These steps can be run while the migration is running.

  1. Create a new folder under the \\servername\mwenterprise called Enterprsie. Underneath that make folder Schools and Central.
  2. Copy the contents of the \\servername\mwenterprise\legacy\central to \\servername\mwenterprise\Enterprise\central
  3. Create a script using robocopy to copy ONLY the structure file, clsmgr folder, and IN folder of all schools from \\servername\mwenterprise\legacy\schools to \\servername\mwenterprise\Enterprise\schools.
  4. Repeat steps 7-12, this time setting the paths as \\servername\mwenterprise\Enterprise\... Only use destlo to double-check the school paths - do not try to log into the testing Enterprise schools at this time.
  5. Disable security in the testing Enterprise Central Office by logging in as supervisor and going to File, Change Security – Maplewood Security.

Change read/write mode to Enterprise

  1. Create a shortcut to \wpr\EnScSe32.exe (Enterprise School Setup) and change the start in path to \\servername\mwenterprise\Enterprise\central.
  2. Enterprise School Setup is used to change the read and write flags and setup each school to be in Enterprise. This step is only done after the migration is done. To set up the schools to run in Enterprise, change the Data Read and write to Enterprise and click Update. This will change the Central Office Structure file.
  3. Close the program, and open it again. This time, move all the schools in the list of Proprietary Schools to the right-hand side (Enterprise Schools). At this time you may also want to create a shortcut for each school using the “Create Shortcut to:? option. Click Update and all schools in the enterprise environment will be set to read and write to Enterprise.
  4. Now it is possible to compare the live or testing legacy data, to the testing Enterprise data.

Subsequent Test Migrations

Typically the test migration will find some data anomalies that need to be addressed. To test out the migration after some data has been altered or something significant like transfer to new year has been run, please copy the files from the live legacy area into the testing legacy area again. This time exclude structure files and the Central Office 'Schools', 'Schools.unc' and 'Schools.ini' files.