Install and Setup - 2023

Welcome to Grooper 2023!

This guide will instruct you how to get up and running in Grooper.  There are three parts of installing and setting up Grooper:

1. Installing the Grooper Product Suite
   • Additional setup is required when setting up a web server to run the Grooper web client. This is covered in the Installing and Configuring the Web Client sub-section.
2. Connecting to a Grooper Repository
   • This section of the article article explains both how to create a new Grooper Repository as well as connecting to an existing one.
3. License Activation

At the end of this article, you will also find guidance for upgrading an older version of Grooper to the current version.

About

Thank you for purchasing/upgrading to Grooper 2023!

NEW! Expanded Web Client!

In previous versions of Grooper, it was necessary to fully install the software on each server and client workstation you wanted to have access to Grooper. No matter if they were designing your Grooper environment or reviewing documents, Grooper had to be installed on each machine. This could cause difficulties in managing the software on multiple workstations. Furthermore, each user would need read and write access to the Grooper Repository's database and file store location. This could present a security risk to your SQL and file store environments, as the more users have access, the more risk there is of untoward intrusion.

With Grooper 2023, Grooper can be fully hosted on a web server. Users can then connect to the Grooper web application via web browser. This means the software only has to be fully installed on one server! This makes everything a lot easier to manage, as there's no more need to install Grooper on each user's workstation. Furthermore, web deployment is more secure. The only user who needs access to the Grooper database and file store is the web server's IIS account.

• Web deployments require additional setup to get Grooper up and running over the web. For information on how to install the web client, please be sure to check out the Installing and Configuring the Web Client section of this article.
• For more information on other new features in Grooper 2023, check out the What's New In Grooper 2023 article.

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 is web server developed by Microsoft for Windows. It is necessary to host the Grooper web client.
• Grooper Web Server: With this application properly installed and configured, multiple users can access Grooper remotely via web browser.
• Grooper Desktop: This application is only necessary for remote scanning when using the Grooper web client.

Download the InstallerInstalling Grooper

Download the Installer

If you have not registered at Grooper xChange, do so by clicking the link below. https://xchange.grooper.com/entry/register 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. https://xchange.grooper.com/categories/downloads-and-resources
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. The 64-bit installer is appropriate for most environments. If you are setting up a web server to host the Grooper web client, you must use the 64-bit installer. You will also need to download the Grooper Web Server installer. If you are using ISIS or TWAIN drivers to operate a scanner: For thick client installations, you will need to install the 32-bit version on scanning workstations. For web client installations, you will need to install the Grooper Desktop application on scanning workstations.
The installer files will download as zipped folders. You will need to extract each zipped folder. Right-click a folder and select "Extract All..."
Choose the folder location you wish to extract the files to. Click the "Extract" button.
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

Open up File Explorer and navigate to your extracted folders. Open the extracted folder "GrooperInstall_23.00.xxxx" to reveal the installation files.
Double-click "setup.exe" to start the Grooper Installer. ⚠ If this is your first time installing Grooper, you may have some prerequisites to install (Microsoft Visual C++, Access Database Engine, and the Microsoft .NET Framework). If you already have these installed from a previous Grooper installation, please skip to step #8.
When the InstallShield Wizard for Grooper pops up, click "Install" to start installing the prerequisite applications. FYI You may already have the Microsoft .NET Framework installed, but this prerequisite installation will check to make sure that all components necessary for Grooper to run are present.
Once Microsoft Visual C++ is installed, your server may require a restart. When prompted, please restart.
After restarting, open File Explorer and navigate back to the setup.exe file and double-click again to restart the InstallShield Wizard. Click "Install" to continue installing the prerequisite applications.
Once complete, the Grooper installer will pop up. Click "Next" to move to the next screen.
After reviewing the Welcome page to the InstallShield Wizard, click "Next" to continue.
Read through the End User License Agreement and click the radial button next to "I accept the terms in the license agreement". Click "Next" to continue.
Now you can choose the location where you want the Grooper Application to be installed. It is recommended to use the default file path, but based on your business needs, you may choose a different area for the installation on your server. Once you are satisfied with the installation location, click "Next".
Select the radial button next to your preferred setup type. Generally we recommend performing a Complete setup of Grooper onto your server, but there are some cases where you might want to customize your installation depending on your business needs. Click "Next".
You are now ready to install the program. Click "Install" to begin installation.
Installation should only take a few minutes. When complete, a window should pop up saying that the installation is complete. Click "Finish" to finalize your installation.

