Export Result CSV

About

This article describes how to interprete the migration report which can be gained by migration summary view. The migration report is provided as zip archive containing a text file in CSV format (semicolon-separated).

Content

Introduction

The migration can be used to migrate an SAP AL source archive to a destination archive.

Configuring ( ) a migration there can be set two kinds of hash based consistency checks.

The migration collects result data inside a DB. These result can be seen using the summary view.

There are in column Action after every item an download button. You can also use the Download all migration reports button.

In the following section we describe how to enter this view, how to download the zipped results and how to interprete the columns in the tables.

The download of a report is only available in case a H2-Database is used.

Since version 3.2.7 it is also possible to download reports with Microsoft MSSQL or Oracle databases!

Retrieving results

Enter summary view

  • enter tomcat ui

  • open manager app

  • select the migration app

  • enter Main → Migration

  • Enter Summary view

Download

You can choose to download a single result or download all results. In both cased you’ll get a zip file.

Single result

In summary view click in the wished row and in column Action the Download CSV Report button.

As result you’ll get a zip with one CSV file inside. The name shall be like this:

Export_M04_MW_banane8_12603522985634273652.zip

After unzipping it you gain:

Export_M04_MW_banane8_12603522985634273652.csv

All results

In summary view click on Download all migration reports button.

You’ll get a zip file like this:

20210920-085703-migration-results.zip

After unzipping it you gain several files with names like this:

Export_M04_MW_banane8_12603522985634273652.csv

Export_M04_MW_banane6_2621601885127550154.csv

Interpretation of CSV files

The files containes of a head and a table.

Head

The head containes general information about the migration.

Table

The table has these columns:

Column Name

Description

Column Name

Description

ID

incrementing number

STATUS

1: DocID has been loaded into the database

2: DocID in active migration process

3: DocID was successfully migrated

4: The document could not be migrated due to an error

>4: Document has been processed in "Reprocessing", but had still an error.

DOCID

the document id

DATESOURCE

date from source archive

DATEMIGRATED 

date and time of migration

COMPIDS

the component id’s migrated

COMPIDCOUNT

the amount of components migrated

CHECKSUM_SRC

if configuration item CheckSrcHashValues is enabled, the hash transfered from source archive (only KGS CS) and hash built in migration tool is compared. If comparison was sucessful, the hash value appears in this column.

CHECKSUM_DST

if configuration item CheckDstHashValues is enabled, a hash is generated by the migration tool and sent to destination CS as HTTP header. If the destination CS is an KGS CS it can compare the sent hash with an own generated one. If this comparison fails, it will send an error response. If it is successful the CS will send an 201 HTTP status (“Created”) and the migration tool will write the hash into the column CHECKSUM_DST. Until 3.0.2 the behavior was a bit different. Please consult:

ERROR

If an error occures during migration the error is written here.

EXTRACOUNT

 

SORTKEY

 

SIZE

document size

READTIME

time consumed while reading the document

WRITETIME

time consumed while writing the document