Configuring the XML file. A migration is described in an XML file containing all steps that should be performed.

    <?xml version="1.0" encoding="UTF-8"?>
    <migration>

      <databank>
        <source
          driverType="org.javahispano.dbmt.migrations.MigrationCSVSource"
          driver="delimeter=; codepage=Windows-1251 trim=true"
          url="c:\" 
        />
        <target
          driverType="org.javahispano.dbmt.migrations.MigrationJDBC"
          driver="com.sap.dbtech.jdbc.DriverSapDB"
          url="jdbc:sapdb://127.0.0.1/DATABASE_TGT"
          username="dbuser"
          password="dbpwd"
          quoted-names="false"
        />
      </databank>
      <log level="INFO"/>

      <steps>
       <step name="EXAMPLE_STEP"
              skip='false'
              source_table="SOURCE_TABLE.csv"
              target_table="TARGET_TABLE"
              clear_target="false"
              where="INTERNAL is null OR INTERNAL=false"
              log_level="OFF"
              slice_size="1000"
              stop_on_error="true"
         >
          <field from="ID"/>
          <field from="NAME" to="OTHER_NAME"/>
          <field from="substr(DESC,1,2)||'_suffix'" to="NEW_DESC"/>
          <field from="true" to="LOGIC_FIELD"/>
       </step>
      </steps>
    </migration>

The databank tag.

In this tag we are defining types of the source and the target for this migration, giving the URL and driver parameters to be used. URL and driver parameters are dependent on types of the source and the target.

Note: Databanks org.javahispano.dbmt.MigrationSaxXMLSource and org.javahispano.dbmt.MigrationFreemarkerTarget are not compatible.

This file will be used for all steps. Full file name is url+file. If this parameter is omited then each step will use own file with name equals to step's name

Pay attention that JDBC and DBF drivers are not included in DBMT's distribution, so you should add them to your classpath. Of course this tag is mandatory.

The log tag.

DBMT uses 'org.javahispano.dbmt' JDK14 logger to informate about migration process.

In each step there is attribute 'log_level'. MigrationTarget can use for logging all insert commands into file. Now only MigrationJDBC uses this attribute.

The steps tag.

Steps are the most important part of a migration and in every step it is defined how the fields of a table should be changed to fit in the new schema. You can write so many step tags as tables we want to migrate.

    <step name="EXAMPLE_STEP"
          skip='false'
          source_table="SOURCE_TABLE.csv"
          target_table="TARGET_TABLE"
          clear_target="false"
          where="INTERNAL is null OR INTERNAL=false"
          log_level="OFF"
          slice_size="1000"
          stop_on_error="true"
     >
      FIELDS
    </step>

Next we have to write how the fields will be processed.

  <field from="ID"/>
  <field from="NAME" to="OTHER_NAME"/>
  <field from="substr(DESC,1,2)||'_suffix'" to="NEW_DESC"/>
  <field from="true" to="LOGIC_FIELD"/>

'from' attribute is mandatory. It can contain name of the field in source table or SQLJEP expresson where variables are names of columns in the source table.

If 'to' is absent then it will be get the same as 'from'.

Some MigrationTarget objects may not have information about types of fields. For example MigrationDBFTarget. When MigrationDBFTarget creates new DBF file it doesn't have information about fields types. And some MigrationSource objects can convert types. For example MigrationDBFSource represents dates only as java.util.Date type but it can convert dates to java.sql.Time or java.sql.Timestamp or java.sql.Date.

For this purposes tag 'field' has attribute 'type'.

Mapping 'type' attribute to Java class.