> 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/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/query-hcp/before-you-begin.md).

# Before you begin

In the HCP [Tenant Management Console](https://knowledge.hitachivantara.com/Documents/Storage/Content_Platform/8.1.2/Tenants_and_Namespaces/General_administrative_information/03_Tenant_Management_Console) and [System Management Console](https://knowledge.hitachivantara.com/Documents/Storage/Content_Platform/8.1.2/System_administration/HCP_administration/01_System_Management_Console), perform the following steps to set up HCP for queries from PDI:

1. In the Tenant Management Console at the tenant level, verify the following options are selected for you namespace:

   1. Under the **Protocols** tab, select **Enable REST API**.
   2. Under the **Settings** tab, select **Enable ACLs**.

   See [Enabling REST, S3 compatible, HSwift, and WebDAV access to namespace](https://knowledge.hitachivantara.com/Documents/Storage/Content_Platform/8.1.2/Tenants_and_Namespaces/Configuring_namespace_access_protocols/02_Configuring_the_REST%2C_S3_compatible%2C_HSwift%2C_and_WebDAV_APIs#Enabling_REST.2C_S3_compatible.2C_HSwift.2C_and_WebDAV_access_to_a_namespace) and [Enabling the use of ACLs](https://knowledge.hitachivantara.com/Documents/Storage/Content_Platform/8.1.2/Tenants_and_Namespaces/Managing_namespaces/04_Configuring_a_namespace#Enabling_the_use_of_ACLs) for more details.
2. In the System Management Console, go to the **Services** tab and verify that the following options for **MQE** (Metadata Query Engine) are selected:
   * **Enable metadata query API**
   * **Enable indexing**
   * **Enable indexing of custom metadata**\
     See [Configuring the metadata query engine](https://knowledge.hitachivantara.com/Documents/Storage/Content_Platform/8.1.2/System_administration/Search_administration/02_Metadata_query_engine#Configuring_the_metadata_query_engine) in the HCP documentation for more details.
3. In the Tenant Management Console on the level of your namespace, go to the **Services** tab, and verify that the following options for **Search** are selected:
   * **Enable search**
   * **Enable indexing**
   * **Enable indexing of custom metadata**
   * **Enable full custom metadata indexing**\
     See [Setting search and indexing options](https://knowledge.hitachivantara.com/Documents/Storage/Content_Platform/8.1.2/Tenants_and_Namespaces/Managing_search_and_indexing/10_Managing_search_and_indexing_for_an_individual_namespace#Setting_search_and_indexing_options) for more details.


---

# 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/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/query-hcp/before-you-begin.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.