> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/pentaho-installation-overview-cp/manual-installation/step-3-configure-and-start-the-pentaho-server-after-manual-installation.md).

# Step 3: Configure and start the Pentaho Server after manual installation

How you configure and start the Pentaho Server after a manual installation depends on your OS.

## Configure the Pentaho Server on Windows

Complete these steps to configure the Pentaho Server on Windows.

{% hint style="warning" %}
**Important**: The server will not start if any environment variable value is invalid.
{% endhint %}

{% stepper %}
{% step %}

### **Modify the Tomcat startup script**

The Tomcat startup script must include:

* `CATALINA_OPTS` (Java options, including memory)
* `DI_HOME` (required for PDI components)
* The license file location

1. Copy all `.jar` files from:

`<pentaho_install_dir>\pentaho-server\pentaho-solutions\native-lib\win64`

To:

`<tomcat_webapps_dir>\pentaho\WEB-INF\lib`

2. Add the `LIBPATH` variable to the Tomcat `startup.bat` file:

```bat
set LIBPATH=<pentaho_install_dir>\pentaho-server\pentaho-solutions\native-lib\win64
```

3. Make sure Tomcat is not running.
   1. Open **Task Manager**.
   2. Look for **Tomcat**.
   3. If Tomcat is running, stop it.
4. Open the startup script in a text editor:

`<pentaho_install_dir>\pentaho-server\tomcat\bin\startup.bat`

5. Find the `CATALINA_HOME` section.

Add this line before it:

```bat
SET DI_HOME=%~dp0..\..\pentaho-solutions\system\kettle
```

6. Add the license option to `CATALINA_OPTS`.

Update the existing `CATALINA_OPTS` line by adding:

`-Dpentaho.license.information.file=%PENTAHO_LICENSE_INFORMATION_PATH%`

Example:

{% code overflow="wrap" %}

```bat
SET CATALINA_OPTS=-Xms4096m -Xmx6144m -Djava.library.path=%LIBPATH% -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dpentaho.license.information.file=%PENTAHO_LICENSE_INFORMATION_PATH% -DDI_HOME=%DI_HOME%
```

{% endcode %}

7. Save and close the file.
   {% endstep %}

{% step %}

### **Run the Pentaho Server as a Windows service (optional)**

You can create a Tomcat task to run the Pentaho Server as a Windows service.

