2023.1:Grooper Infrastructure (Concept): Difference between revisions
Configadmin (talk | contribs) No edit summary |
Configadmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
What is Grooper? Grooper is a repository of information made up by a [https://en.wikipedia.org/wiki/Microsoft_SQL_Server SQL Server] Database and a Windows | What is Grooper? Grooper is a [https://en.wikipedia.org/wiki/Information_repository repository] of information made up by a [https://en.wikipedia.org/wiki/Microsoft_SQL_Server SQL Server] [https://en.wikipedia.org/wiki/Database Database] and a [https://en.wikipedia.org/wiki/Microsoft_Windows Windows] file share. This information is displayed to the user via an [https://en.wikipedia.org/wiki/Application_software application(s)] that displays a 1 to 1 relationship of what exists in that database and fileshare. Gaining an understanding of how to properly create using Grooper begins by first understanding the structure of its architecture, and why it is built the way it is. This sets a foundational groundwork for knowing how to think and interact with the application. | ||
==The Three Layers of Grooper== | ==The Three Layers of Grooper== | ||
Revision as of 13:07, 3 January 2020
What is Grooper? Grooper is a repository of information made up by a SQL Server Database and a Windows file share. This information is displayed to the user via an application(s) that displays a 1 to 1 relationship of what exists in that database and fileshare. Gaining an understanding of how to properly create using Grooper begins by first understanding the structure of its architecture, and why it is built the way it is. This sets a foundational groundwork for knowing how to think and interact with the application.
The Three Layers of Grooper
Grooper consists of three main components that constantly interact with one another:
- Database
- Filestore
- Application
The Database
This is the core component of Grooper as all aspects of the functionality and configuration of a Grooper repository are stored here as metadata in cells of tables. There are 13 tables that make up the Grooper database:
- AccessControlEntry
- CustomStats
- FileStoreEntry
- License
- LicenseCheckout
- Lock
- Log
- NodeReference
- ProcessingTask
- ServiceInstance
- SessionStats
The Application
This is the most visible aspect of Grooper as it is the software you interact with that displays the currently active repository. It consists of several pieces:
- Grooper Design Studio
- Grooper Config
- Grooper Attended Client
- Grooper Unattended Client
In discussing the overall picture of infrastructure, let’s focus on Grooper Design Studio for a moment, as it is the piece you will use most directly as you are developing processes. Every object in the Grooper node tree is an object, or row, in a specific table, the dbo.TreeNode table. The GUI of Grooper is essentially wrapping information from the Grooper database (again, this is a 1 to 1 relationship) into a series of grids and windows to allow you to directly interact with that database, and its related Windows fileshare, without writing SQL queries. It is also displaying and updating files that exist in the Grooper filestore that are associated with the objects you are interacting with. An example of this would be the extracted index data of a document, or the image displayed for a page.