> 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/pdc-10.2-data-optimizer/pdso-install-landing-page/pdso-install-in-hadoop-cluster/pdso-install-landing-page-hadoop-installation/installing-data-storage-optimizer-on-cloudera-manager-cluster-cp/download-the-parcel-to-cloudera-manager-pdso-install-in-hadoop.md).

# Download the parcel to Cloudera Manager

If you are using a local parcel repository, skip this section and proceed to [Distribute and activate the parcel](/pdc-10.2-data-optimizer/pdso-install-landing-page/pdso-install-in-hadoop-cluster/pdso-install-landing-page-hadoop-installation/installing-data-storage-optimizer-on-cloudera-manager-cluster-cp/distribute-and-activate-the-parcel-pdso-install-in-hadoop.md).

This task assumes you have an internally-hosted remote parcel repository.

1. Log into Cloudera Manager Admin Console and click **HostsParcels** in the top navigation bar.

   The Parcels page opens.
2. Click **Configuration**.

   The Parcel Configurations dialog box opens.
3. Locate the **Remote Parcel Repository URLs** setting and add the location of the Data Optimizer parcel on your internally-hosted remote repository server as your new entry.

   The value of the new entry is the location of the Data Optimizer parcel on your internally hosted remote repository server. For example, if your remote repository is located at `https://myrepo.example.com/parcel-repo/`, then the value would be `https://myrepo.example.com/parcel-repo/pdso/1.2.0/`.
4. Save your changes to return to the Parcels page.
5. Click **Check for New Parcels**.

   The `pdso` parcel entry displays in the parcel list with a status of **Available Remotely**.
6. Click **Download** for the `pdso` parcel.

When the process is complete, the status of the parcel changes to **Downloaded**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/pdc-10.2-data-optimizer/pdso-install-landing-page/pdso-install-in-hadoop-cluster/pdso-install-landing-page-hadoop-installation/installing-data-storage-optimizer-on-cloudera-manager-cluster-cp/download-the-parcel-to-cloudera-manager-pdso-install-in-hadoop.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.