For details, see [Tomcat Windows service how-to documentation](https://tomcat.apache.org/tomcat-8.0-doc/windows-service-howto.html).

When you run `tomcat8w.exe`, use these settings:

* **Startup** tab
  * **Working Path**: Add `bin` to the end of the path. Example: `C:\pentaho\server\pentaho-server\tomcat\bin`
* **Java** tab
  * **Initial Memory Pool**: `2048`
  * **Maximum Memory Pool**: `6144`
  * **Java Options**: add the following items:
    * `-DDI_HOME`
    * `-Dfile.encoding`
    * `-Djava.library.path`
    * `-Dpentaho.license.information.file`

Example values:

* `-DDI_HOME=C:\pentaho\server\pentaho-server\pentaho-solutions\system\kettle`
* `-Dfile.encoding=utf8`
* `-Djava.library.path=<pentaho_install_dir>\pentaho-server\pentaho-solutions\native-lib\win64`
* `-Dpentaho.license.information.file=%PENTAHO_LICENSE_INFORMATION_PATH%`

You must set `PENTAHO_LICENSE_INFORMATION_PATH` to point to the `.elmLicInfo.plt` file:

`PENTAHO_LICENSE_INFORMATION_PATH=<complete_path>\.elmLicInfo.plt`
{% endstep %}

{% step %}

### **Install licenses**

Install your enterprise licenses before you start the server. See [Acquire and install enterprise licenses](/install/pentaho-installation-overview-cp/acquire-and-install-enterprise-licenses.md).
{% endstep %}

{% step %}

### **Start the Pentaho Server**

Go to [Start the Pentaho Server](#start-the-pentaho-server-2).
{% endstep %}
{% endstepper %}

## Configure the Pentaho Server on Linux

Complete these steps to configure the Pentaho Server on Linux.

{% hint style="warning" %}
**Important**: The server will not start if any environment variable value is invalid.
{% endhint %}

{% stepper %}
{% step %}

### Modify the Tomcat startup script

The Tomcat startup script must include:

* `CATALINA_OPTS` (Java options, including memory)
* `DI_HOME` (required for PDI components)
* The license file location

1. Copy all `.jar` files from:

`<pentaho_install_dir>/pentaho-server/pentaho-solutions/native-lib/linux/x86_64`

To:

`<tomcat_webapps_dir>/pentaho/WEB-INF/lib`

2. Add the `LIBPATH` variable to the Tomcat `startup.sh` file:

```bash
export LIBPATH=<pentaho_install_dir>/pentaho-server/pentaho-solutions/native-lib/linux/x86_64
```

3. Make sure Tomcat is not running.
   1. Open a terminal.
   2. Run `ps -A`.
   3. If Tomcat is running, stop it.
4. Open the startup script in a text editor:

`<pentaho_install_dir>/pentaho-server/tomcat/bin/startup.sh`

5. Find the `#Check that target executable exists` line.

Add this line above it:

```bash
DI_HOME=<pentaho_install_dir>/pentaho-server/pentaho-solutions/system/kettle
```

6. Add the license option to `CATALINA_OPTS`.

Update the existing `CATALINA_OPTS` line near the end of the file.

Example:

```bash
export CATALINA_OPTS="$CATALINA_OPTS -Xms4096m -Xmx6144m \
  -Djava.library.path=$LIBPATH \
  -Dsun.rmi.dgc.client.gcInterval=3600000 \
  -Dsun.rmi.dgc.server.gcInterval=3600000 \
  -Dpentaho.installed.licenses.file=$PENTAHO_INSTALLED_LICENSE_PATH \
  -DDI_HOME=$DI_HOME"
```

7. Save and close the file.
   {% endstep %}

{% step %}

### Install licenses

Install your enterprise licenses before you start the server.

See [Acquire and install enterprise licenses](/install/pentaho-installation-overview-cp/acquire-and-install-enterprise-licenses.md).
{% endstep %}

{% step %}

### Start the Pentaho Server

Go to [Start the Pentaho Server](#start-the-pentaho-server-2).
{% endstep %}
{% endstepper %}

## Start the Pentaho Server

After you configure the Pentaho Server for your platform:

1. Define the `DI_HOME` environment variable. The default path for Windows and Linux:
   * Windows: `PENTAHO_INSTALLATION_FOLDER\pentaho-server\pentaho-solutions\system\kettle`
   * Linux: `PENTAHO_INSTALLATION_FOLDER/pentaho-server/pentaho-solutions/system/kettle`
2. Run the startup script for your web application server.
   * Windows: `startup.bat` in the Tomcat `bin` folder
   * Linux: `startup.sh` in the Tomcat `bin` directory
3. Open `http://localhost:8080/pentaho` to access the Pentaho User Console (PUC).

If your server uses a different hostname or port, update the URL.

### Troubleshoot startup issues

Troubleshooting is centralized in [Troubleshooting possible installation and upgrade issues](/install/pentaho-installation-overview-cp/installation-and-upgrade-issues.md).

## Install Pentaho client tools

After you install and start the Pentaho Server, you can install the client tools on separate workstations.

* [Install Business Analytics design tools](/install/pentaho-installation-overview-cp/installation-of-the-pentaho-design-tools.md#install-business-analytics-design-tools)
* [Install PDI client, utilities, and plugins](/install/pentaho-installation-overview-cp/installation-of-the-pentaho-design-tools.md#install-pdi-client-utilities-and-plugins)

After you install the Pentaho Server and client tools, configure them so you can:

* Install licenses.
* Sign in to the Pentaho Server.
* Set up data sources.
* Choose a security method.

See [Pentaho configuration](/install/pentaho-configuration.md).

See **Administer Pentaho Data Integration and Analytics** for instructions on setting up licenses and optional Operations Mart logging.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/install/pentaho-installation-overview-cp/manual-installation/step-3-configure-and-start-the-pentaho-server-after-manual-installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.