Repositories
The Qlik Sense Repository Service (QRS) manages persistence and synchronization of Qlik Sense apps, licensing, security, and service configuration data. The QRS attaches to a Qlik Sense Repository Database and is needed by all other Qlik Sense services to run and to serve Qlik Sense apps. The QRS also manages the synchronization in multi-node Qlik Sense sites. In addition, the QRS stores the Qlik Sense app structures and the paths to the binary files (that is, the app data stored in the local file system).
The Repositories overview lists all the available repositories. You can manage your repositories by performing a number of actions, as described in the following:
Name | The name of the repository. |
Status |
The Status column displays the status of the service. One of the following texts is displayed:
Tip noteClick in the Status column for more detailed information on the status. See Checking the status of Qlik Sense services.
|
Tags | The QMC tags that are connected to the proxy. |
Refreshing page: Click to manually refresh the page. | |
Sorting columns: Click to sort the list alphabetically, ascending or descending according to the nature of the column. |
|
Filtering columns: Click to open a dialog and filter the list based on that column and your filter criteria as you type. Click to remove the filter. Click outside of the filter dialog (or press the keyboard key "Esc") to close the dialog. The filter icon is inverted when a filter is applied to a column . You can apply filters to multiple columns to narrow your search. |
|
Edit | Editing repository: Click Edit in the action bar and edit the selected repository. |
Show more items |
Show more items: The overview shows a set number of items by default. To show more items, scroll to the end of the list and click Show more items. Sorting and filtering of items is always done on the full database list of items, not only the items that are on display. |
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!