> 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/pba-report-designer/9.3-report-designer/connect-report-designer-to-a-data-source-cp/add-a-jndi-data-source-connecting-to-a-data-source-in-prd.md).

# JNDI

You should already have established a JNDI data connection in your application server before continuing.

Follow this procedure to establish a connection to a JNDI data source.

1. Quit Report Designer if it is currently running.
2. Edit the `.pentaho/simple-jndi/default.properties` file.

   The `.pentaho` directory is in the home or user directory of the user account that runs Report Designer. If you have multiple copies of Report Designer installed to multiple user accounts, each `default.properties` file will have to be edited.
3. Add your JNDI connection information, beginning with the JNDI name on each line, as shown in the example below:

   ```
   SampleData/type=javax.sql.DataSource
   SampleData/driver=org.hsqldb.jdbcDriver
   SampleData/url=jdbc:hsqldb:hsql://localhost/sampledata
   SampleData/user=pentaho_user
   SampleData/password=password
   ```
4. Save and close the file, then start Report Designer.
5. To add this data source to a report, add a JDBC data source, choose **JNDI** as the connection type, and type in the JNDI name in the appropriate field.

Report Designer can now access your JNDI data sources.


---

# 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/pba-report-designer/9.3-report-designer/connect-report-designer-to-a-data-source-cp/add-a-jndi-data-source-connecting-to-a-data-source-in-prd.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.