Grooper Infrastructure (Concept) - Revision history

Dgreenwood: Redirected page to Grooper Infrastructure

2026-01-08T17:29:40Z

Redirected page to Grooper Infrastructure

Dgreenwood at 18:17, 14 August 2025

2025-08-14T18:17:25Z

← Older revision		Revision as of 13:17, 14 August 2025
Line 60:		Line 60:
	⚠		⚠
	\|		\|
	Be aware. We do not recommend using SQL as a Service (SQLaaS) solutions to ~~sand~~ up the Grooper Database for most scenarios. Please refer to our [[#Cloud Deployment Guidance\|Cloud Deployment Guidance]] below for more information.		Be aware. We do not recommend using SQL as a Service (SQLaaS) solutions to stand up the Grooper Database for most scenarios. Please refer to our [[#Cloud Deployment Guidance\|Cloud Deployment Guidance]] below for more information.
	\|}		\|}

Dgreenwood: /* dbo.Query */

2025-07-31T19:56:52Z

dbo.Query

← Older revision		Revision as of 14:56, 31 July 2025
Line 732:		Line 732:
	\|}		\|}

	=== dbo.Query ===		==== dbo.Query ====

	This table stores saved queries that can be executed from the Search page.		This table stores saved queries that can be executed from the Search page.

Dgreenwood: /* Grooper's Core and Supporting Architecture */

2025-07-23T18:28:40Z

Grooper's Core and Supporting Architecture

← Older revision		Revision as of 13:28, 23 July 2025
Line 772:		Line 772:
	Although the majority of files in the File Store relate to Batch objects (a page's image or imported files), some files are the result of other "in-Grooper" processes, such as layout data, OCR character data, extracted index data, and more.		Although the majority of files in the File Store relate to Batch objects (a page's image or imported files), some files are the result of other "in-Grooper" processes, such as layout data, OCR character data, extracted index data, and more.

	== Grooper's Core and Supporting Architecture ==		== Diagram: Grooper's Core and Supporting Architecture ==

	There are several components that make up a Grooper system's internal infrastructure: the Grooper database, the Grooper file store, the Grooper web server, etc. There are also several external resources Grooper connects to. This includes import and export sources and LLM (large language model) providers used in Grooper's AI-based features.		There are several components that make up a Grooper system's internal infrastructure: the Grooper database, the Grooper file store, the Grooper web server, etc. There are also several external resources Grooper connects to. This includes import and export sources and LLM (large language model) providers used in Grooper's AI-based features.

Dgreenwood: /* The Database */

2025-07-23T18:04:30Z

The Database

@@ Line 292: / Line 292: @@
 The Grooper Repository's database (aka "Grooper Database") is the core component of Grooper. All aspects of Grooper configuration are stored has metadata in the Grooper Database's tables. The processing status of Batches and their tasks are stored in the Grooper Database. Statistical information and logs are stored in the Grooper Database. There is no Grooper without the Grooper Database.
-There are 15 tables (as of Grooper version 2024) that make up the Grooper Database:
+There are 18 tables (as of Grooper version 2024) that make up the Grooper Database:
 ''Please note the Grooper database tables are not listed here in alphabetical order. They are listed in terms of how impactful they are to Grooper's overall architecture.''
@@ Line 675: / Line 675: @@
 |-
 | Value || varchar || 1024 || Current installed Grooper version
 |}

Dgreenwood: /* dbo.Log */

2025-07-23T17:09:36Z

dbo.Log

