2023:Upgrading Grooper to a New Version - Revision history

Dgreenwood: /* Step 1: Stop Services */

2024-06-07T15:14:35Z

Step 1: Stop Services

@@ Line 143: / Line 143: @@
 |}
-{|class="attn-box"
+{{GhostServices}}
 === Step 2: Uninstall the Current Version of Grooper ===

Randallkinard: Randallkinard moved page 2023:Upgrading Grooper to a New Version (Concept) to 2023:Upgrading Grooper to a New Version without leaving a redirect: undo naming

2024-04-18T19:25:11Z

Randallkinard moved page 2023:Upgrading Grooper to a New Version (Concept) to 2023:Upgrading Grooper to a New Version without leaving a redirect: undo naming

← Older revision	Revision as of 14:25, 18 April 2024
(No difference)

Randallkinard: Randallkinard moved page 2023:Upgrading Grooper to a New Version to 2023:Upgrading Grooper to a New Version (Concept) without leaving a redirect: new naming convention

2024-04-18T17:54:41Z

Randallkinard moved page 2023:Upgrading Grooper to a New Version to 2023:Upgrading Grooper to a New Version (Concept) without leaving a redirect: new naming convention

← Older revision	Revision as of 12:54, 18 April 2024
(No difference)

Dgreenwood: /* How To Perform a Simple Upgrade */

2024-02-27T16:24:23Z

How To Perform a Simple Upgrade

Dgreenwood: /* How To Perform a Simple Upgrade */

2024-02-27T16:21:03Z

How To Perform a Simple Upgrade

← Older revision		Revision as of 11:21, 27 February 2024
Line 158:		Line 158:
	\|}		\|}

	==== ~~Reminder~~: ~~Back up your Database and File Store!~~ ====		==== Step 2: 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.

	{\|class="attn-box"		{\|class="attn-box"
Line 164:		Line 165:
	⚠		⚠
	\|		\|
			'''''REMINDER!! BACK UP YOUR GROOPER REPOSITORY BEFORE UNINSTALLING!'''''

	You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.		You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.

Line 173:		Line 176:
	\|}		\|}

	~~==== Step 2: 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.~~

	{\|cellpadding=10 cellspacing=5		{\|cellpadding=10 cellspacing=5

Dgreenwood: /* How To Perform a Simple Upgrade */

2024-02-27T16:17:40Z

How To Perform a Simple Upgrade

← Older revision		Revision as of 11:17, 27 February 2024
Line 68:		Line 68:
	\|}		\|}

	~~<tabs style~~=~~"margin:20px">~~		==== Before You Begin: Backup and Validate Your Grooper Repository ====
	~~<tab name~~="Before You Begin~~" style="margin~~:~~20px">~~

	~~===~~ 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.		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.
Line 78:		Line 75:
	* [[Backup and Restore Grooper Repository]]		* [[Backup and Restore Grooper Repository]]

			===== How to Validate a Grooper Repository =====

	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.		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.
Line 123:		Line 121:
	[[File:2021-upgrading-grooper-validate-branch-3.png]]		[[File:2021-upgrading-grooper-validate-branch-3.png]]
	\|}		\|}
			====Step 1: Stop Services====
	~~</tab>~~

	~~<tab name="Stop Services" style="margin:20px">~~
	====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.		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.
Line 164:		Line 158:
	\|}		\|}

			==== Reminder: Back up your Database and File Store! ====
	~~</tab>~~
	~~<tab name="Uninstall Grooper" style="margin:20px">~~
	==== Back up your Database and File Store ====

	{\|class="attn-box"		{\|class="attn-box"
Line 182:		Line 173:
	\|}		\|}

	==== Uninstall the Current Version of Grooper ====		==== Step 2: 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.		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.

