Kettle deployment in a Linux environment (JDK installation configuration, kettle installation configuration, resource pool configuration, scheduled job execution)

I. Deployment Readiness

1.1 Java Installation (abbreviated)

1.2 JDK Configuration

1. Command line type "CD/ETC" into the ETC directory

2. Command line type "VI profile" to open the profiles file

3. Tap the keyboard ctrl+f to the end of the file

4. At the end, that is, the first ~ place, tap the keyboard to enter the following content into the file

Export java_home=/usr/java/jre1.6.0_45

Export path= $JAVA _home/bin: $PATH

Export classpath=.: $JAVA _home/lib/dt.jar: $JAVA _home/lib/tools.jar

5. Keyboard tapping exc, command line type ": Wq", save the file;

JDK Configuration succeeded:

1. Command: java-version. Version information appears

2. Command: Echo ${java_home} configuration path appears

Two. Kettle Deployment

1. Create a folder under Linux under a directory to extract the kettle you downloaded from the official website (my is pdi-ce-5.0.1.a-stable.zip) and put it in the folder

Under

2. Locate the path where the kitchen.sh is located under the extracted path, enter the directory, and grant the. sh file execution permissions through chmod +x *.sh.

Here is a detailed description:

Type./kitchen.sh, and look at the input information

bash:/kitchen.sh: Permission denied

From the above can be seen kitchen.sh lack of execution permissions, we re-enter to look at the File box folder permissions

As can be seen from the above, the directory below the. sh file does not have Execute permission (X), next we give this folder all the. sh files assigned to execute permissions

From the above we can see that the empowerment of success!

Again./kitchen.sh, enter to see output information--

You can see the help information in these kettle that appeared above-rep,-user,-pass, stating Kettle deployment was successful!

3. Enter the command./kitchen.sh. If a help message appears, the deployment succeeds.

4. Configure the Resource library

The kettle repository uses a database to create many tables in the database, so you choose how you use the file repository. If you simply use the file method rather than the file repository, in the job reference conversion to choose the file local path, from Windows to Linux in the path to the problem, although can be modified manually, but every time the modification is annoying.

Using the file repository is much simpler.

Of course, using the repository requires uploading the. Kettle folder to the. Kettle folder in Linux,windows in Administrator. If kettle is used in Linux, it will be built automatically in the user directory. Kettle folder, if not used, may not have this folder, then manually created. However, the creation is not visible. Location in/home/user/.kettle. Mine is under the Kettle User root directory: The kettle folder is hidden from the "ls-a" command to view hidden folders.

My repository content: Repositories.xml

XML code

2. <? XML version= "1.0" encoding="UTF-8"?>
4. <repositories>
6. <repository> <ID>kettlefilerepository</ID>
8. <name>filerepository</name>
10. <description>filereposity</description>
12. <base_directory>C& #x3a;& #x5c;D ata& #x5c kettlerepository</base_ Directory>
14. <read_only>n</read_only>
16. <hides_hidden_files>n</hides_hidden_files>
18. </repository> </repositories>

The <base_directory> section is the repository path under Windows, and the repository path to Linux will need to be changed. You can then put the transformations and jobs you have designed under Windows into this folder.

Finally, call the job script:/opt/kettle/data-integration/kitchen.sh-rep=filerepository-job=testjob

Specify the Repository ID and job name.

Mine is to get the path on SVN. So you need to install SVN under Linux. Cond...

Kettle deployment in a Linux environment (JDK installation configuration, kettle installation configuration, resource pool configuration, scheduled job execution)