Click here to return to the top of the section

Installing and Configuring the Web Client

To stand up a Grooper 2023 web server, there are three things that need to be installed first:

1. The Grooper product suite

   ⚠  It is best practice to install the Grooper product suite first, before installing the Grooper Web Client application.

2. Internet Information Services (IIS)
3. The Grooper Web Client application

FYI

Desktop Scanning Advice Once your Grooper web server is stood up, you can scan remotely from any computer able to connect to the web server via an internet browser. However, each scan operator will need to have an additional application, Grooper Desktop, installed on there computer to operate the scanner. For information on how to install Grooper Desktop please refer to the "Installing Grooper Desktop" and "Reserve URL for Grooper Desktop" tabs below.

Installing IISInstalling the Web ClientInstalling ServicesFYI: How to Create and Bind a Self-Signed CertificateInstalling Grooper DesktopReserve URL for Grooper Desktop

Installing IIS

Here we will go through the required Internet Information Services (IIS) installation for your host server.

Open Server Manager.
In the top right corner, click on "Manage" to bring up the drop down menu. Click "Add Roles and Features".
In the window that pops up, feel free to read through the information associated with the installation wizard and then click "Next".
Make sure "Role-based or feature-based installation" is selected. Click "Next".
Select the desired server from the server pool list. Click "Next".
Click the check box next to Web Server (IIS) under "Roles" to add the option (When the dialogue box pops up, click the "Add Features" button at the bottom). Click "Next".
On this screen you don't need any additional features, so just click "Next".
Feel free to read through the description of what a web server is, and click "Next".
We need to make sure that the appropriate role services are installed for Grooper to function. Scroll through the list and select the following components (If a window appears asking you to add features, click the "Add Features" button): Web Server Common HTTP Features Default Document Static Content Security Request Filtering Basic Authentication Windows Authentication Application Development .NET Extensibility 4.5 (or above) ASP.NET 4.5 (or above) ISAPI Extensions ISAPI Filters WebSocket Protocol Management Tools IIS Management Console IIS 6 Management Compatibility IIS 6 Metabase Compatibility IIS Management Scripts and Tools Management Service Click "Next" after all components are selected.
If desired, click the checkbox next to "Restart the destination server automatically if required". Click the "Install" button and allow the installation to run.
Once installation is complete, click "Close" to close the wizard.

Installing the Web Client

⚠	If you wish to perform ad hoc processing or multi-threaded process step testing via web client, you will need to install two services in Grooper Config: an Import Watcher and an Activity Processor. Please see installation instructions in the next tab.

Open up File Explorer and navigate to your extracted folders. Open the extracted folder "GrooperWebClient_23.00.xxxx" to reveal the installation files.
Double-click "setup.exe" to start the Grooper Installer.
After reviewing the Welcome page to the InstallShield Wizard, click "Next" to continue.
Read through the End User License Agreement and click the radial button next to "I accept the terms in the license agreement". Click "Next" to continue.
Enter in the user name and password to be associated with this installation of Grooper. This needs to be the user name and password associated with the server Grooper is being installed on. This will allow you to configure permissions for other users later on. ⚠ Make sure your user name starts with the domain name using the format: "DOMAIN\username". Click "Next".
Click the "Install" button to begin installation.
Installation should only take a few minutes. When complete a window should pop up saying that the installation is complete. Click "Finish" to finalize your installation.

Installing Services

When using the Grooper web client, two Grooper services must be installed and running for certain ad-hoc operations.

• The Import Watcher service must be installed to perform ad-hoc document imports from the Imports page.
• The Activity Processing service must be installed to submit multithreaded jobs when using the Unattended Activity tester on a step in a Batch Process.

Here we will show you how to install and start the services needed.