← Older revision		Revision as of 12:09, 23 July 2025
Line 640:		Line 640:

	==== dbo.Log ====		==== dbo.Log ====
	* This table contains the Grooper log, which is represented in Grooper's "Event Viewer".		This table contains the Grooper log, which is represented in Grooper's "Event Viewer".
	:: {\| class="wikitable"		:: {\| class="wikitable"
	! Column Name !! Data Type !! Size !! Description		! Column Name !! Data Type !! Size !! Description

Dgreenwood at 17:09, 23 July 2025

2025-07-23T17:09:12Z

← Older revision		Revision as of 12:09, 23 July 2025
Line 691:		Line 691:

	Although the majority of files in the File Store relate to Batch objects (a page's image or imported files), some files are the result of other "in-Grooper" processes, such as layout data, OCR character data, extracted index data, and more.		Although the majority of files in the File Store relate to Batch objects (a page's image or imported files), some files are the result of other "in-Grooper" processes, such as layout data, OCR character data, extracted index data, and more.

			== Grooper's Core and Supporting Architecture ==

			There are several components that make up a Grooper system's internal infrastructure: the Grooper database, the Grooper file store, the Grooper web server, etc. There are also several external resources Grooper connects to. This includes import and export sources and LLM (large language model) providers used in Grooper's AI-based features.

			This diagram seeks to illustrate these resources.

			[[File:2025Wiki Grooper-Infrastructure core-and-supporting-architecture.png]]

Dgreenwood: /* Grooper's Core and Supporting Architecture */

2025-07-23T17:08:56Z

Grooper's Core and Supporting Architecture

← Older revision		Revision as of 12:08, 23 July 2025
Line 231:		Line 231:
	:Microsoft Access Database Engine contains essential components that make it possible for Microsoft Office programs to interact with software services and applications that do not belong to Microsoft. For instance, if you are working in a program that gives you the possibility to export tables directly to Microsoft Access, then you need the database engine to make that happen.		:Microsoft Access Database Engine contains essential components that make it possible for Microsoft Office programs to interact with software services and applications that do not belong to Microsoft. For instance, if you are working in a program that gives you the possibility to export tables directly to Microsoft Access, then you need the database engine to make that happen.
	:The Microsoft Access Database Engine is available in multiple editions, which mainly depend on which Microsoft Office product you’re using. The hint is in the year. As such, if you use Microsoft Office 2016, then you need Microsoft Access Database Engine 2016.		:The Microsoft Access Database Engine is available in multiple editions, which mainly depend on which Microsoft Office product you’re using. The hint is in the year. As such, if you use Microsoft Office 2016, then you need Microsoft Access Database Engine 2016.

	~~== Grooper's Core and Supporting Architecture ==~~

	There are several components that make up a Grooper system's internal infrastructure: the Grooper database, the Grooper file store, the Grooper web server, etc. There are also several external resources Grooper connects to. This includes import and export sources and LLM (large language model) providers used in Grooper's AI-based features.

	~~This diagram seeks to illustrate these resources.~~

	~~[[File:2025Wiki Grooper-Infrastructure core-and-supporting-architecture.png]]~~

	== About thread allocation for Grooper services ==		== About thread allocation for Grooper services ==

Dgreenwood: /* System Architecture and Requirements */

2025-07-23T17:08:35Z

System Architecture and Requirements

← Older revision		Revision as of 12:08, 23 July 2025
Line 231:		Line 231:
	:Microsoft Access Database Engine contains essential components that make it possible for Microsoft Office programs to interact with software services and applications that do not belong to Microsoft. For instance, if you are working in a program that gives you the possibility to export tables directly to Microsoft Access, then you need the database engine to make that happen.		:Microsoft Access Database Engine contains essential components that make it possible for Microsoft Office programs to interact with software services and applications that do not belong to Microsoft. For instance, if you are working in a program that gives you the possibility to export tables directly to Microsoft Access, then you need the database engine to make that happen.
	:The Microsoft Access Database Engine is available in multiple editions, which mainly depend on which Microsoft Office product you’re using. The hint is in the year. As such, if you use Microsoft Office 2016, then you need Microsoft Access Database Engine 2016.		:The Microsoft Access Database Engine is available in multiple editions, which mainly depend on which Microsoft Office product you’re using. The hint is in the year. As such, if you use Microsoft Office 2016, then you need Microsoft Access Database Engine 2016.

			== Grooper's Core and Supporting Architecture ==

			There are several components that make up a Grooper system's internal infrastructure: the Grooper database, the Grooper file store, the Grooper web server, etc. There are also several external resources Grooper connects to. This includes import and export sources and LLM (large language model) providers used in Grooper's AI-based features.

			This diagram seeks to illustrate these resources.

			[[File:2025Wiki Grooper-Infrastructure core-and-supporting-architecture.png]]

	== About thread allocation for Grooper services ==		== About thread allocation for Grooper services ==

Dgreenwood at 16:59, 23 July 2025

2025-07-23T16:59:54Z

Show changes