> 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/legacy-redirects/hadoop-connection-info-redirects/additional-configurations-for-specific-distributions-legacy-pages/advanced-settings-for-connecting-to-cloudera-data-platform-archive/using-oozie-shared.md).

# Oozie configuration

If you use Oozie on your cluster, configure proxy access on the cluster and the server.

By default, the `oozie` user runs Oozie jobs.

If you start an Oozie job from PDI, configure a proxy user.

* [Set up Oozie on a cluster](#set-up-oozie-on-a-cluster)
* [Set up Oozie on the server](#set-up-oozie-on-the-server)

### Set up Oozie on a cluster

Add your PDI user to `oozie-site.xml`.

1. Open the `oozie-site.xml` file on the cluster.
2. Add the following properties.

   Replace `<your_pdi_user_name>` with your PDI user name. Example: `jdoe`.

   ```xml
   <property>
     <name>oozie.service.ProxyUserService.proxyuser.<your_pdi_user_name>.groups</name>
     <value>*</value>
   </property>
   <property>
     <name>oozie.service.ProxyUserService.proxyuser.<your_pdi_user_name>.hosts</name>
     <value>*</value>
   </property>
   ```
3. Save and close the file.

### Set up Oozie on the server

Add the proxy user name to the PDI named connection configuration.

1. Open the following file:

   `<username>/.pentaho/metastore/pentaho/NamedCluster/Configs/<connection_name>/config.properties`

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>This path and file are created when you create a named connection.</p></div>
2. Set `pentaho.oozie.proxy.user` to the proxy user name.
3. Save and close the file.

For more information about named connections, see the Pentaho Data Integration documentation.


---

# 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/legacy-redirects/hadoop-connection-info-redirects/additional-configurations-for-specific-distributions-legacy-pages/advanced-settings-for-connecting-to-cloudera-data-platform-archive/using-oozie-shared.md?ask=<question>&goal=<endgoal>
```

`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.