Open Grooper Config and click on "Edit Services".
Once the "Service Manager" window pops up, click "Install..." in the top left corner.
In the "Install New Service" window, select "Import Watcher". In the top right corner, select the repository needing the service from the drop down list. Click "OK".
When the "Import Watcher" window pops up, enter the user name and password associated with the server Grooper is installed on. Make sure to include the domain name in your user name following the convention DOMAIN\username. Click "Execute". FYI While setting up the Import Watcher, you can configure the Scheduled Imports, but this is optional. The Import Watcher must be running to perform ad-hoc imports in the web client, with or without Scheduled Imports.
Once back in the "Service Manager" window, click "Install..." in the top left corner again.
In the "Install New Service" window, select "Activity Processing". In the top right corner, select the repository needing the service from the drop down list. Click "OK".
When the "Activity Processing" window pops up, enter the user name and password associated with the server Grooper is installed on. Make sure to include the domain name in your user name following the convention DOMAIN\username. If desired, change the Number of Threads property to reflect the thread count you wish to use for processing. The maximum number of threads should not exceed the total number of processor threads available minus one.  One thread must be reserved to run the operating system.  e.g. If the machine has 20 total threads, the highest value you should enter for Number of Threads should be 19. If the service is running on the same server where IIS is installed, an additional thread should be reserved for IIS. If the service is running on the same server where SQL is installed, an additional thread should be reserved for SQL. Click "Execute".
When back at the "Service Manager" window, click "Start All" if you wish to start all of your services. You can also choose specifically which services to start by selecting each one individually and clicking "Start".
When activated, the dot to the left of the service will turn from red to green.

FYI: How to Create and Bind a Self-Signed Certificate

Generally speaking, you should always connect to a website using the more secure HTTPS protocol and not the unsecure HTTP. Enabling SSL on your web server will allow you to do so. For the purposes of this tutorial, we will not enable SSL. However, this is not best practice in the wide world of world wide web traffic. Even for internal use, you should at least use a self-signed SSL certificate.

Here, we will cover the most basic steps to create a self-signed SSL certificate and bind it to the Grooper Web Client's website.

First, open the Information Internet Services (IIS) Manager application on your web server. Select your server in the left-hand Connections panel. Click "Server Certificates".
In the right-hand Actions panel, click "Create Self-Signed Certificate..."
Enter a name for the certificate. Click "OK".
Expand the server connection and select the "Grooper" site. Click "Bindings..."
Click "Add..."
Under "Type" select "https" from the drop down list. Under "Host name" enter the host address (if applicable). Under "SSL certificate", select the self signed certificate you created earlier. Click "OK" when finished.
You should now see the binding for port 443. Click "Close".

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.

Open up File Explorer and navigate to your extracted folders. Open the extracted folder "GrooperDesktop_23.00.xxxx" to reveal the installation files.
Double-click "setup.exe" to start the Grooper Installer.
After reviewing the Welcome page to the InstallShield Wizard, click "Next" to continue.
Read through the End User License Agreement and click the radial button next to "I accept the terms in the license agreement". Click "Next" to continue.
Now you can choose the location where you want the Grooper Application to be installed. It is recommended to use the default file path. FYI Notice that this application is being installed in Program Files (x86). We are installing a 32-bit application because it interfaces with scanners. Click "Next".
Click the "Install" button to begin installation.
Installation should only take a few minutes. When finished, a window should pop up saying that the installation is complete. Click "Finish" to finalize your installation.
There is one more thing we need to do to finish the installation of Grooper Desktop. We need to reserve a URL for Grooper Desktop to use. See the next tab for instructions on how to do this.

Reserve URL for Grooper Desktop

The first time you run Grooper Desktop, you might notice a notification pop up above your system tray that says Grooper Desktop is "Not Configured".

This is because you need to reserve the URL as the listening location that the service will use to pull from the scanner. We will run a short command line code to reserve this URL.

right click on the Grooper "G" logo in your system tray and click on "Configure..."
When the window pops up, Web Scanning is set to "Disabled". Click the drop-down arrow and select "Enabled".
Click the down arrow to the left of "Web Scanning" to expand properties. Down at the bottom, you will see a property called "URL Reservation". It is populated with a netsh command. Select the contents of this property and copy it to your clipboard.
Open a Command Prompt (as an administrator) in Windows and paste the previously copied netsh command. Hit Enter. The command prompt should return with "URL reservation successfully added".
Now you should be finished with the installation of Grooper Desktop!

