> 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/9.3-install/pentaho-installation-overview-cp/installation-of-the-pentaho-design-tools/install-the-ba-design-tools/perform-a-manual-installation-of-the-ba-design-tools/step-3-install-the-design-tools.md).

# Step 3: Install the design tools

Perform the following steps to install the Aggregation Designer, Metadata Editor, Report Designer, or Schema Workbench Design Tools.

1. Create a directory for installing your design tools.

   **Note:** For publishing reports, models, and schemas created with the design tools, we recommend you install the design tools in a directory on a workstation or server that is on the same network as the Pentaho Server.

   If you are unsure of the directory in which to install the design tools, we suggest that you create a `Pentaho` directory and `design-tools` subdirectory on your workstation and install the design tools there. If you choose this option, the directory path should look like the following example:

   ```
   Pentaho/design-tools
   ```
2. Verify that you have the appropriate permissions to read, write, and execute commands in the directories you created.
3. Copy or more the extracted design tool installation file(s) to the `design-tools` directory.

   The extracted files should end up in the following paths:

   * Aggregation Designer: `pentaho/design-tools/aggregation-designer`
   * Metadata Editor: `pentaho/design-tools/metadata-editor`
   * Report Designer: `pentaho/design-tools/report-designer`
   * Schema Workbench: `pentaho/design-tools/schema-workbench`


---

# 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/9.3-install/pentaho-installation-overview-cp/installation-of-the-pentaho-design-tools/install-the-ba-design-tools/perform-a-manual-installation-of-the-ba-design-tools/step-3-install-the-design-tools.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.