2023:Install and Setup: Difference between revisions
No edit summary |
No edit summary |
||
| Line 511: | Line 511: | ||
|} | |} | ||
</tab> | </tab> | ||
<tab name="Create a New Grooper Repository" style="margin:20px"> | |||
=== Create a New Grooper Repository === | |||
{|cellpadding=10 cellspacing=5 | |||
|valign=top style="width:40%"| | |||
Now that Grooper is initialized, we have a file store location, and we have an available SQL environment (either a full install of SQL Server or SQL Express) we can create a new Grooper Repository. | |||
Connecting to a Grooper Repository is the first thing you will do in Grooper Config. If you're not connecting to an existing Grooper Repository set up on someone else's Grooper installation, you'll need to create one. | |||
# Select the '''''Repositories''''' property in Grooper Config. | |||
# Click the ellipsis button at the end. | |||
This will open up a new window to add Grooper Repository connections. | |||
|valign=top| | |||
[[File:2023-Install and Setup-New Repository 01.png]] | |||
|- | |||
|valign=top| | |||
#<li value=3> Click the "Add" button to add a new connection. | |||
|valign=top| | |||
[[File:2023-Install and Setup-New Repository 02.png]] | |||
|- | |||
|valign=top| | |||
The first part of creating a new Grooper Repository is establishing the database connection. | |||
#<li value=4> Select the '''''Server Name''''' property and enter the server's name running the SQL environment. | |||
#* FYI: For SQL Express installs, the server instance will be the machine's name followed by <code>\GROOPER</code> as seen here. | |||
#* For standard SQL Server installs, simply enter the server machine's name. | |||
# Select the '''''Database Name''''' property and enter a name for the database. | |||
#* Here, we chose to name it ''okcstrpa01_001'' after the server name. Name the database whatever you would like. | |||
# Click the "Test Connection" button. | |||
| | |||
[[File:2023-Install and Setup-New Repository 03.png]] | |||
|- | |||
|valign=top| | |||
#<li value=7> Since we are creating a new Grooper Repository, the database has not been created yet. A dialog box will appear informing you the database does not exist and asking you if you want to create it. | |||
# Click "Yes" to create the database. | |||
|valign=top| | |||
[[File:2023-Install and Setup-New Repository 04.png]] | |||
|- | |||
|valign=top| | |||
{|cellpadding="10" cellspacing="5" style="margin:12px" | |||
|- | |||
|style="font-size:125%; background-color:#36b0a7; color:white; width:28px; text-align:center"|'''FYI''' | |||
|style="border: 4px solid #36b0a7"| | |||
By default, Grooper will use your Windows login authentication to access the SQL environment. However, if you need to access the SQL environment with different rights (for example a SQL admin login), you can do so using the '''''Authentication''''' properties. | |||
|} | |||
|valign=top| | |||
[[File:2023-Install and Setup-New Repository 05.png]] | |||
|- | |||
|valign=top| | |||
#<li value=9> Upon creating the database, you will get a message letting you know the database has not been initialized. | |||
# Press "Ok" to continue. | |||
| | |||
[[File:2023-Install and Setup-New Repository 06.png]] | |||
|- | |||
|valign=top| | |||
#<li value=11> Press the "Initialize" button. | |||
| | |||
[[File:2023-Install and Setup-New Repository 07.png]] | |||
|- | |||
|valign=top| | |||
Remember, a Grooper Repository is two things: | |||
# A database connection | |||
# '''A file store connection''' | |||
Initializing the Grooper Repository connects the repository to the file store location and establishes the folder structure Grooper uses to store files. | |||
#<li value=12> Select the '''''Storage Path''''' property and enter the file path for the file store's folder. | |||
# Press the "Execute" button to initialize the Grooper Repository. | |||
{|cellpadding="10" cellspacing="5" style="margin:12px" | |||
|- | |||
|style="font-size:250%; background-color:#f89420; color:white; width:28px; text-align:center"|⚠ | |||
|style="border: 4px solid #f89420"| | |||
While you ''can'' use the ellipsis button to navigate to a local file store location, it is ill-advised. Please use a fully qualified UNC path for your Grooper files store location. | |||
|} | |||
{|cellpadding="10" cellspacing="5" style="margin:12px" | |||
|- | |||
|style="font-size:125%; background-color:#36b0a7; color:white; width:28px; text-align:center"|'''FYI''' | |||
|style="border: 4px solid #36b0a7"| | |||
You may also name the Grooper Repository using the '''''Repository Name''''' property. We named ours ''okcstrpa01_001''. | |||
But don't worry if you don't name it at this time. You may rename your Grooper Repository at any time after it is initialized. Once initialized, you can select the Grooper Repository from the Repositories list and press the "Rename" button to rename it. | |||
|} | |||
|valign=top| | |||
[[File:2023-Install and Setup-New Repository 08.png]] | |||
|- | |||
|valign=top| | |||
#<li value=14> Upon successful initialization, you will receive this confirmation window. | |||
# Click the "Ok" button to continue. | |||
# Click the "Ok" button to finish. | |||
| | |||
[[File:2023-Install and Setup-New Repository 09.png]] | |||
|- | |||
|valign=top| | |||
This will return you to the main Grooper Config window. | |||
#<li value=17> Press the "Save" button to finalize your Grooper Repository connection. | |||
|valign=top| | |||
[[File:2023-Install and Setup-New Repository 10.png]] | |||
|- | |||
|valign=top| | |||
After licensing your Grooper installation, you will be able to access the Grooper Repository in Grooper Design Studio. | |||
The Grooper Repository forms the root node of the Node Tree when the repository is selected in Grooper Design Studio. | |||
| | |||
[[File:2022-create-new-grooper-repo-19.png]] | |||
|} | |||
</tab> | |||
</tabs> | </tabs> | ||
Revision as of 16:34, 3 March 2023
| WIP |
This article is a work-in-progress or created as a placeholder for testing purposes. This article is subject to change and/or expansion. It may be incomplete, inaccurate, or stop abruptly. This tag will be removed upon draft completion. |
Welcome to Grooper 2023!
This guide will instruct you how to get up and running in Grooper.
This article also provides guidance for Upgrading an Older Version of Grooper.
About
Thank you for purchasing/upgrading to Grooper 2023!
Before we go over the installation and setup of Grooper 2023, let us explain some of the new features 2023 has to offer.
In previous versions of Grooper, you had to install the software on each computer you wanted to have access to any part of Grooper. So, no matter if they were designing your Grooper environment or reviewing documents, Grooper had to be fully installed on their computers. Everyone would then have to access a server where the Grooper repositories are stored or create a local repository on their machine. This could cause some difficulties in customizing permissions and managing the software on multiple computers.
With Grooper 2023, the software only has to be fully installed on one computer! Instead, everyone else can access the Grooper environment and repositories via web browser. This makes everything a lot easier to manage.
Installing the Grooper Product Suite
To get up and running with Grooper 2023, there are several applications that need to be installed and configured.
- Grooper: This primary application installs the Grooper thick client and Grooper Config.
- Internet Information Services (IIS): This program is necessary to use the Grooper Web Client.
- Web Client: With this application properly installed and configured, multiple users can access Grooper remotely via web browser.
- Grooper Desktop: This application can be installed on any computer. Grooper Desktop integrates with scanners
Download the Installer
|
If you have not registered at Grooper xChange, do so by clicking the link below. Once you've registered, you will have access to the user forum, including the "Downloads and Resources" section. Follow the link below to the "Download and Resources" section. The top level topic will have download links to the most recent version of Grooper. Links to older versions are available lower in the list of topics. |
|
|
Click on the link for Grooper 2023. Here you will see four links to downloads: The 64-bit installer, the 32-bit installer, Grooper Desktop Installer, and Grooper Web Server Installer. You will need to choose between the 64-bit installer and the 32-bit installer. The 64-bit installer is appropriate for most environments. However, if you are using ISIS or TWAIN drivers to operate a scanner, you will need to install the 32-bit version. Download the version appropriate to your needs, then also download both the Grooper Desktop and Grooper Web Server installers. |
|
|
The installer files will download as zipped folders. You will need to extract each zipped folder. Right-click a folder and select "Extract All..." |
|
|
|
|
Now you should have all your files extracted and are ready to install the software. Click on the next tab for installation instructions. |
Installing Grooper
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
Installing IIS
For the Grooper 2023 web server to operate properly, there are extra components that need to be installed first. Here we will go through the required Internet Information Services (IIS) installation for your host server.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Installing the Web Client
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
Installing Grooper Desktop
Grooper Desktop can be installed on any desktop computer used to scan documentation. The Grooper thick client does not have to be installed on the computer for Grooper Desktop to operate.
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|
Connecting to a Grooper Repository
A Grooper Repository is the environment used to create, configure and execute objects in Grooper. It provides the framework to "do work" in Grooper.
This environment consists of two things:
- A database connection
- A file store connection
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). Grooper is the application layer that sits on top of this two parts of the environment. It allows readable and writable access and the UI to create, configure, test, and process the information stored there.
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. This is done with the Grooper Config application.
| ⚠ |
Grooper Config must be run as an administrator. It performs functions that require elevated access in Windows. |
Creating a New Grooper Repository
Install SQL Express
| ⚠ |
This step is only applicable to stand-alone Grooper installations on a local machine. If you are using the full version of Microsoft SQL Server and it is already installed and running, you can skip this step and continue to the next tab. Grooper is not designed to run at an enterprise level for your business on SQL Express, but it can be useful for testing/experimentation purposes. |
Remember, a Grooper Repository is two things:
- A database connection
- A file store connection
For Grooper Repositories, nodes and their property values are stored in tables in a SQL database. Node objects created in Grooper Design Studio are stored as rows in a table, with their property values in the row's columns. This can be anything from a Batch of documents, to a Batch Process used to process that Batch, to a Content Model referenced by the Batch Process to classify the documents in the Batch or any object used to execute document processing in Grooper.
|
If you do not have a SQL environment already available, you can download and install Microsoft SQL Express directly from Grooper Config.
|
|
|
|
|
Next, you can install SQL Express directly from Grooper Config.
|
|
|
|
|
You will then be prompted through the SQL Express installation process. |
|
|
Initialize Grooper Config
|
|
|
Upon initializing the system for the first time, you will see this screen. This is a totally unconfigured Grooper Config! From here, we can create new Grooper Repositories and connect to existing Grooper Repositories accessible on your network. If starting totally from scratch, you will need to create at least one Grooper Repository. |
Establish the File Store Location
|
Remember, a Grooper Repository is two things:
The file store simply needs to be a Windows folder you have readable and writable access to. In this case, it is a folder named "okcstrpa01" in a parent folder named "BIS" on the "C: drive" folder of this server.
|
|||
The file store can be any folder you have writeable access to. However, using a fully qualified UNC path is always regarded as best practice. UNC paths can be established using the "Sharing" properties of a folder.
|
|||
|
Create a New Grooper Repository
|
Now that Grooper is initialized, we have a file store location, and we have an available SQL environment (either a full install of SQL Server or SQL Express) we can create a new Grooper Repository. Connecting to a Grooper Repository is the first thing you will do in Grooper Config. If you're not connecting to an existing Grooper Repository set up on someone else's Grooper installation, you'll need to create one.
This will open up a new window to add Grooper Repository connections. |
|||||
|
|||||
|
The first part of creating a new Grooper Repository is establishing the database connection.
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
|
Remember, a Grooper Repository is two things:
Initializing the Grooper Repository connects the repository to the file store location and establishes the folder structure Grooper uses to store files.
|
|||||
|
|||||
|
This will return you to the main Grooper Config window.
|
|||||
|
After licensing your Grooper installation, you will be able to access the Grooper Repository in Grooper Design Studio. The Grooper Repository forms the root node of the Node Tree when the repository is selected in Grooper Design Studio. |































































