> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/installation/install-central-manager-multi-store/manage-services/modify-settings/central-server-settings.md).

# Modify the Central Server settings

1. Double-click the **Central Server** icon on the desktop.
2. Click **Settings**.
3. On the **Database Connection** tab, modify the **Central SQL Server Instance**, **Database Name**, **User ID**, and **Password** as required.

<div align="left"><figure><img src="/files/eveSrOY1RpuLQKb1Zxf2" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
If you change the database, or if you add, remove, or deactivate a store, select **Check this option to recreate config file**. Central Server reads the config file for active store information. The config file is usually found under **C:\ProgramData\RetailHero\RMH Central Flash Server**.
{% endhint %}

4. On the **Server Services** tab, modify the **RMH Central Input Gateway** host name and port as required. The **RMH Central Input Gateway URL** is automatically set after you have successfully started the Central Server service. To change it:
   1. Select **Check this option to change this URL** and enter the host name and port for the computer where RMH Central Flash Server is installed.
   2. Click **Test Address** to verify the address.
   3. Click **Save**. The host name and port are saved to the Central Manager database. The Flash Bridge app will use this host name and port to send data packages/jobs to the Central Server to synchronize to stores.

<div align="left"><figure><img src="/files/1Piqqw3ihPzhuT9UlOx5" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
Enter a unique port number for each service. If you are using the Backward Compatibility Extension, ensure the port numbers used for the Flash-based Central Server app are different from the port numbers used for the non-Flash Central Server app. Refer to [Use the Backward Compatibility Extension](/installation/install-central-manager-multi-store/backward-compatibility.md) for more information.
{% endhint %}

5. On the **Setting Mode** tab, modify the following as required:

* **Delete the logs after:** Records are only kept in the log for the number of days indicated. After that, records are deleted from the log. The default number of days to keep records in the log is 7 days. The minimum number of days is 7 and the maximum is 90.
* **Retry attempts before declaring failure:** The maximum number of attempts that will be made to process a job before the system identifies a job as failed.
* **Retry interval between each attempt:** The time between retry attempts.
* **Delete failed jobs after failure:** Failed jobs are only kept for the number of days indicated. After that, failed jobs are deleted.

{% hint style="info" %}
Failed jobs are more common on the Central Server side, so the best practice is to select a longer retry interval and to keep failed jobs for 15 days before deleting them.
{% endhint %}

<div align="left"><figure><img src="/files/z8t0PAniW3SRC7hYb6N4" alt=""><figcaption></figcaption></figure></div>

6. Click **Save**.


---

# 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.rmhpos.com/installation/install-central-manager-multi-store/manage-services/modify-settings/central-server-settings.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.