Setting up an Execution Server

It is on the Execution Server that the Hopp migrations actually execute. The server hosts the databases that are used in the migration.

A characteristic feature of an Execution Server is that it has the Hopp Agent Windows Service installed. The service is responsible for launching the migration processes when requested via the Portal.

Configure Folders

Recommended folder structure on Execution Server

• D:\MigFx
  1. Database: Database files for databases global to the migration server
  2. Runtime: The MigFx Service Account must have full control access to this folder
     • Track (one numbered sub folder pr track on the Migration Server)
       • 01
         1. Database: Place the MigFx_01_Migration and MigFx_01_Staging database files here 
         2. (The MigFx Runtime will automatically create other, required folders for the Track here)
       • 02 ….
       • XX
         1. Database:  MigFx_XX_Migration and MigFx_XX_Staging database files

Create Databases

Install Sql Server as per previous guidelines. 

NB: Please ensure that all databases are created with the same Sql Server collation. We recommend using the Sql Server collation Latin1_General_100_CI_AS_SC_UTF8 for all Migration and Staging databases

• Create database MigFx_Utility
  1. Database files in D:\MigFx\Database
  2. Run setup script MigFx.UtilityDb.Setup.sql
     
     
• For each Track XX: 
  1. Note: In a setup where multiple execution servers are connecting to one database server, the track-specific databases below should be named accordingly (database name should include the name of the execution server)
     
     
  2. Create database MigFx_XX_Migration
     • Database files in the D:\MigFx\Runtime\Database\XX\Database
     • Run setup script MigFx.MigrationDb.Setup.sql
       
       
  3. Create database MigFx_XX_Staging
     • Database files in the D:\MigFx\Runtime\Database\XX\Database
     • (no setup script, database is maintained automatically by MigFx)

Install Hopp Components

• Run the MigFx.EngineFramework.msi installer
  
  
• Run the MigFx.Director.Agent.msi installer
  1. Navigate to the installation folder (normally C:\Program Files\HoppTech\migFx\Agent) and edit the MigFx.Agent.dll.config file:
     • MigFxMaster connection string must connect to the MigFx_Master database on the Master Server
       
       
     • Change RuntimePath to point to the Director folder on the master server (local path is single master install, Network Uri (starting with \\) if multi-server setup
       
       
     • If you need to access the RuntimePath with credentials, set Credentials to the credentials as needed. If not, you can delete this element
       
       
  2. Change the service to run under the Hopp Service Account
     • Open the Services Control Panel add-in (Windows-R, services.msc) and locate the Hopp Runtimer Agent service
       
       
       
       
     • Open the Properties dialog for the service 
       • Ensure that Startup mode is set to Automatic (Delayed Start) if available, otherwise Automatic (earlier versions of Windows)
         
         
         
         
       • Set the Logon user to the Hopp Service Account