> 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/10.2-install/pentaho-installation-overview-cp/manual-installation/manual-installation-process/prepare-your-linux-environment-for-a-manual-installation/install-your-web-application-server.md).

# Install your web application server

If you want to install Pentaho on your own Tomcat web application server, you will first need to install that web application server. You must complete the installation yourself.

**Note:** If you already have a Tomcat web application server installed and you want to run the Pentaho Server on it, you can skip this task.

The Pentaho Server can be deployed on your own Tomcat web application server. Perform the following steps to install your web application server:

1. Check the list in the [Components Reference](/install/10.2-install/components-reference.md) to see which version of Tomcat is supported by Pentaho.
2. To download and install the web application software, use the instructions in the documentation for the web application server.

   We recommend that you install the web application server in the `pentaho/server/pentaho-server` directory.
3. Verify the web application server is installed correctly by starting it and viewing the default page.

   If the web application server does not start, troubleshoot it using the web application server's documentation before you continue with the Pentaho Server installation process.
4. Stop the web application server.


---

# 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/10.2-install/pentaho-installation-overview-cp/manual-installation/manual-installation-process/prepare-your-linux-environment-for-a-manual-installation/install-your-web-application-server.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.