| Info |
|---|
This article in Russian: https://wiki.hydra-billing.ru/pages/editpage.action?pageId=11862238 |
What is It Used for?
The application is created to facilitate three main tasks — loading data within the intermediate schema, checking data, and matching the data from the original system against these in Hydra, as well as assigning default values for migration.
Default Values
Deafault values are a set of basic settings and parameters that should be configured before starting to work with the application. For example, you can specify a default region. In this case, all regions created during migration will belong to this region.
Default values are configured by HBS engineers.
Matching
Certain data are not migrated but rather matched against entities that have already been created in Hydra. Such data belong to the following sections:
- Account types
- Banks
- Currencies
- Equipment types
- Groups
- Network services
- Payment types (for real and virtual funds)
- Price plans and services
- Statuses
Matching during migration helps filter and get rid of the major part of incorrect or obsolete data.
Steps to Prepare for Migration
The expected procedure is strictly scheduled in terms of the sequence between migration sections so that certain sections become available only upon successful completion of works with the previous ones. Before initiating a test migration you are to deploy the refined dump at the test database which was previously exported from the main database, otherwise, when performing migration at the stages further than the Final Testing stage there might be data overlap of the previous migration results.
Step 1. Loading Data
Click the loading section to open the page for loading archive for export. For proper loading, exported CSV tables (data separator — quotations ("), field separator — semicolon (;) are to be archived into zip file and uploaded to the data loading section. There must be only exported files, no subdirectories.
Also note that the archive must contain the full list of tables as per Intermediate Schema for Data Migration. If for some reason you don't need to use some of the tables they still should be present inside the archive as empty ones with just the headers.
Messages on errors as well as successfully loaded tables are shown here. Errors that are critical for further steps are marked with red.
When there are no errors you will be allowed to proceed to the next step — checking exported data automatically.
Step 2. Checking Exported Data Automatically
There is a special section for automatic checking. Here the system checks the exported data for referential integrity, format correctness, the presence of required data and other things that cannot be checked manually.
The application has two sections for checking exported data — preliminary testing (right after exporting) and final testing (performed after matching).
To initiate checking, choose a section and click Start Migration.
Error messages will be logged. You can view them by clicking the section name, as in the example above, Preliminary Testing.
Step 3. Matching Exported Data
Here the exported data is matched against entities already created in Hydra.
Click the section to open the table:
On the left, you can see the original exported data (Code, Name) — data to be matched.
On the right, you can use lookup fields to choose corresponding entities from Hydra — data to be matched against.
For the most of the sections, you can also fond corresponding values in Hydra by similar names. To do so, choose the necessary section (see checkboxes on the left) and click Start Migration, thus matching them automatically.
In each section, there will be logged mismatches that should be corrected manually.
Step 4. Second Checking
It is different from the first check only in deploying another section, i.e. the set of checking procedures is different. To start checking, select the Pre-processing exported data section and click Start Migration. Note that you will be able to choose this section only after all sections with matches are closed (it is done automatically when all data is matched). If for any reason the section cannot be marked as a completed one despite finished matching, you need to contact HBS tech support.
Upon completing works for the Pre-processing exported data section you will be granted access to Final testing. Again, you should select it and click Start Migration. Typically, completing this check is regarded as the end of all required works by the provider, and the rest of the migration is done by HBS engineers.