> 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/extracting-data-into-pdi/work-with-the-streamlined-data-refinery/install-and-configure-the-streamlined-data-refinery/configure-ktr-files-for-your-environment.md).

# Configure KTR files for your environment

If you are not using Postgres and a default installation, you will need to configure a few of the sample KTR files in Spoon to use the SDR form.

1. Click **File** > **Open** and navigate to find the `SDR_data.ktr` in this directory: `pentaho/server/pentaho-server/pentaho-solutions/system/SDR/endpoints/kettle`.
   1. Right-click on the Set Local Variables step to edit, and enter the URL for your Pentaho Server.
   2. Click **OK**.
2. In the same transformation, right-click on the Call\_ML\_SDR job and select **Open Referenced Object** > **Job** to open the `_ML_SDR.job`.
   1. Right-click to edit the Create Table step to point to your staging database.
   2. Click **OK**.
3. Right-click to edit the Publish Model step and, if requested, enter your user id and password for the Pentaho Server.
   1. Click **Test Connection**.
   2. Click **OK**.
4. Open the `_ML_SDR_REFINERY.ktr`.
   1. Right-click to edit the Out to Staging DB step.
   2. Select your staging database from the drop-down menu.
5. Save all of these files and exit out of the PDI client.
6. Restart the Pentaho 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/pdia-data-integration/extracting-data-into-pdi/work-with-the-streamlined-data-refinery/install-and-configure-the-streamlined-data-refinery/configure-ktr-files-for-your-environment.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.