> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/platform-administration/snyk-broker/classic-broker/install-and-configure-snyk-broker/nexus-repository-prerequisites-and-steps-to-install-and-configure-broker.md).

# Nexus Repository - prerequisites and steps to install and configure Broker

Prerequisites and steps to install and configure Snyk Broker for Nexus Repository Manager, on Enterprise plans

{% hint style="info" %}
**Feature availability**

Integration with Nexus Repository Manager is available only with Enterprise plans. For more information, see [plans and pricing](https://snyk.io/plans/).
{% endhint %}

Before installing, review the general instructions for the installation method you plan to use, [Helm](/platform-administration/snyk-broker/classic-broker/install-and-configure-snyk-broker/install-and-configure-broker-using-helm.md) or [Docker](/platform-administration/snyk-broker/classic-broker/install-and-configure-snyk-broker/install-and-configure-broker-using-docker.md).

Before installing the Snyk Nexus Repository Broker, ask your Snyk account team for a Broker token, or generate one by following the steps in [Obtain Broker token for Nexus integration](#obtain-broker-token-for-nexus-integration).

You must have Docker or another way to run Linux containers.\
Some Docker deployments for Windows run only Windows containers. Ensure that your deployment can run Linux containers.

If you are installing Classic Broker, use the [Docker](/platform-administration/snyk-broker/classic-broker/install-and-configure-snyk-broker/nexus-repository-prerequisites-and-steps-to-install-and-configure-broker/nexus-repository-install-and-configure-using-docker.md) or [Helm](/platform-administration/snyk-broker/classic-broker/install-and-configure-snyk-broker/nexus-repository-prerequisites-and-steps-to-install-and-configure-broker/nexus-repository-install-and-configure-using-helm.md) instructions to obtain a token.\
If you are installing Universal Broker, skip the token steps and follow the Universal Broker setup instructions instead. 

## Obtain Broker token for Nexus integration

The environment variable configuration in this section also applies to Universal Broker. When you configure Nexus using a Broker (Classic or Universal), you manage all configuration through Broker environment variables. The Snyk Web UI does not display Nexus settings under **Languages** or **Brokered package registries**.

If you are installing Universal Broker, enter your Nexus Base URL in this format when prompted: `https://username:password@your.nexus.hostname.`

1. Navigate to **Settings** > **Integrations** > **Package Repositories** > **Nexus**.
2. Ensure that the Nexus configuration screen is visible. If the Snyk Broker switch is missing, you do not have the necessary permissions and can only add a publicly accessible instance. Contact [Snyk Support](https://support.snyk.io) to request access to add a private registry.
3. Move the Snyk Broker switch to **On** to display the Broker token generation form.
4. Select **Generate and Save**.
5. Copy the generated token to use when you set up the Broker Client.


---

# 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.snyk.io/platform-administration/snyk-broker/classic-broker/install-and-configure-snyk-broker/nexus-repository-prerequisites-and-steps-to-install-and-configure-broker.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.