Grooper Repository (Concept)

STUB	This article is a stub. It contains minimal information on the topic and should be expanded.

A Grooper Repository is the environment used to create, configure and execute objects in Grooper. It provides the framework to "do work" in Grooper. Fundamentally, a Grooper Repository is a connection to a database and file store location, which store the node configurations and their associated file content. The Grooper application interacts with the Grooper Repository to automate tasks and provide the Grooper user interface.

This environment consists of:

1. a database connection and
2. a file store location.  

The database stores Grooper nodes and their property settings (such as a Content Model or a Data Type or any other Grooper object). The file store location houses content associated with these nodes (such as the image file for a Batch Page object).

FYI

Creating (or connecting to) a Grooper Repository is one of the first things you will do after installing Grooper to start designing (or implementing already architected) document processing solutions. For more information on how to create or connect to a Grooper Repository, visit the Install and Setup and/or Grooper Config articles.