Click here to return to the top of the section

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:

1. A database connection
2. 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 (Optional)Initialize Grooper ConfigEstablish the File Store LocationCreate 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:

1. A database connection
2. 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. Click the "Download SQL Express..." button.
The installer files will download automatically. You will see this dialog box appear upon successful download. Click "Ok" to continue.
Next, you can install SQL Express directly from Grooper Config. Click the "Install SQL Express..." button. The following confirmation box will appear. Click "Yes" to continue installing SQL Express.
Grooper will then prompt you for a folder location to save the installed files. This defaults to a folder in the "Grooper" folder of the "BIS" folder created during installation. Click "Ok" to continue.
You will then be prompted through the SQL Express installation process.
Upon successful installation, the following dialog box will appear. You can elect to either keep the installer executable file or delete it. You don't need it anymore. You may as well delete it. Click "Yes" to delete the file.

Initialize Grooper Config

If this is your first time opening Grooper Config after installation, you will need to initialize the System Configuration. You will see the following dialog box appear. Click "Yes" to initialize.
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: A database connection A file store connection 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. What you name your file store and where you put it is totally up to you.
⚠ Grooper strongly recommends always using a UNC path to avoid access problems when networking your Grooper Repositories. Mapped and local drive references may not be accessible to other users or machines. 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. Right-click the folder Select the "Properties" option.
In the following window, click the "Sharing" tab. If the folder is already shared, you will see the UNC path under "Network Path" The UNC naming convention for Windows paths is as follows: \\host-name\file_path If you have not shared the folder, you can do so by clicking the "Share..." button. From there you can list users or user groups who should have networked access to the 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.

⚠	If you are using the Web Client, you will need to recycle the Grooper app pool in IIS to access any new repository you create or when connecting to a previously configured repository.

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.
Click the "Add" button to add a new connection.
The first part of creating a new Grooper Repository is establishing the database connection. 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 \GROOPER 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.
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.
FYI 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.
Upon creating the database, you will get a message letting you know the database has not been initialized. Click "Ok" to continue.
Click the "Initialize" button.
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. Select the Storage Path property and enter the file path for the file store's folder. Click the "Execute" button to initialize the Grooper Repository. ⚠ 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. FYI 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 click the "Rename" button to rename it.
Upon successful initialization, you will receive this confirmation window. Click the "Ok" button to continue. Click the "Ok" button to finish.
This will return you to the main Grooper Config window. Click the "Save" button to finalize your Grooper Repository connection.

Click here to return to the top of the section

Connecting to an Existing Grooper Repository

Add a Repository ConnectionConfigure the Connection

Add the Repository Connection

Connecting to an existing Grooper Repository is similar to creating a new one. It is essentially the same process with fewer steps. For this tutorial, we will connect to a repository that is hosted on another machine.

FYI

When connecting to a networked repository, you do not need to have a SQL environment on the machine accessing the repository. As long as the machine has networked access to the SQL server where the Grooper repository's database is created and networked access to the repository's file store location, it can connect to the repository.

⚠	If you are using the Web Client, you will need to recycle the Grooper app pool in IIS to access any new repository you create or when connecting to a previously configured repository.

The first steps of connecting to an existing Grooper Repository are the same as creating a new one. Select the Repositories property. Click the ellipsis button at the end of the property to bring up the Grooper Repositories connection editor.
In the new window that pops up, click the "Add" button to add a new connection.

Configure the Connection

Select the Server Name property and enter the server's name running the SQL environment. Select the Database Name property and enter the Grooper Repository's database name. Click the "Test Connection" button.
FYI The repository we are connecting to has already been created and initialized on another machine. As long as we have networked access to the SQL environment and file store, we should be able to just connect to it. A dialog box appears letting you know the connection is successful. Click "Ok" to continue.
FYI By default, Grooper will use your Windows login authentication to access the SQL server and database. 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.
You will see the "Status" listed as Ok indicating you have successfully connected to the Grooper Repository. Click the "OK" button to continue.
This will return you to the main Grooper Config window. Click the "Save" button to finalize your Grooper Repository connection.

