> 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/9.3-install/pentaho-upgrade-cp/post-upgrade-tasks-pentaho-ugrade-cp/setting-up-password-encryption-after-upgrading-pentaho-upgrade-cp/update-the-jackrabbit-repository-xml-file-post-upgrade-encryption-task.md).

# Update the Jackrabbit Repository XML file

The Jackrabbit component contains the solution repository, examples, security data, and content data from reports that you create in Pentaho. You must use the latest version of the `repository.xml` file if you plan to apply password encryption.

Perform the following steps to update the `repository.xml` file to use password encryption.

1. If you are using a database other than Postgres for your Pentaho Repository, perform the following substeps:
   1. Navigate to the `pentaho/server/pentaho-server/pentaho-solutions/system/jackrabbit` directory and open the `repository.xml` file with any file editor.
   2. Comment out any references to databases other than the database you are using for the Pentaho Repository in each of the following sections, and uncomment the sections that apply to your database:
      * Repository
      * DataStore
      * Workspaces
      * PersistenceManager (1st part)
      * Versioning
      * PersistenceManager (2nd part)
      * DatabaseJournal
   3. Save and close the `repository.xml` file.
2. If your `repository.xml` file contained any customizations before upgrading and you have not yet applied these customizations to the 9.3 version of the file, merge your customizations into the `repository.xml` file. See [Address customizations with post-upgrade versions](/install/9.3-install/pentaho-upgrade-cp/post-upgrade-tasks-pentaho-ugrade-cp/apply-customizations-post-upgrade-tasks/address-customizations-to-upgraded-archive-installation-post-upgrade-customization-task.md) for instructions.
3. [Stop and restart the server](/install/9.3-install/pentaho-configuration/tasks-to-be-performed-by-an-it-administrator/configure-the-pentaho-server/start-and-stop-the-pentaho-server-for-configuration.md) to confirm no errors occurred.

   Depending on the error, you may need to contact your customer support representative for help.


---

# 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/install/9.3-install/pentaho-upgrade-cp/post-upgrade-tasks-pentaho-ugrade-cp/setting-up-password-encryption-after-upgrading-pentaho-upgrade-cp/update-the-jackrabbit-repository-xml-file-post-upgrade-encryption-task.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.