---
title: "Connecting a Decisions Server to a Repository Server"
slug: "connecting-a-decisions-server-to-a-repository-server"
description: "This document shows how to to properly connect a Decisions Server to a Repository Server. Proper communication via IP or DNS, MUST be setup for Decisions to utilize the repository. "
updated: 2025-09-16T14:38:15Z
published: 2025-09-16T14:38:15Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting a Decisions Server to a Repository Server

## Overview

This document demonstrates how administrators can connect a Decisions Server (Development/QA/Production Environment) to a Repository Server. To learn more about the Repository server, refer to the [Repository Overview](https://documentation.decisions.com/v9/docs/repository-overview) article. In order to get the Decisions Server to access the Repository, the Servers must be able to communicate via **IP**or **DNS**.

Prerequisites:

- Already installed Repository Server. Refer to the [Repository Installation](https://documentation.decisions.com/v9/docs/repository-installation) article.
- Copy the Repository Server's [Portal Base URL](https://documentation.decisions.com/v9/docs/system-settings-overview-settings-xml?highlight=PortalBaseUrlhttp://localhost:80Prompts%20for%20URL%20to%20the%20Portal.%20This%20is%20typically%20defined%20during%20installation.) for future reference.

### ---

## Connect to Repository Server

After meeting all the prerequisites listed under the overview section, the following subsection explains how to connect Decisions with the Repository server.

Saving these settings will connect the Decisions environment to a Repository Server. 

1. In the environment you want to connect to the repository, navigate to **System > Settings > Designer Repository Settings**. The **Repository Settings** dialog box appears.
2. Under **Repository Server**, paste the Repository Server's**Portal Base****URL**.Example: Ensure the URL includes the instance name "`/Primary`" at the end of the base URL ({PortalBaseUrl}/Primary). Refer to the following example screenshot: `http://repo:[port#]/Primary`.
3. Enable **Show Repository Actions**under the ****Advanced****section. This will expose all the entities to the Designer Repository actions. These actions can be found by [right-clicking](https://documentation.decisions.com/v9/docs/repository-overview?highlight=Once%20a%20repository%20environment%20is%20connected) any designer entity.
4. Click **SAVE****SETTINGS**. To learn more about all the settings, refer to the [Repository Settings](https://documentation.decisions.com/v9/docs/repository-settings) document. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1741807274996.png)

---

## Validating the Connection

Validating ensures that the configuration you have set up for the servers is correct and that the servers communicate with each other as intended. This confirmation can help prevent any issues from arising later due to incorrect configuration settings.

To validate the connection to a repository server, follow these steps:

1. From the current Decisions server (where the Repository is configured), navigate to any Folder/Designer Folder.
2. On the left panel, you will see the name of the Folder/Designer Folder (e.g., Documentation Project). Under that are two icons: one for **Check-in/Commit Changes** and the other for **Checkout**. The same options can be accessed by clicking the vertical ellipsis (represented as "⋮").  
![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1741805287920.png)
3. To validate the connection, click on Check-in/Commit Changes. A popup will appear, prompting you to enter your username and password for the configured Designer Repository. After entering your credentials and clicking OK, if the Commit Changes window appears, this confirms a successful connection to the repository server.  
![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1741805572623.png)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1741805503263.png)

---

## Common Troubleshooting Points

1. Ensure the Repository Server URL entered is correct in the [Designer Repository Settings](/v9/docs/connecting-a-decisions-server-to-a-repository-server#steps-to-connect-to-repository-server)
2. Ensure the Repository Server is reachable and actively running. If the server is unreachable, please contact your IT administrator.
3. Ensure to use `HTTPS` in the URL in the [Designer Repository Settings](/v9/docs/connecting-a-decisions-server-to-a-repository-server#steps-to-connect-to-repository-server) if the repository server is configured with a secured connection.
4. Check [Event Viewer](https://documentation.decisions.com/v9/docs/system-tools-event-viewer) for any possible logs related to Repository. If unmanaged to resolve the issue, reach out to [support@decisions.com](mailto:support@decisions.com).

Refer to the following article for [Troubleshooting Repository](https://documentation.decisions.com/v9/docs/repository-faq). If the problem continues, please reach out to [support@decisions.com](mailto:support@decisions.com).

---

For further information on Repository, visit the [Decisions Forum](https://community.decisions.com/categories/Repository).
