Studio

Normally, in a data migration setup of any significant size, the Core Runtime will run on one or more dedicated servers.

However, in a tiny setup, it is perfectly possible to establish and execute the Core Runtime on a local machine as well. A complete Core setup leveraging the full execution facilities of the Core includes the ability to iterate concurrently over separate data migration projects in the Core setup.

In this full-scale scenario, the Core can execute several isolated migration projects on one or more dedicated servers in so-called Tracks. One server may host multiple tracks, and the Core can handle multiple servers – each with multiple tracks.

Yes, definitely. This software component is made to work with rules of all levels of complexity, so developers can implement rules that fit the needs and details of their projects.

All elements of hopp are centered on Business Objects. A business object represents all the data flowing through the migration-related to one specific item in the business being migrated. Examples of business objects of course depend on the nature of this business, but could be Customer, Account, Policy, Patent, Mortgage, etc.

Business Objects are organized in hierarchies providing a set of root business objects each with a recursive hierarchy of sub-business objects. Business Objects are the basis for the mapping, for the actual iterations of the migration executions, and for the surfacing of the migration iteration results and events. When executing, every business object passes through the migration steps as one unit

The Target Map is founded on the description of the Target data.

The Target Map eliminates internal references and data that can be derived from other data and exposes the data that cannot be derived and, thus, must be received. In addition, the Target Map can implement a vast host of runtime validations to ensure the highest quality possible for the target data being produced by the data migration.

The Target Map is strongly linked to the target system, and this mapping can be reused in all migrations to the same target system. The value of improving/extending the Target Map is retained over time, from project to project.

The Source Map is based on both the source data descriptions as well as the data requirements exposed by the Target Map.

While the target mapping exposes the data that must be received, it does so in the terms of the target system. In addition, all validation is founded on value sets known by the target system.

On the other hand, the Source Map describes how – based on the source data – to produce the data required by the target map.

Finally, the export can be exported from the Studio as a complete, structured specification as input for the engine generator generating the export engine.