The Concrii® user interface
The user interface gives full access to the search capabilites of Concrii and allows to do test runs and optimizations on searches as well as editing the Concrii configuration.
General
On the very right bottom of the Concrii GUI screen, the logged-in User is displayed with a link to the User Details page. The logout link logs out the user (not displayed if user has logged in via certificate).
On successful login, the Welcome page will be displayed (if not, the page has been requested in the browser URL).
Configuration Page
On the Configuration Page (ConfigurationRead policy needed; more information can be found here) all available configuration files are displayed. Use show / hide links to show / open the appropriate contents. If the logged-in User owns the policy ConfigurationWrite, he / she can save changes. The saved contents will be checked for valid json format only.
Status Page
On the Status Page, the status of all indexes, columns and tables will be displayed (StatusRead policy needed; more information can be found here). Use show / hide links to show / open the appropriate contents. Statuses will be updated by the system only and cannot be changed manually.
Friends Page
On the Friends Page, all configured Friend instances and their indexes are listed (FriendsRead policy needed).
Columns:
| Name | Description |
|---|---|
| Id | Unique Id of Concrii instance. |
| Online: true / false | Only Friends that are online will be used to share workload. |
| Configuration | Endpoint of Friend. |
| Indexes | List of all available Friends. |
Indexes Page
The Indexes Page lists all configured indexes (IndexesRead policy needed; more information can be found here).
Find out more about Index configuration.
Settings:
| Name | Description |
|---|---|
| Forward actions to friends | If checked (default: off), all index actions (create and erase) will be forwarded to friends, too. This happens regarding the friends forward configuration. |
Warning
All forwarded actions will be done on all friends in parallel (friends forward 'Parallel' configuration is not evaluated!). Thus, this option should be used wisely because if e.g. a recreation of an index is done in parallel (simultaneously) on all friends, no index will be available for search forsome time. In contrast to UI, the api will evaluate the 'Parallel' settings within friends configuration to detect if forward request are done parallel or not.
Columns:
| Name | Description |
|---|---|
| Id | Unique Id of the index. |
| Health | "Well" or "Bad", depending whether errors have been deteted during crea/update/erase processes or not. "Bad" in general means, the is unexpectedly no more created or erased (see Created) or the data is out of date because of erros during update. |
| Friends | On / Off / Prioritize. Use online friends, or not, or prioritize them. |
| Created | true / false. Is the index available (created) or not? |
| Information | Information (string) about the last activity that happened. |
| Size | Number of entries / rows of the index. |
| Details | Encryption value status / Encryption Ids status. |
| CreateOnStart|Schedule | true/false if index is created during startup of Concrii service | Configured crontab expression indicating when the index will be recreated (full). |
| WhenCreated | Date / time of index creation. |
| WhenUpdated | Date / time of last index update. |
Actions
Warning
As index creation should be always configured within productive environments and with automation (CreateOnStart or schedule), all actions should only be used on the development environments to test indexes and their performance / behaviour.
| Action | Description |
|---|---|
| [eraseindex] | Erase / empty index. After erasure, the index is still configured and available for creation, but not available for any searches. (IndexErase policy needed). |
| [createindex] | Create / fill index. When creation is finished, the index is available for any searches (IndexCreate policy needed). |
| [recreate] | Recreate (overwrite) / fill index. Visible when index is created already. (IndexCreate policy needed). |
| [reload] | Reload index status (current line in the list of indexes). Most actions run asynchronous and do not directly report status back to the page, but to its status. To refresh this information, reloading the whole page or action is required. |
| [canceloperation] | When a process is running (mostly creation of indexes) it can be cancelled with this action (IndexCancelOperation policy needed). As the processes run asynchronous, this can take some seconds. |
System Page
The GUI System page displays system information and actions depending on the Concrii service and is not related to the seach funcionality of Concrii.
When running Concrii in the console, you can restart the application from this page. This is not possible when Concrii is running as windows service.
Dianostics Page
On the Diagnostics Page, number of garbage collection are displayed and some basic system counters (cpu, allocated memory).
| Action | Description |
|---|---|
| [force garbage collection] | Force garbage collection to run. (DiagnosticsForceGarbageCollection policy needed). |
Warning
Run of garbage collection needs resources on the server and must therefore used wisely within productive environments. This action here is just to test functionality, for expert setup on garbage collection refer to GC