Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

Excerpt
hiddentrue

Execute Jobs in Batch Mode

Index

Kitchen? ?????

...

??

...



What is Kitchen?

Anchor
What is Kitchen?
What is Kitchen?

Kitchen is a program that can execute jobs designed by Spoon in XML or in a database repository. Usually jobs are scheduled in batch mode to be run automatically at regular intervals.

Installation

Anchor
Installation
Installation

The first step is the installation of Sun Microsystems Java Runtime Environment version 1.5 or higher. You can download a JRE for free at http://www.java.com/ ??? JRE? ?? ?? ? ????.? ?, ????? ??? zip??? ??? ????? ??? ?? ???.
??? ? Kettle ?????? ?? ?? ??? ?? ????. ??? ?? ?????, ??????? ???? ??? ??? ???.  ?? ??? ????, Kettle ?????? ?? ?????? ????? ???.

After this, you can simply unzip the distribution zip-file in a directory of your choice.
In the Kettle directory where you unzipped the file, you will find a number of files.
Under Unix-like environments (Solaris, Linux, OSX, ...) you will need to make the shell scripts executable. Execute these commands to make all shell scripts in the Kettle directory executable:

Code Block
cd Kettle
chmod +x *.sh



Launching Kitchen

...

Anchor
Launching Kitchen ????
Launching Kitchen ????
?? ????? Carte? ???? ?? ???? ?????? ????.

To launch Kitchen on the different platforms these are the scripts that are provided:

  • Kitchen.bat: run Kitchen on the Windows platform?? Kitchen? ??.
  • kitchen.sh: Unix platform ? Mac OSX?? Kitchen? ??.

...

??? ?? ??

...

  • run Kitchen on Unix platforms and Mac OSX

Kitchen can be run on any platform that has a version of the Java Runtime Environment version 1.5 or higher.



Command line options

Anchor
Command line options
Command line options

These are the command line options that you can use.

IMPORTANT NOTES:
Windows ??????, ??? ???? On Windows system, the use of the minus ("-") ? equalin the options causes problems as well as the equal sign ("=")? ???? ??? ?? ???. ? ???, 2.2.2 ?? ??? ? ??? ?? ? ? ????.
( Because of this, from version 2.2.2 on, you can also use this format or any combination of /,- and :,=)
????? ??? ??? ?? ??? ???? ?? ?????.
?? ?? ?? ????? ???, ????(quotes or double quotes)? ?????. ??? ??? ??? ??? ???
Fields in italic represent the values that the options use.
It's important that if spaces are present in the option values, you use quotes or double quotes to keep them together. Take a look at the examples below for more info.

Code Block
/option:value

??? ??? ??? ???.

...

Below are the valid options.

Display version information

Code Block
-version

? ??? Kettle? ?? ?????This option displays the version of the Kettle core library (kettle.kar)? ??? ?????.
???? ??? ?? ??? ?? ?????.

...

jar).
The build version number and build date are shown as well.

Launch XML File

Code Block
--file=XML????

...

filename

This option runs the job defined in the XML file. (.kjb : Kettle Job)

...

Set the logging file

Code Block
-log=???? ??

????? ?? ???. ???? ?? ??(stdout) ???.

...

Logging Filename

Specifies the log file. The default is the standard output.

Set the logging level

Code Block
-level=????

????? ???? Job? ????? ?? ???.
????? ??? ??? ??? ????:

  • Error: ??? ???.
  • Nothing: ?? ??? ?? ??.
  • Minimal: ???? ??? ???.
  • Basic: ??? ????.
  • Detailed: ??? ????.
  • Debug: ??? ???? ?? ??? ??.
  • Rowlevel: (row)? ??. ? ??? ?? ???? ?? ? ? ????.

...

Logging Level

The level option sets the log level for the job that's being run.
These are the possible values:

  • Error: Only show errors
  • Nothing: Don't show any output
  • Minimal: Only use minimal logging
  • Basic: This is the default basic logging level
  • Detailed: Give detailed logging output
  • Debug: For debugging purposes, very detailed output.
  • Rowlevel: Logging at a row level, this can generate a lot of data.

Choose a repository

Code Block
-rep=?????

...

Repository name

