iLoader Script and Load
Overview
Allows Kettle run locally to trigger iLloader scripts to load data into engine
This step will only run outside Alterian Journey Orchestration.
Plugin Configuration
Within the plugin:
The following settings can be configured:
Setting | Description |
---|---|
Direct Load | Allows you to choose whether you want to directly load the data into Engine or load it via a iloader script. If Direct Load is selected you do no need to specify an iLoader script or data input file name but you will need to stipulate either a buffer size or buffer time or both |
Project name | Name of the Engine project you want to load your data into. |
Engine Database Name | Provide the name of the Database you want to load this data into |
Engine Table Name | Provide the name of the Table within the Database you want to load this data into |
Delimiter | Choose the delimiter used in you data file.
|
Qualifier | Choose a delimiter qualifier if you are using one
|
Table Operation | Choose the operation the file being loaded willl do. Will it refresh, append or update the table.
|
Engine user name | Provide the engine username you want to use to access engine allowing the operation to take place. Care needs to be taken to ensure this information is stored securely. |
Engine passsword | Provide the engine password for your chosen username. Care needs to be taken to ensure this information is stored securely. |
File Format | When loading data via a script you can optionally choose the file format, either delimited or Fixed.
|
ILoader Script File name | Browse and select the iLoader script you want o use as part of the file load process. |
Data Input File name | Select the data input file you want to load using this step |
Create input file | When selected the input file will be created by the step |
Fields | Define the fields required in the data file. Get Fields allows you to select the fields present in the transformation at this point. |