> 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-2-unpack-the-files.md).

# Step 2: Unpack the files

Unpack the files by completing these steps.

1. Use a ZIP tool to extract the file you just downloaded.

   **CAUTION:**

   Do not use Unarchiver 3.3 to unzip files; it may corrupt the plugin file names.
2. Open a Command Prompt window or a Terminal window and navigate to the folder that contains the files you just extracted.
3. Depending on your operating system, enter one of the following commands at the prompt.
   * Windows: `install.bat`
   * Linux: `./install.sh`
4. Read the license agreement that appears. Select **Accept**, then click **Done**.

   **Note:** If you are unpacking the file in a non-graphical environment, open a Terminal window or a Command Prompt window and type `java -jar install.jar -console` and follow the instructions presented in the window.
5. Specify where you want the file to be unpacked.

   This location can be temporary because you will be manually placing the files in the appropriate directories later in these instructions.
6. Click the **Next** button. The Installation in Progress window appears.
7. When the installation progress is complete, click **Quit** to exit the Unpack Wizard.


---

# 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-2-unpack-the-files.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.