Laying the foundation before touching Pentaho: the essential data integration and ETL skills you must master, the software and tools you need to install, minimum hardware requirements, plus the steps to set up your environment using JDK and Docker for a local lab.

Welcome to the Learn Pentaho series! Before you open Spoon or write your first transformation, let's lock in the foundation. This episode covers the preparation: which skills you should already have, which tools you need on your machine, what a reasonable hardware spec looks like, and how to keep your lab environment tidy so your journey through the next 22 episodes runs smoothly.
The main message of this episode: Pentaho is a tool that moves and processes data. If you understand the concepts of ETL, SQL, and data structure, the tool simply plugs into those concepts. So don't rush to install anything before you understand the skill map.
If you're starting from zero, don't panic — but do realize that Pentaho is not a tool for learning data engineering from scratch. It speeds up work whose concepts you already understand. The minimum skills you should master:
Info
If you're not yet confident with SQL, first read the Learn SQL series on this blog. SQL is the everyday working language of a Pentaho developer — the Table input, Execute SQL script, and Database lookup steps all build on top of it.
Here's the minimum list of what your machine should have. Don't install everything at once; follow the order in the setup section below.
JAVA_HOME version is correct before running Spoon..properties and .xml configuration files. You don't need a special IDE — VS Code is enough.PDI runs as a Java desktop application, and Spoon is quite memory-hungry because it runs inside one large JVM. The numbers below are a safe minimum for learning, not for production:
| Component | Minimum Requirement | Comfortable Recommendation |
|---|---|---|
| RAM | 8 GB | 16 GB or more |
| CPU | Quad-core | 8 cores or more |
| Storage | 20 GB | 50 GB SSD (leave room for the database) |
| OS | Windows 10, macOS, or a modern Linux | Linux for production simulation |
| Screen | 1366x768 | Full HD so the step palette has breathing room |
If you only have a single 8 GB laptop, close other heavy applications while running Spoon, and add -Xmx as suggested in episode 14. If you work remotely, the lightest scenario is installing PDI on a VPS and running Spoon over SSH X11 forwarding — but that's optional.
Now the practical part. The goal of this section: you have one tidy lab folder, a verified JDK, and a database container ready to use. Follow the order so you don't get overwhelmed.
Make sure JDK 8 or 11 is installed and JAVA_HOME points to its installation folder. Open a terminal and run the commands below. If you see a version like openjdk version "1.8.0_..." or "11.0...", your Java environment is ready:
java -version
echo $JAVA_HOME
which javaIf JAVA_HOME is empty, set it in your ~/.bashrc file with your JDK installation path, then run source ~/.bashrc so the change takes effect immediately. Make sure $JAVA_HOME/bin is on your PATH.
The cleanest way to set up a database is a container. Here's an example of running PostgreSQL with a volume so the data isn't lost when the container is restarted:
docker run -d --name pentaho-pg \
-e POSTGRES_PASSWORD=pentaho \
-e POSTGRES_DB=lab \
-p 5432:5432 \
-v pentaho_pg_data:/var/lib/postgresql/data \
postgres:14Verify the container is running with docker ps. From here you can connect Spoon to localhost:5432 using the lab database — this is the connection you'll reuse again and again in the episodes that follow.
Before closing this episode, make sure every box below is checked:
JAVA_HOME is configured.transformations, jobs, and resources subfolders to keep your .ktr and .kjb files organized.Success
You don't need to memorize every command right now. What matters is that the environment is up and running and you know where to look when something goes wrong. The rest will be trained episode by episode.
In episode 0 you prepared the roadmap: the essential skills, the required tools, the minimum hardware spec, and a lab environment already standing with JDK and a database via Docker.
The key takeaways:
JAVA_HOME must be correct before running anything.In episode 1, we'll step back for a moment to study the history, background, and why choose Pentaho — how the small Kettle project grew into a complete BI platform, and where it stands compared to Talend, Informatica, and Power BI.