> 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/10.2-install/pentaho-configuration/tasks-to-be-performed-by-an-it-administrator/configure-the-pentaho-server/specify-data-connections-for-the-pentaho-server/jdbc-database-connections/set-up-jndi-connections-for-the-pentaho-server.md). # Set up JNDI connections for the Pentaho Server If you installed the Pentaho Server using the manual installation method, then you specified data connections to the [Tomcat](http://tomcat.apache.org/) web application server. To modify existing connections or define more JNDI connections, perform the following set of instructions. You must be an IT administrator, know where data you are managing is stored, how to connect to the data, details about the computing environment, and how to use the command line to issue commands for Microsoft Windows or Linux. You should also know how to install a database and a web application server. ## Defining JNDI connections for PDI clients If you are publishing to the Pentaho Server from a PDI client, Pentaho supplies a method for you to configure your PDI client to have the same JNDI connection information as the Pentaho Server. By using this method, your application server will not be continuously running during the development and testing of transformations. * To configure a JNDI connection for your PDI client, edit the `jdbc.properties` file to mirror the JNDI connection information of your application server data sources. The `jdbc.properties` file is located here: `/pentaho/design-tools/data-integration/simple-jndi`. ## Tomcat JNDI connections If you installed the Pentaho Server using the manual installation method, then you specified data connections to your Tomcat web application server. If you want to modify existing connections or add more connections, perform the following tasks. Database connection and network information, such as the username, \ password, driver class information, IP address or domain name, and port \ numbers for your Pentaho Repository database are stored in the context.xml \ file. Modify this file to reflect the database connection and network information to reflect your operating environment. You also modify the values for the \ validationQuery parameters in this file if you have chosen to use a Pentaho \ Repository database other than PostgreSQL. #### Procedure 1. Stop the Tomcat and Pentaho Servers. For instructions on starting the server, see [Stop and start the Pentaho Server and repository](/install/10.2-install/pentaho-configuration/tasks-to-be-performed-by-an-it-administrator/configure-the-pentaho-server/stop-and-start-the-pentaho-server-and-repository.md). 2. Consult your database documentation to determine the class name and connection string for your database. 3. Edit the `/tomcat/webapps/pentaho/WEB-INF/web.xml` file. 4. At the end of the element, in the same part of the file where you see ``, add the following XML snippet: ```shellscript myDataSource jdbc/myDataSource javax.sql.DataSource Container ``` Change the `description` and `res-ref-name` nodes, as well as any others that apply to your situation and fit your database. You may need to consult the **JNDI Resources** article in the [Apache Tomcat documentation](https://tomcat.apache.org/) to see if there are other components to consider. 5. Save and close the `web.xml` file. 6. Edit the `/tomcat/conf/context.xml` with a text editor. Alternatively, you can modify the `/tomcat/webapps/pentaho/META-INF/context.xml` file if you want this data connection to be available only to the Pentaho Server. Adding JNDI connections to the `context.xml` makes them available to all of the webapps deployed to this Tomcat instance. 7. Anywhere inside of the `Context` element, add the following XML snippet: 
<Resource name="jdbc/myDataSource"
       auth="Container" type="javax.sql.DataSource"
       factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
       maxActive="20"
       maxIdle="5"
       maxWait="10000"
       username="dbuser"
       password="password"
       driverClassName="org.postgresql.Driver"
       url="jdbc:postgresql://127.0.0.1:5432/myDataSource"
   />
8. The example above shows a simple PostgreSQL configuration. Replace the `Resource name`, `username`, `password`, `driverClassName`, and `url` parameters, or any relevant connection settings, to match your database connection information and the details you supplied in the `web.xml` file earlier. 9. Save and close the `context.xml` file. 10. Delete the `pentaho.xml` file located in the `/tomcat/conf/catalina/` directory. The `pentaho.xml` is a cached copy of the `context.xml` file you modified. Since the cache is not usually configured to update frequently, you have to delete the `pentaho.xml` file and let Tomcat recreate it when it starts up. 11. Start the Tomcat and Pentaho servers. **Result:** Tomcat can now properly connect to your data. ### Add drivers The Pentaho Server needs the appropriate driver to connect to the database that stores your data. Your database administrator, Chief Intelligence Officer, or IT manager should be able to provide the appropriate driver. If not, you can download drivers from your database vendor's website. The [Components Reference](/install/10.2-install/components-reference.md) contains a list of drivers. Once you have the correct driver, copy it to the following directories: * Pentaho Server: `/pentaho/server/pentaho-server/tomcat/lib/` * PDI client: `data-integration/lib` You must restart PDI client for the driver to take effect. There should be only one driver for your database in the directory. Ensure that there are no other versions of the same vendor's driver in this directory. If there are, back up the old driver files and remove them to avoid version conflicts. This is a concern when you are adding a driver for the same database type as your Pentaho Repository. If you have any concerns about how to proceed, contact [Pentaho Support](https://support.pentaho.com/). #### Driver for Microsoft SQL Server If you are using a Microsoft SQL Server (MSSQL), you might need to use an alternative, nonvendor-supported driver called JTDS. Contact [Pentaho Support](https://support.pentaho.com/) to ensure that you are adding the correct driver. For Microsoft Windows, most JDBC drivers support Type 2 integrated authentication through \ the integratedSecurity connection string property. To use integrated authentication, \ copy the sqljdbc\_auth.dll file to all machines and directories to which you copied the \ JDBC driver. You can find this file in this location: `\sqljdbc_\\auth\`
If running:Use the sqljdbc_auth.dll file here:
64-bit JVM on a x64 processorx64 folder
64-bit JVM on an Itanium processorIA64 folder
--- # 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/install/10.2-install/pentaho-configuration/tasks-to-be-performed-by-an-it-administrator/configure-the-pentaho-server/specify-data-connections-for-the-pentaho-server/jdbc-database-connections/set-up-jndi-connections-for-the-pentaho-server.md?ask=&goal= ``` `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.