Migration Steps

The steps types are the following:

• Global step: it contains generic properties values to be used when specific ones are not set.
• Configuration step: it represents a logical connection to the database.
• Action step: it can be one of the following:
  • Creation or deletion step: executes scripts from the sql files. The scripts aims to creates or deletes database items.
  • Data loading step: loads data to the database.
  • Conversion step: converts the data to a specific format.

The Migrator Tool accept .ini input files with the -configurationIni option. Each .ini file can contains one or more steps.                                         
For more readability, the steps can be specified inside 2 input files:

• The config.ini file, including one or more configuration steps.
• The all.ini file, including one or more action steps. The global step can be included in this file.

A step corresponds to a section in the .ini file.

• Each section have an id as title. The id is a combination of a typeand a name connected with a hyphen. (e.g.[type - name])

The section type must be one of the following:

• Database : for a configuration step.
• ExecuteSql : for a creation or deletion step.
• CSV2DB : for a CSV data loading step.
• EBCDIC2DB : for an EBCDIC data loading step.
• ConvertQDDS: for a QDDS data conversion step.

Notes

• A section should have a unique id. If many sections have the same id, only the content of the last one will be taken into consideration, however, the order of the first one will be kept.
• The configuration steps and the global step do not accept duplicated section id.
• Since the global step is unique, its id is "Global".
• The connection name should be specified in the action steps.
• When generating a reverse project using Analyser, a template of "all.ini" file will be created under yourReverseProject\database\stepsIniFile

Global step

Since the global step is unique, its id is Global. The global step contains the following properties to consider when they are not specified in the specific steps.

Notes

• If a property is specified in a step, it must have a non-empty value.              
• If the property is missing, its default value will be taken into consideration.              
• An environment variable can be used as a property value.               
• The global step is optional.               

Configuration step

The configuration step contains the following properties to create a connection to the database:

Database identification

Steps

POSTGRE configuration step example

[Database - cnxPostgreSQL1]
adminDataBaseName=postgres
adminDataBaseUser=postgres
adminDataBasePassword=P@ssw0rd 
dataBaseHost=localhost 
dataBasePort=5432 
dataBaseName=mydb 
dataBaseUser=myuser 
dataBasePassword=mypwd
dataBaseAdditionalArgs="?currentSchema=APL002" 
stepDatabaseKillDropCreate=true
stepDatabaseCreateScriptPath=database/database/create-database.sql

Creation or Deletion step

The creation or deletion step contains the following properties to consider to execute the SQL targeted scripts.

Deletion step example

[ExecuteSql - Drop tables] 
input.folder=database/tables-drop 
database=cnxPostgreSQL1 
multithread=1

Creation step example

[ExecuteSql - Create tables] 
input.folder=database/tables 
database=cnxPostgreSQL1 
multithread=1

Data loading step

The data loading step contains the following properties to consider when loading data to the database.

DATA

CSV

EBCDIC

Miscellaneous

CSV Data loading example

[CSV2DB - Loading1] 
csvQuote=' 
csvSeparator=, 
database=cnxOracle1 
encoding=UTF-8 
input.folder=datas 
keepDebugFiles=true 
multithread=5 
temp.folder=dataTemp

EBCDIC Data loading example

[EBCDIC2DB - Loading1] 
csvQuote=' 
csvSeparator=, 
database=cnxOracle1 
encoding=CP1145 
ebcdicCodePointShift=0 
ebcdicNullByteIndicatorPositionMode=ALWAYS_RIGHT 
ebcdicOid=false 
ebcdicOidLength=0 
ebcdicVarcharAsChar=false 
ebcdicZonedMode=EBCDIC_STRICT 
input.folder=data 
keepDebugFiles=true 
multithread=10 
temp.folder=dataTemp 
zipContentWildcard=P???

QDDS Conversion step

The QDDS conversion step contains the following properties to consider when converting the QDDS data.

QDDS Conversion step example

[ConvertQDDS - Conversion1] 
database=cnxPostgreSQL1 
encoding=CP037 
input.folder=inputs 
output.folder=data/DataFiles