Execution of a data migration in Hopp is organised in Tracks. Tracks are different states of the migration for setup for operational purposes. By using multiple Tracks different sets of migration code, data and paramerers can be processed and results viewed.
A given Track is a container for all the artefacts necessary to execute data migration iterations for one project:
- An application repository: A folder containing the engine libraries deployed as a result of the code generation
- A Staging database: A SQL Server database containing (generated) tables and SQL functionality (generated stored procedures) used by the generated source engine to produce the export result
- A runtime database: A SQL Server database used by the Runtime to store the intermediate and results of the data migration as well as the events that occurred for each business object
To manage of all this, hopp also includes a Master database containing all information necessary for the Portal Operation to manage all the different Tracks:
- Which migration projects are executed in which tracks
- Folder locations for the track
- Database connection strings for the track
- Etc.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article