Click here to return to the top of the section

License Activation

Now that you have your repositories initialized and connected, you need to activate your Grooper license. When you purchased Grooper, you should have received a license key GUID, something like "1a2b3c4d-5e6f-7g8h-9i10-j11k12l13m14". You will need this GUID to license your Grooper installation.

There are three ways to license Grooper:

• shared-online
• stand-alone
• hosted

In this article, we will show you how to perform "shared-online" licensing. Shared-online licensing is the easiest but least secure method of licensing.

• It is easiest because a Grooper Repository is licensed simply by entering the license GUID into a property at the root node in Grooper Design. Licensing is decremented over the internet.
• However, all that's required to license the repository is the GUID. It is not locked to any individual server or machine on use.
  • This means any user with the license GUID and an internet connection can use the license. Make sure to keep your GUID secure and do not share with anyone that you do not wish to have access.

The "stand-alone" and "hosted" methods require additional setup using Grooper Config but are more secure.

• These installations are more secure because the license is locked to an individual machine when the license key is activated.
  • If a user attempts to use the license GUID to license a Grooper Repository, licensing will fail.
  • For "hosted" installations, licensing is distributed to client workstations via a URL provided by the Grooper Licensing service not the license GUID.
  • For information on the stand-alone and hosted licensing methods, visit the Grooper Licensing article.

How to Activate Your License Using the "Shared-Online" Method

To license your Grooper repository using "shared-online" licensing, perform the following steps: Open the Grooper Web Client in a web browser. At the top you will see that the software is currently "UNLICENSED". Click the "Design" icon.
With the repository selected in the root node, make sure the "Root" tab is selected. Click to the right of the License Serial# or URL property and paste your activation key. Click the "Save" button. ‼ IMPORTANT: Again, when licensing Grooper this way, the GUID is not connected to any one machine. Your GUID can be used by any user with access to a web browser. Make sure to keep your GUID secure and do not share with anyone that you do not wish to have access.
Close and re-open Grooper Design Studio. At the top the "LICENSEE" should now reflect your current liscence. You may begin using Grooper!

Upgrading an Older Version of Grooper

‼

IMPORTANT!!! NEW GROOPER ARCITECTURE DETECTED - PROJECTS Projects are a new way of organizing Grooper resources in the node tree. After upgrading, all your resources will work as they did before, but their organization will shift from certain parts of the node tree to a Project named "Project 1". You may choose to move resources out of this Project and into new Projects or you can choose to keep everything in "Project 1". For more information and guidance, refer to the links below: Project - This is the full Projects article. It has general information about what Projects are and how to use them. Projects and Upgrading to 2023 - This contains specific guidance around upgrading from an older version of Grooper to version 2023, how to navigate the new Project architecture, and how to move from "Project 1" to new Projects.

Upgrading to 2023 is now easier than ever. You can upgrade directly from version 2.72, 2.80, 2.90, 2021, or 2022 to version 2023 (For upgrading from versions older than 2.72, you must upgrade to 2.72 before upgrading to 2023).

The upgrade process is essentially three steps:

1. Uninstall the older version of Grooper.
2. Install Grooper 2023.
3. Upgrade Grooper Repositories from the older version to 2023.

⚠

This article instructs users on how to perform simple upgrades. The instructions in this article outline the basic steps for all upgrades. However, depending on your Grooper install, your upgrade process may be more involved. If you are running scripts in your environment to customize Grooper's functionality, you may need to update the associated scripting code and Object Libraries, as some code objects may have been altered or obsoleted or their names may have changed. If present, make sure you re-compile all Object Libraries after the upgrade. Custom scripts are not guaranteed to work without changes upon upgrading to a new major version of Grooper. If you are running custom reports polling the Grooper database, you may need to update the report query, as Grooper's database tables may have changed. If you are using expressions in your Batch Processes, IP Profiles, Data Models or Import/Export Mappings, please verify all expressions are working as intended as some as some code objects may have been altered or obsoleted or their names may have changed. If you are moving across multiple major versions, it's likely Grooper's architecture has changed more than if upgrading from one major version to the next. Your solution design may not be taking advantage of newly added features in newer versions. In all cases, you should take some time to test your Grooper system after an upgrade to ensure everything is working as expected. When upgrading across multiple major versions, please take extra care to do so.

