Difference between revisions of "Running ETL Scenarios"
From Toolsverse Knowledge Base
(Created page with "== Running ETL scenario using standalone executable == # Open APP_HOME/config/etl_config.xml file in your favorite text editor. # Add connections for the particular ETL scena...") |
(→Running ETL scenario using standalone executable) |
||
Line 10: | Line 10: | ||
'''Example of the etl_config.xml:''' | '''Example of the etl_config.xml:''' | ||
+ | <syntaxhighlight lang="xml"> | ||
<?xml version="1.0" encoding="UTF-8"?> | <?xml version="1.0" encoding="UTF-8"?> | ||
<config> | <config> | ||
Line 36: | Line 37: | ||
</execute> | </execute> | ||
</config> | </config> | ||
+ | </syntaxhighlight> | ||
In this example move.xml ETL scenario located under the {app.data}/scenario folder will be executed using extract_load action. Alias test javadb will be used for the source connection and alias test oracle for the destination. | In this example move.xml ETL scenario located under the {app.data}/scenario folder will be executed using extract_load action. Alias test javadb will be used for the source connection and alias test oracle for the destination. |
Revision as of 15:15, 31 July 2014
Running ETL scenario using standalone executable
- Open APP_HOME/config/etl_config.xml file in your favorite text editor.
- Add connections for the particular ETL scenario
- Specify connections to use and scenarios to run
- Save
- Run ETL executable. For example c:\etl\etl.exe on Windows
- When it is finished check the etl.log file located under APP_HOME/logs
Example of the etl_config.xml:
<?xml version="1.0" encoding="UTF-8"?> <config> <connections> <connection alias="test javadb"> <driver>org.apache.derby.jdbc.EmbeddedDriver</driver> <url>jdbc:derby:{app.root.data}/demo/javadb</url> </connection> <connection alias="test oracle"> <driver>oracle.jdbc.driver.OracleDriver </driver> <url>jdbc:oracle:thin:@localhost:1521:orcl1</url> <userid>user</userid> <password>password</password> <params/> </connection> </connections> <active.connections> <sourses> <source alias="test javadb" /> </sourses> <destination alias="test oracle"/> </active.connections> <execute> <scenario name="move.xml" action="extract_load" /> </execute> </config>
In this example move.xml ETL scenario located under the {app.data}/scenario folder will be executed using extract_load action. Alias test javadb will be used for the source connection and alias test oracle for the destination.