> 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-client-settings.md).
# Modify the Central Client settings
This topic describes how to modify the Central Client settings, such as the connection to the SQL Server and store database, the Store Input Gateway, the Central Input Gateway, and more.
{% hint style="info" %}
Refer to [**Use the Consistency Checker**](/installation/install-central-manager-multi-store/manage-services/consistency-checker.md) for information about how to use the options on the Consistency Checker tab.
{% endhint %}
1. Double-click the **Central Client** icon on the desktop.
2. Click **Settings**.
3. On the **Database Connection** tab, modify the **Store SQL Server Instance**, **Database Name**, **User ID**, and **Password** as required.
{% hint style="info" %}
If you change the database, select **Check this option to recreate config file**. Central Client reads the config file for store database information. The config file is usually found under **C:\ProgramData\RetailHero\RMH Central Flash Client**.
{% endhint %}
4. On the **Client Services** tab, modify the **RMH Store \[number] Input Gateway** host name and port as required. The **RMH Store \[number] Input Gateway URL** is automatically set after a successful connection to Central Server. To change it:
1. Select **Check this option to change this URL** and enter the host name and port for the computer where Central Client is installed.
2. Click **Test Address** to verify the address.
3. Click **Save**. The host name and port are saved to the Store Manager database. The Flash Bridge app will use this host name and port to send data packages/jobs to the Central Client to synchronize to Central Server and Central Manager.
{% hint style="info" %}
Enter a unique port number for each service.
{% endhint %}
5. On the **Server Connection** tab:
* Check the **RMH Central Input Gateway** host name and port.
* (Optional) Enter the **Store Key** that you are using to authenticate the store to Central Manager.
{% hint style="warning" %}
If you choose to use Store Key for store authentication, you must first add the Store Key in Central Manager and then restart the Central Server services. Refer to [Add the store to Central Manager](/installation/install-central-manager-multi-store/installation-cm-configure-store.md) for more information. After you have confirmed that the Central Server services are running, you must add the Store Key in Central Client (this procedure) and restart Central Client services.
{% endhint %}
6. On the **Setting Mode** tab, modify the following as required:
* **Log init sync result:** Select to log the results of the initial synchronization between the store's database and the Central database.
* **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.
7. 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.rmhpos.com/installation/install-central-manager-multi-store/manage-services/modify-settings/central-client-settings.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
