Configuring kettle.properties

The kettle.properties file holds the ETL Client environment variables that are used each time the ETL session is opened.

These variables can be established through the desk top application or through the Windows Batch Script scheduled to run the jobs. The kettle.properties file is created when creating the repository and is specific to the ETL Client. Some ETL Clients can be shared for non-production environments.

The kettle.properties file that is used by the application is in the .kettle sub-directory set in your KETTLE_HOME system environment variables.

To find your KETTLE_HOME:

  1. Open the Control Panel.
  2. Click System.
  3. Click Advanced system settings.
  4. Click Environment Variables and search for the KETTLE_HOME variable.
  5. Open the folder that is mentioned in the KETTLE_HOME variable and find the .kettle sub-directory.
  6. Open the kettle.properties file.
    These are the standard variables that are included in the kettle.properties and used in the Data Lake transformations and jobs: 
    MAIL_CONFIG_FILE=C:/Infor/IONETL/mail.properties

IONAPI_FILE=C:/Infor/IONETL/TENANT_TRN.ionapi
DATALAKE_HOURS=-5
DATALAKE_DAYS=-2

M3_CONO=100
M3_DIVI= BETWEEN '' AND '999'
  7. If required, update the properties by setting the location of the Mail Configuration and the files with the authorized app credentials (.ionapi files).

    See "Service Authorized App (.ionapi)".

    If you use an older version of the ETL Client (before 2022-08), you may be using the query string in the Data Lake input step and the DATALAKE_HOURS and DATALAKE_DAYS. You can configure the default values in the kettle.properties file.

    We recommend that you move from using these static values to the newer dynamic selection.

  8. Before setting up any transformations, add these additional variables to the kettle.properties file: 
    DATALAKE_DEFAULT_STARTDATE=1900-01-01T00:00:00.000Z

DB_HOST=
DB_TARGET_NAME=
DB_INSTANCE=
DB_PORT=
DB_USER=
DB_PW=

    These additional variables are used for the latest incremental process and set the staging (target) database variables.

    By setting the staging (target) database variables in the kettle.properties files, life cycle promotion to update the DB information is done in one location.

    Note: The DB_PW must be encrypted if the environment variable is utilized. Use the command prompt, navigate to the current version of the installation directory. Use the encryption utility: encr -kettle {password}
  9. Copy the whole line starting with “Encrypted” from the command prompt into the DB_PW variable.
Related topics