Line 208:		Line 199:
	[[File:2023-Install and Setup-Uninstall Grooper 04.png]]		[[File:2023-Install and Setup-Uninstall Grooper 04.png]]
	\|}		\|}
	~~</tab>~~
	~~<tab name~~=~~"Install the New Grooper Version" style="margin:20px">~~		==== Step 3: Install the New Grooper Version ====
	=== Install the New Grooper Version ===

	{\|cellpadding=10 cellspacing=5		{\|cellpadding=10 cellspacing=5
Line 225:		Line 215:
	\|}		\|}

	=== Additional Guidance for Web Client Deployments ===		===== 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.		* 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.		** It is also considered 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.		* 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.
	\|}
	~~</tab>~~		==== Step 4: Upgrade Grooper Repositories from Grooper Config ====
	~~<tab name~~=~~"Upgrade Grooper Repositories" style="margin:20px">~~
	=== Upgrade Grooper Repositories from Grooper Config ===

	After installing Grooper 2023, open Grooper Config to upgrade the previous versions of Grooper Repositories to 2023.		After installing Grooper 2023, open Grooper Config to upgrade the previous versions of Grooper Repositories to 2023.
Line 319:		Line 307:
	* '''Object Libraries''' should be compiled ''before'' validating your repository to ensure best results.		* '''Object Libraries''' should be compiled ''before'' validating your repository to ensure best results.
	\|}		\|}

	~~</tab>~~
	~~:[[#Upgrading an Older Version of Grooper\|Click here to return to the top of the section]]~~
	~~</tabs>~~
	<section end="Upgrade1" />		<section end="Upgrade1" />

Dgreenwood: /* About */

2024-02-27T16:06:38Z

About

← Older revision		Revision as of 11:06, 27 February 2024
Line 20:		Line 20:
	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).		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:		The upgrade process is essentially four steps:

			# Stop any Grooper services.
	# Uninstall the older version of Grooper.		# Uninstall the older version of Grooper.
	# Install Grooper ~~2023~~.		# Install the newer version of Grooper.
	# Upgrade Grooper Repositories from the older version to ~~2023~~.		# Upgrade Grooper Repositories from the older version to the newer.

	{\|class="attn-box"		{\|class="attn-box"

Dgreenwood at 15:56, 12 January 2024

2024-01-12T15:56:56Z

← Older revision		Revision as of 10:56, 12 January 2024
Line 9:		Line 9:
	{\|class="important-box"		{\|class="important-box"
	\|		\|
	'''~~‼~~'''		'''!!'''
	\|		\|
	'''IMPORTANT!! NEW GROOPER ARCITECTURE DETECTED - PROJECTS'''		'''IMPORTANT!! NEW GROOPER ARCITECTURE DETECTED - PROJECTS'''
Line 98:		Line 98:
	\|valign=top style="width:40%"\|		\|valign=top style="width:40%"\|

	{\|~~cellpadding=10 cellspacing=5 style~~="~~margin:12px~~"		{\|class="important-box"
	\|-		\|
	~~\|style="font-size:200%; background-color:#662d91; color:white; width:28px; text-align:center"\|~~'''~~‼~~'''		'''!!'''
	~~\|style="border: 4px solid #662d91"~~\|		\|
	It is recommended that you validate your ENTIRE repository before upgrading to a new version of Grooper. However, validation CANNOT be performed at the Root Node in the web client. You MUST open the thick client in order to fully validate your repository.		It is recommended that you validate your ENTIRE repository before upgrading to a new version of Grooper. However, validation CANNOT be performed at the Root Node in the web client. You MUST open the thick client in order to fully validate your repository.
	\|}		\|}

Dgreenwood at 15:37, 12 January 2024

2024-01-12T15:37:09Z

← Older revision		Revision as of 10:37, 12 January 2024
Line 236:		Line 236:
	After installing Grooper 2023, open Grooper Config to upgrade the previous versions of Grooper Repositories to 2023.		After installing Grooper 2023, open Grooper Config to upgrade the previous versions of Grooper Repositories to 2023.

	{\|~~cellpadding~~="~~10" cellspacing="5" style="margin:12px~~"		{\|class="fyi-box"
	\|-		\|
	~~\|style="font-size:125%; background-color:#36b0a7; color:white; width:28px; text-align:center"\|~~'''FYI'''		'''FYI'''
	~~\|style="border: 4px solid #36b0a7"~~\|		\|
	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.		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.

Dgreenwood at 13:55, 12 January 2024

2024-01-12T13:55:22Z

← Older revision		Revision as of 08:55, 12 January 2024
Line 26:		Line 26:
	# Upgrade Grooper Repositories from the older version to 2023.		# Upgrade Grooper Repositories from the older version to 2023.

	{\|~~cellpadding~~="~~10" cellspacing="5" style="margin:12px; width: 100%~~"		{\|class="attn-box"
	\|-		\|
	~~\|style="font-size:250%; background-color:#f89420; color:white; width:28px; text-align:center"\|~~⚠		⚠
	~~\|style="border: 4px solid #f89420"~~\|		\|
	This article instructs users on how to perform simple upgrades. The instructions in this article outline the basic steps for all upgrades.		This article instructs users on how to perform simple upgrades. The instructions in this article outline the basic steps for all upgrades.

Line 148:		Line 148:
	\|}		\|}

	{\|~~cellpadding~~="~~12" cellspacing="4" style="margin:12px~~"		{\|class="attn-box"
	\|-		\|
	~~\|style="font-size:250%; background-color:#f89420; color:white; width:28px; text-align:center"\|~~⚠		⚠
	~~\|style="border: 4px solid #f89420"~~\|		\|
	Very rarely, a Grooper service will not uninstall properly when you uninstall the service from Grooper Config. This can make it appear as though a duplicate or "ghost" Windows service is installed without being listed in Grooper Config.		Very rarely, a Grooper service will not uninstall properly when you uninstall the service from Grooper Config. This can make it appear as though a duplicate or "ghost" Windows service is installed without being listed in Grooper Config.

Line 168:		Line 168:
	==== Back up your Database and File Store ====		==== Back up your Database and File Store ====

	{\|~~cellpadding~~="~~10" cellspacing="5" style="margin:12px~~"		{\|class="attn-box"
	\|-		\|
	~~\|style="font-size:250%; background-color:#f89420; color:white; width:28px; text-align:center"\|~~⚠		⚠
	~~\|style="border: 4px solid #f89420"~~\|		\|
	You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.		You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.

Line 309:		Line 309:
	\|}		\|}

	{\|~~cellpadding~~="~~10" cellspacing="5" style="margin:12px~~"		{\|class="attn-box"
	\|-		\|
	~~\|style="font-size:250%; background-color:#f89420; color:white; width:28px; text-align:center"\|~~⚠		⚠
	~~\|style="border: 4px solid #f89420"~~\|		\|
	'''IMPORTANT''' - If present, make sure you compile all '''Object Libraries''' after the upgrade.		'''IMPORTANT''' - If present, make sure you compile all '''Object Libraries''' after the upgrade.

← Older revision		Revision as of 11:24, 27 February 2024
Line 44:		Line 44:

	\|}		\|}
	=== How To Perform a Simple Upgrade ===		== How To Perform a Simple Upgrade ==

	{\|class="fyi-box"		{\|class="fyi-box"
Line 68:		Line 68:
	\|}		\|}

	==== Before You Begin: Backup and Validate Your Grooper Repository ====		=== Before You Begin: 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.		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.
Line 75:		Line 75:
	* [[Backup and Restore Grooper Repository]]		* [[Backup and Restore Grooper Repository]]

	===== How to Validate a Grooper Repository =====		==== How to Validate a Grooper Repository ====

	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.		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.
Line 121:		Line 121:
	[[File:2021-upgrading-grooper-validate-branch-3.png]]		[[File:2021-upgrading-grooper-validate-branch-3.png]]
	\|}		\|}
	====Step 1: Stop Services====		===Step 1: 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.		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.
Line 158:		Line 158:
	\|}		\|}

	==== Step 2: Uninstall the Current Version of Grooper ====		=== Step 2: 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.		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.

Line 201:		Line 201:
	\|}		\|}

	==== Step 3: Install the New Grooper Version ====		=== Step 3: Install the New Grooper Version ===

	{\|cellpadding=10 cellspacing=5		{\|cellpadding=10 cellspacing=5
Line 216:		Line 216:
	\|}		\|}

	===== Additional Guidance for Web Client Deployments =====		==== 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.		* 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.
Line 222:		Line 222:
	* 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.		* 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.

	==== Step 4: Upgrade Grooper Repositories from Grooper Config ====		=== Step 4: Upgrade Grooper Repositories from Grooper Config ===

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