2.90:Grooper Licensing (Service) - Revision history

Dgreenwood at 16:04, 5 August 2025

2025-08-05T16:04:07Z

← Older revision		Revision as of 11:04, 5 August 2025
Line 1:		Line 1:
			__NOINDEX__
	{{AutoVersion}}		{{AutoVersion}}

Randallkinard at 17:59, 29 April 2024

2024-04-29T17:59:55Z

← Older revision		Revision as of 12:59, 29 April 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}
	<blockquote ~~style="font-size~~:~~14pt">~~
	~~'''Grooper Licensing''' is a [[Grooper Service]] that distributes licenses to workstations running Grooper applications. Except for stand-alone Grooper installs, a '''~~Grooper Licensing~~''' service is required for all deployment scenarios.~~		<blockquote>{{#lst:Glossary\|Grooper Licensing}}</blockquote>
	</blockquote>

	For client-server environments, a '''Grooper Licensing''' service is installed and started on the host server using [[Grooper Config]]. Then, a '''License Server''' object is created in [[Grooper Design Studio]] and configured with the host server's name and port number. Next, the license is activated using the "Activate Online" button and entering Grooper serial number, or, if necessary, imported from a .lic file using the "Import License Package" button.		For client-server environments, a '''Grooper Licensing''' service is installed and started on the host server using [[Grooper Config]]. Then, a '''License Server''' object is created in [[Grooper Design Studio]] and configured with the host server's name and port number. Next, the license is activated using the "Activate Online" button and entering Grooper serial number, or, if necessary, imported from a .lic file using the "Import License Package" button.

Dgreenwood at 18:34, 29 December 2023

2023-12-29T18:34:02Z

← Older revision		Revision as of 13:34, 29 December 2023
Line 1:		Line 1:
	~~<onlyinclude>~~		{{AutoVersion}}
	<blockquote style="font-size:14pt">		<blockquote style="font-size:14pt">
	'''Grooper Licensing''' is a [[Grooper Service]] that distributes licenses to workstations running Grooper applications. Except for stand-alone Grooper installs, a '''Grooper Licensing''' service is required for all deployment scenarios.		'''Grooper Licensing''' is a [[Grooper Service]] that distributes licenses to workstations running Grooper applications. Except for stand-alone Grooper installs, a '''Grooper Licensing''' service is required for all deployment scenarios.
Line 7:		Line 7:

	Client machines can then be set up to access licensing information by creating their own '''License Server''' object, referencing the host server's name and port number (Note: You will also need to add the server's machine id to the '''Machines''' folder to accomplish this).		Client machines can then be set up to access licensing information by creating their own '''License Server''' object, referencing the host server's name and port number (Note: You will also need to add the server's machine id to the '''Machines''' folder to accomplish this).
	~~</onlyinclude>~~

	== Installing a Grooper Licensing service ==		== Installing a Grooper Licensing service ==

Dgreenwood: Dgreenwood moved page Grooper Licensing - 2.90 to 2.90:Grooper Licensing (Service) without leaving a redirect

2023-12-29T18:32:50Z

Dgreenwood moved page Grooper Licensing - 2.90 to 2.90:Grooper Licensing (Service) without leaving a redirect

← Older revision	Revision as of 13:32, 29 December 2023
(No difference)

Rpatton: Undo revision 16070 by Rpatton (talk)

2023-12-04T15:47:34Z

Undo revision 16070 by Rpatton (talk)

Show changes

Rpatton: Undo revision 16071 by Rpatton (talk)

2023-12-04T15:47:16Z

Undo revision 16071 by Rpatton (talk)

@@ Line 2: / Line 2: @@
 Once you have your Grooper Repository 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.
 </blockquote>
 There are three ways to license Grooper:
@@ Line 21: / Line 30: @@
 ** If a user attempts to use the license GUID to license another Grooper installation, licensing will fail.
 ** For "self hosted" installations, licensing is distributed to client workstations via a URL provided by the '''Grooper Licensing''' service '''''not''''' the license GUID.
 == Cloud Hosted Licensing ==

Rpatton at 15:46, 4 December 2023

2023-12-04T15:46:42Z

@@ Line 2: / Line 2: @@
 Once you have your Grooper Repository 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.
 </blockquote>
 There are three ways to license Grooper:
@@ Line 30: / Line 21: @@
 ** If a user attempts to use the license GUID to license another Grooper installation, licensing will fail.
 ** For "self hosted" installations, licensing is distributed to client workstations via a URL provided by the '''Grooper Licensing''' service '''''not''''' the license GUID.
 == Cloud Hosted Licensing ==

Rpatton at 15:46, 4 December 2023

2023-12-04T15:46:08Z

Show changes

Dgreenwood at 17:55, 25 September 2023

2023-09-25T17:55:11Z

← Older revision		Revision as of 12:55, 25 September 2023
Line 6:		Line 6:
	For client-server environments, a '''Grooper Licensing''' service is installed and started on the host server using [[Grooper Config]]. Then, a '''License Server''' object is created in [[Grooper Design Studio]] and configured with the host server's name and port number. Next, the license is activated using the "Activate Online" button and entering Grooper serial number, or, if necessary, imported from a .lic file using the "Import License Package" button.		For client-server environments, a '''Grooper Licensing''' service is installed and started on the host server using [[Grooper Config]]. Then, a '''License Server''' object is created in [[Grooper Design Studio]] and configured with the host server's name and port number. Next, the license is activated using the "Activate Online" button and entering Grooper serial number, or, if necessary, imported from a .lic file using the "Import License Package" button.

	Client machines can then be set up to access licensing information by creating their own '''[[License Server]]''' object, referencing the host server's name and port number (Note: You will also need to add the server's machine id to the '''Machines''' folder to accomplish this).		Client machines can then be set up to access licensing information by creating their own '''License Server''' object, referencing the host server's name and port number (Note: You will also need to add the server's machine id to the '''Machines''' folder to accomplish this).
	</onlyinclude>		</onlyinclude>

Dgreenwood at 17:54, 25 September 2023

2023-09-25T17:54:44Z

← Older revision		Revision as of 12:54, 25 September 2023
Line 4:		Line 4:
	</blockquote>		</blockquote>

	For client-server environments, a '''Grooper Licensing''' service is installed and started on the host server using [[Grooper Config]]. Then, a '''[[License Server]]''' object is created in [[Grooper Design Studio]] and configured with the host server's name and port number. Next, the license is activated using the "Activate Online" button and entering Grooper serial number, or, if necessary, imported from a .lic file using the "Import License Package" button.		For client-server environments, a '''Grooper Licensing''' service is installed and started on the host server using [[Grooper Config]]. Then, a '''License Server''' object is created in [[Grooper Design Studio]] and configured with the host server's name and port number. Next, the license is activated using the "Activate Online" button and entering Grooper serial number, or, if necessary, imported from a .lic file using the "Import License Package" button.

	Client machines can then be set up to access licensing information by creating their own '''[[License Server]]''' object, referencing the host server's name and port number (Note: You will also need to add the server's machine id to the '''Machines''' folder to accomplish this).		Client machines can then be set up to access licensing information by creating their own '''[[License Server]]''' object, referencing the host server's name and port number (Note: You will also need to add the server's machine id to the '''Machines''' folder to accomplish this).