Connect to the repository with name "Repository name".
You also need to specify the options -user, -pass, -dir ? and -job ??? ??? ??? ???.
???? KETTLE_REPOSITORY ? ? ??? ?? ? ?? ????.

...

.
You can also specify this option in the form of environment variable KETTLE_REPOSITORY.

Set the repository user name

Code Block
-user=?????

??? ???? ??? ???? ??? ?? ???.
??, ???? KETTLE_USER ? ? ??? ?? ? ?? ????.

...

Username

This is the username with which you want to connect to the repository.
You can also specify this option in the form of environment variable KETTLE_USER.

Set the repository password

Code Block
-pass=????

???? ?????? ???? ????.
???? KETTLE_PASSWORD ? ? ??? ?? ? ?? ????.

...

Password

The password to use to connect to the repository
You can also specify this option in the form of environment variable KETTLE_PASSWORD.

Select the repository job to run

Code Block
-job=Job??

?? ? Job? ????? ???? ?? ? ??? ?????. "-dir" ???? ????? ?? ? ???.

...

 Name

Use this option to select the job to run from the repository. Please also select the directory with the "-dir" option.

List the directories in the repository

Code Block
-listdir=Y

Print a listing of all the sub-directories in the repository directory specified with the option "-dir" ???? ?? ? ????? ????? ?? ?? ???? ???? ?????.

Set the repository directory

Code Block
-dir=directory

Specifies the directory in the repository to use. Repository directories are specified like this:

...

From version 2.2.2 on, a / (slash) is used to separate directories on all platforms.

List the repository jobs

Code Block
-listjobs=Y

Show a list of all the jobs in the repository directory specified with the option "-dir".

List the available repositories

Code Block
-listrep=Y

Print a listing of all the defined repositories.

Don't log in to the repository

Code Block
-norep=Y

If you have set environment variables KETTLE_REPOSITORY, KETTLE_USER, KETTLE_PASSWORD, you can prevent Kitchen from logging into the repository. For example if you want to launch a job from an XML file.

...



Path

Anchor
?? Path ??
Path

Please make sure that you are positioned in the Kettle directory before running the samples below. If you put these scripts into a batch file or shell script, simply do a change directory to the installation directory:

...

Code Block
cd /product/Kettle/

??? ?? Job ?? ??

...



...

Run a job from file

Anchor
Run a job from file
Run a job from file

This example runs a job from file on a windows platform:

...

Code Block
kitchen.sh -file=/PRD/updateWarehouse.kjb -level=Minimal

?????? ?? Job ????

...



...

Run a job from Repository

Anchor
Run a job from Repository
Run a job from Repository

This example runs a job from the repository on a windows platform:
(Enter on a single line without returns...)

Code Block
kitchen.bat
                    /rep:"Production Repository"
                    /job:"Update dimensions"
                    /dir:/Dimensions
                    /user:matt
                    /pass:somepassword123
                    /level:Basic

...



Redirecting output

Anchor
?? ??? ?? ?? ??? ?? Redirecting output
Redirecting output

If you don't want the output of the file to appear on the screen but rather be put into a log file, you can use redirection.

...

Code Block
kitchen.bat /file:C:\PRD\runAll.kjb /level:Basic > C:\LOG\trans.log

...



Return codes

Anchor
???? ???? Return codes
Return codes

Kitchen returns an error code based on how the execution went:

  • 0 : The job ran without a problem.
  • 1 : Errors occurred during processing
  • 2 : An unexpected error occurred during loading / running of the job
  • 7 : The job couldn't be loaded from XML or the Repository
  • 8 : Error loading steps or plugins (error in loading one of the plugins mostly)
  • 9 : Command line usage printing

...



Scheduling

Anchor
???? ???? Scheduling
Scheduling

Schedule a job on windows

The best way to go at it is to test the command first at the dos prompt.
Then you can use the windows scheduler to launch this command.
Windows versions since Windows 2000 have a GUI for doing this accessible through the control panel. However it's also possible to use the command line to do this:

...

To see a list of the scheduled commands simply type:

Code Block
at

Schedule a job on Unix

First create a shell script that runs all the jobs you need. Then you can schedule this script to run.
On Unix like systems the easiest way to schedule a command is by using the "cron table". You can do this by entering the following command:

...