# Loader

## How to Export table data with the external XML loader

| ### What to do:
| As a prerequesite for the folIowing example you must have created an export script as described in the example Creating an export/import script.
| To call the XML loader you have to open the command line/shell!
| Please note that the script to start the loader (loader.bat/loader.sh) is located in the following directories:
| Windows: <ep_root>/axalant/cmd/loader.bat Unix: <ep_root>/axalant/scripts/loader.sh
| Call the program with the command loader.
| Enter the following parameters according to the syntax required:
| loader <app_name> --export < export script name>.exp
| In case an error comes up, a possible reason might be that the file was not found. Read the error message carefully as it contains the search path!
| If you have successfully completed the table data export the results will be displayed as follows:
| Building on x86 # Calling "D:\Agile_e6.1\axalant\cmd\axalant_env.cmd" yin Setting environment for using Microsoft Visual Studio .NET 2003 tools. (If you have another version of Visual Studio or Visual C++ installed and wish to use its tools from the command line, run vcvars32.bat for that version.) Exporting from database db:yin/*****@melon T_MASTER_HIS. (1 ) relation records by query T_MASTER_DAT. (1 ) entity records by query BVB_ARTIKEL. (1 ) entity records by query T_CHG_OPR_DAT. (1 ) entity records by query BVB_ARTMEH. (1 ) relation records by query Writing the XML loader file "D:/Agile_e6.1/app_name/dmp/test_item.bin" T_MASTER_HIS. (1 ) T_MASTER_DAT. (1 ) BVB_ARTIKEL. (1 ) T_CHG_OPR_DAT. (1 ) BVB_ARTMEH. (1 ) Done.
| The points behind the table names are printed for every successfully exported record during the export. After having finished the export from the current table, the absolut number of exported records is indicated in brackets.

##

##