How To Perform a Simple Upgrade

FYI	If you are upgrading from version 2.72, 2.80 or 2.90, 2021, or 2022 to 2023, you may upgrade directly to version 2023. However, if you are upgrading from version 2.70 (or older) to 2023, you must first upgrade to version 2.72, and then upgrade to version 2023.

‼

IMPORTANT!!! DON'T FORGET TO BACKUP YOUR REPOS You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version. If, for whatever reason, something goes wrong during the upgrade process and your file store and/or database is corrupted, you could loose critical components, such as your Batch Processes, Content Models, or document files for any Test or Production Batches. Performing a backup will ensure you have something to revert to in the rare cases where the upgrade does improperly overwrite existing database values or files in your file store. For information how to backup and restore your Grooper database and file store, please visit the article below: Backup and Restore Grooper Repository

Before You BeginStop ServicesUninstall GrooperInstall the New Grooper VersionUpgrade Grooper Repositories

Backup and Validate Your Grooper Repository

You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version. If, for whatever reason, something goes wrong during the upgrade process and your file store and/or database is corrupted, you could loose critical components, such as your Batch Processes, Content Models, or document files for any Test or Production Batches. Performing a backup will ensure you have something to revert to in the rare cases where the upgrade does improperly overwrite existing database values or files in your file store.

For information how to backup and restore your Grooper database and file store, please visit the article below:

• Backup and Restore Grooper Repository

FYI	Repository validation can only be performed on the Grooper thick client. You cannot validate from the web client.

While not strictly necessary, the Grooper developers strongly encourage you perform validation on your Grooper Repository before upgrading from and older version to a newer version of Grooper. Improperly configured nodes can cause unexpected issues during upgrade. Validating your repository helps catch these configuration issues to avoid configuration related problems when upgrading the objects in your existing repository to the newer versions of those objects.

For example, a Data Type extractor object whose Collation property is set to Key-Value Pair must have a Layout specification as part of its configuration. If this is left unconfigured, validation will catch the configuration error. The Data Type selected in the Node Tree here does not have a Layout enabled.
To validate your Grooper Repository and catch configuration errors like the one described above perform the following steps: In Grooper Design Studio, select the root of the repository's Node Tree in the Tree View window.
Select "Tools" from the toolbar. Select "Validate Branch..." This will bring up the "Validate Branch" window. Click the "Validate" button. Grooper will check every object in your repository for any property configuration errors. Any object with configuration errors will be listed here. By choosing the validate the root, you validate all descendent branches. In other words, the whole repo. You may select any object in the list and click the "Go To Item" button to go to that object and resolve the configuration error, if you so choose.

Stop Services

Before uninstalling your current version of Grooper, you will need to stop all services currently running in Grooper Config. This will help avoid potential errors regarding the services connected to your repositories.

Open Grooper Config and click "Edit Services".
If you have any services running they will be listed with a green dot to the left side. You can select each individual service and click "stop" or you can just click "Stop All".
Once a service is stopped, the dot to the left of the service name should turn red.

⚠

If you do not stop running Grooper services, there is a chance a duplicate Windows service will be installed when the new version of Grooper is reinstalled. If this does occur, you will need to manually delete the service from the Windows Registry Editor, using the following steps: Open the Registry Editor (regedit.exe) Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services key. Select the key of the service you want to delete. From the "Edit" menu select "Delete. You will be prompted "Are you sure you want to delete this Key?". Click Yes. Exit the Registry Editor.

Back up your Database and File Store

⚠

You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version. If, for whatever reason, something goes wrong during the upgrade process and your file store and/or database is corrupted, you could lose critical components, such as your Batch Processes, Content Models, or document files for any Test or Production Batches. Performing a backup will ensure you have something to revert to in the rare cases where the upgrade does improperly overwrite existing database values or files in your file store. For information how to backup and restore your Grooper database and filestore, please visit this article.

Uninstall the Current Version of Grooper

The first thing you need to do is uninstall the current version of Grooper before installing the new version. This can be done in a number of ways, such as uninstalling from your settings menu.

