> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ras-multi-tenant-architecture/deploying-tenant-broker-and-tenants.md).

# Deploying Tenant Broker and Tenants

A typical scenario of deploying the multi-tenant architecture of Parallels RAS consists of the following steps:

1. Deploy Tenant Broker.
2. Deploy a traditional RAS Farm to operate as a Tenant.
3. Configure network between the Tenant Broker and the Tenant to allow the following connections:

   * Shared RAS Secure Gateways to Tenant RAS Connection Brokers.
   * Shared RAS Secure Gateways to resources hosts.
   * Tenant RAS Connection Brokers to Tenant Broker RAS Connection Broker.

   For the information about ports numbers, please see [**Communication ports**](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ras-multi-tenant-architecture/communication-ports.md).
4. Create a Tenant object and a corresponding invitations hash in the Tenant Broker console, or create a secret key (more on this later in this chapter).
5. Join the Tenant to the Tenant Broker using the invitation hash or the secret key.
6. Assign a public domain address to the Tenant. This can be done at this point (after you join a Tenant) or it can be done in advance if you wish. Either way it has to be done or the clients will not be able to connect to the Tenant Farm.
7. Set up routing for incoming Tenant traffic from the Internet to shared RAS Secure Gateways and HALB.
8. Configure a certificate for the Tenant. By default, a self-signed certificate created during the installation will be used.
9. Test the client connectivity.

The subsequent sections describe the steps above in detail.


---

# 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.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ras-multi-tenant-architecture/deploying-tenant-broker-and-tenants.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.