Difference between revisions of "Running ETL Scenarios"

From Toolsverse Knowledge Base
Jump to: navigation, search
Line 56: Line 56:
  
 
== Using Web service to run ETL scenario ==
 
== Using Web service to run ETL scenario ==
 +
 +
Example:
 +
<syntaxhighlight lang="java">
 +
 +
/**
 +
* Creates connection aliases for ETL process, sets scenario name, remotely executes ETL scenario.
 +
*
 +
* @return ETL response
 +
* @throws Exception in case of any error
 +
*/
 +
private EtlResponse execute()
 +
        throws Exception
 +
{
 +
        // initializes system config, loads properties
 +
        SystemConfig.instance();
 +
       
 +
        // instantiates ETL config
 +
        EtlConfig config = new EtlConfig();
 +
       
 +
        // initializes ETl config
 +
        config.init();
 +
       
 +
        // creates source alias
 +
        Alias source = new Alias();
 +
        source.setName("Java DB");
 +
        source.setUrl("jdbc:derby:{app.root.data}/demo/javadb");
 +
        source.setJdbcDriverClass("org.apache.derby.jdbc.EmbeddedDriver");
 +
       
 +
        // creates destination alias
 +
        Alias destination = new Alias();
 +
        destination.setName("JSON files");
 +
        destination
 +
                .setConnectorClassName("com.toolsverse.etl.connector.json.JsonConnector");
 +
        destination.setUrl("{app.root.data}/*.json");
 +
       
 +
        // adds aliases. ETL process will create connections from these aliases
 +
        config.addAliasToMap(EtlConfig.SOURCE_CONNECTION_NAME, source);
 +
        config.addAliasToMap(EtlConfig.DEST_CONNECTION_NAME, destination);
 +
       
 +
        // creates empty ETL scenario, sets ETL action. The remote ETL process
 +
        // will load it from file at the run-time.
 +
        Scenario scenario = new Scenario();
 +
        scenario.setName("Examples/Engine/db2file.xml");
 +
        scenario.setAction(EtlConfig.EXTRACT_LOAD);
 +
       
 +
        // creates ETL request using given config, scenario and log level
 +
        EtlRequest request = new EtlRequest(config, scenario, Logger.INFO);
 +
       
 +
        if (Utils.isNothing(SystemConfig.instance().getSystemProperty(
 +
                SystemConfig.SERVER_URL)))
 +
            SystemConfig.instance().setSystemProperty(SystemConfig.SERVER_URL,
 +
                    "http://localhost:8080/dataexplorer/ide");
 +
       
 +
        // gets ETL service from the factory. The ServiceProxyWeb used as a
 +
        // dynamic proxy
 +
        EtlService etlService = ServiceFactory.getService(EtlService.class,
 +
                ServiceProxyWeb.class.getName());
 +
       
 +
        // remotely executes ETL process
 +
        return etlService.executeEtl(request);
 +
}
 +
</syntaxhighlight>
 +
  
 
== Running ETL scenario using standalone executable ==
 
== Running ETL scenario using standalone executable ==

Revision as of 12:00, 3 August 2014

Embedding ETL scenario into existing Java application

There are three easy steps:

  1. Instantiate EtlConfig
  2. Instantiate EtlProcess
  3. Execute scenario

Example:

public static void main(String[] args)
{
        LoadScenarioAndConfigurationFromFile engine = new LoadScenarioAndConfigurationFromFile();
 
        try
        {
            // instantiates ETL configuration
            EtlConfig etlConfig = new EtlConfig();
 
            // set log level to INFO which increases verbosity of the etl engine
            Logger.setLevel(EtlLogger.class, Logger.INFO);
 
            // creates embedded ETL process
            EtlProcess etlProcess = new EtlProcess(EtlProcess.EtlMode.EMBEDDED);
 
            // print out framework version
            System.out.println(SystemConfig.instance().getTitle(
                    EtlConfig.DEFAULT_TITLE)
                    + " "
                    + SystemConfig.instance().getSystemProperty(
                            SystemConfig.VERSION));
 
            // load configuration which contains source and destination
            // connections and ETL scenario name. Load and execute ETL scenario.
            // If no full path
            // provided the configuration file test_etl_config.xml is expected
            // to be under app_home/config
            EtlResponse response = engine.loadConfigAndExecute(etlConfig,
                    "test_etl_config.xml", etlProcess);
 
            // print out formatted output from the ETL response
            System.out.println(engine.getMessage(response,
                    "Exampes/Engine/db2file.xml"));
 
        }
        catch (Exception ex)
        {
            System.out.println(Utils.getStackTraceAsString(ex));
        }
 
        System.exit(0);
}

Look at other examples of embedding ETL engine into Java application.

Using Web service to run ETL scenario

Example:

/**
 * Creates connection aliases for ETL process, sets scenario name, remotely executes ETL scenario.
 * 
 * @return ETL response
 * @throws Exception in case of any error
 */
private EtlResponse execute()
        throws Exception
{
        // initializes system config, loads properties
        SystemConfig.instance();
 
        // instantiates ETL config
        EtlConfig config = new EtlConfig();
 
        // initializes ETl config
        config.init();
 
        // creates source alias
        Alias source = new Alias();
        source.setName("Java DB");
        source.setUrl("jdbc:derby:{app.root.data}/demo/javadb");
        source.setJdbcDriverClass("org.apache.derby.jdbc.EmbeddedDriver");
 
        // creates destination alias
        Alias destination = new Alias();
        destination.setName("JSON files");
        destination
                .setConnectorClassName("com.toolsverse.etl.connector.json.JsonConnector");
        destination.setUrl("{app.root.data}/*.json");
 
        // adds aliases. ETL process will create connections from these aliases
        config.addAliasToMap(EtlConfig.SOURCE_CONNECTION_NAME, source);
        config.addAliasToMap(EtlConfig.DEST_CONNECTION_NAME, destination);
 
        // creates empty ETL scenario, sets ETL action. The remote ETL process
        // will load it from file at the run-time.
        Scenario scenario = new Scenario();
        scenario.setName("Examples/Engine/db2file.xml");
        scenario.setAction(EtlConfig.EXTRACT_LOAD);
 
        // creates ETL request using given config, scenario and log level
        EtlRequest request = new EtlRequest(config, scenario, Logger.INFO);
 
        if (Utils.isNothing(SystemConfig.instance().getSystemProperty(
                SystemConfig.SERVER_URL)))
            SystemConfig.instance().setSystemProperty(SystemConfig.SERVER_URL,
                    "http://localhost:8080/dataexplorer/ide");
 
        // gets ETL service from the factory. The ServiceProxyWeb used as a
        // dynamic proxy
        EtlService etlService = ServiceFactory.getService(EtlService.class,
                ServiceProxyWeb.class.getName());
 
        // remotely executes ETL process
        return etlService.executeEtl(request);
}


Running ETL scenario using standalone executable

  1. Open APP_HOME/config/etl_config.xml file in your favorite text editor.
  2. Add connections for the particular ETL scenario
  3. Specify connections to use and scenarios to run
  4. Save
  5. Run ETL executable. For example c:\etl\etl.exe on Windows
  6. 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.

Creating and running ETL scenario using Data Explorer

The best way to create, run and schedule ETL, data integration and data migration scenario is using Data Explorer - an integrated ETL IDE.