Open your Windows Settings and click on "Apps".
Scroll down through your list of apps until you find the Grooper application. Click on the app. When it expands, click on "Uninstall".
A small window may pop up to confirm you wish to uninstall the app. Click "Uninstall".
Wait for the application to be uninstalled.

Install the New Grooper Version

If you have not done so, you will need to download the current installer file from Grooper xChange. Zip archives containing the installer files can be found in the "Downloads and Resources" section, linked bellow https://https://xchange.grooper.com/categories/downloads-and-resources Once downloaded, unzip the installer file, open the "Setup" executable file and follow the onscreen instructions to install the current Grooper version. If you need more help, you can find the full Grooper installation instructions by following the link below: Installing the Grooper Product Suite

Additional Guidance for Web Client Deployments

• If you are upgrading the Grooper web client, you must also uninstall the Grooper Web Client application on your web server and install the newer version.
  • IMPORTANT It is best practice to stop the Grooper app pool in IIS before uninstalling the Grooper Web Client application.
• After upgrading the Grooper web server, if you have remote scan workstations with Grooper Desktop installed, you will also need to uninstall Grooper Desktop and install the newer version on each workstation.

|}

Upgrade Grooper Repositories from Grooper Config

After installing Grooper 2023, open Grooper Config to upgrade the previous versions of Grooper Repositories to 2023.

FYI

Major versions of Grooper change the Grooper Database in meaningful ways. These changes to the database must be reflected by upgrading the Grooper Repository. For major version upgrades (For example, 2.80 to 2021 or 2021 to 2023), all Grooper Repositories configured on an older version must be upgraded in order to connect to them to Grooper. For minor version upgrades (For example, 2.90.0001 to 2.90.0002) you do not need to upgrade each Grooper Repository. No major changes are made to the Grooper Database, and you can skip this step. However, you should still always uninstall the old version of Grooper before installing the new version, even when upgrading to a new minor version.

When upgrading from a version older than 2021 to version 2021 or later, you'll notice the Grooper Config application's UI has changed. Previously, Grooper Repository connections were listed in a grid. Now, we will need to get into the Repositories configuration window to upgrade the previous versions of the Grooper Repositories to the new versions.

Select the Repositories property. Click the ellipsis button at the end of the property.
Currently, Grooper version 2023 is installed on this machine. As seen here, in Grooper Config, we have two Grooper Repository connections: one named "okcstrpa01_001" and the other "okcstrpa01_002". The Grooper Repository named "okcstrpa01_001" is a networked repository. Its status is listed as "Ok" because it has already been updated to Grooper 2023. This repository's version matches the version of Grooper installed on this machine. The Grooper Repository named "okcstrpa01_002" is another networked repository. Its status is listed as "Needs Upgrade" because it has not been updated to Grooper 2023 yet. After upgrading to Grooper 2023 you will need to upgrade all previous repositories to 2023.
To upgrade a Grooper Repository, select the repository that needs upgrading. Click the "Upgrade..." button in the upper toolbar.
An "Upgrade" window will appear. Click the "Execute" button to confirm the upgrade.
You will be prompted to execute a Version Upgrader. Click "Execute" to start the upgrader.
When the upgrader is finished, click "Ok". In instances where you are upgrading multiple versions of Grooper (i.e. 2.80 to 2021) you must run each Version Upgrader sequentially. For example, in our case, we had to execute the Version 2021 to 2022 Upgrader first, followed by the Version 2022 to 2023 Upgrader. Repeat steps 6. and 7. for each version of Grooper you are needing to upgrade.
After the upgrade is complete, click the "Test Connection.." button to ensure you're now property connected to the upgraded database. If successful, a message box will pop up confirming your connection. Click Ok.
You will see the upgraded Grooper Repository's Status change from "NeedsUpgrade" to "Ok". Click the "Ok" button to exit the Repositories window.
Click the "Save" button in the main screen of Grooper Config to complete the upgrade.
Congratulations! You've upgraded Grooper.

⚠	IMPORTANT - If present, make sure you compile all Object Libraries after the upgrade. IMPORTANT - The devs also strongly recommend that you perform validation on your repository after upgrading. Object Libraries should be compiled before validating your repository to ensure best results.

Click here to return to the top of the section