Licenses & Nodes - Revision history

Craig at 17:48, 23 April 2024

2024-04-23T17:48:33Z

← Older revision		Revision as of 17:48, 23 April 2024
Line 37:		Line 37:
	You can find your license key in [[Admin Scheduler Settings\|Scheduler Settings]] as shown below.		You can find your license key in [[Admin Scheduler Settings\|Scheduler Settings]] as shown below.

	Obsidian will automatically acquire your free single node license ~~and~~ a second ~~trial~~ clustering node ~~license which is valid~~ for a year. If you are converting your trial backup node license to a paid license or are purchasing additional nodes, you can obtain your license key from the location show below.		Obsidian will automatically acquire your free single node license. You can request a second clustering node for evaluation for up to 1 year. If you are converting your trial backup node license to a paid license or are purchasing additional nodes, you can obtain your license key from the location show below.

	[[Image:ClientKey_4.0.png]]		[[Image:ClientKey_4.0.png]]

Craig at 18:40, 15 January 2024

2024-01-15T18:40:16Z

← Older revision		Revision as of 18:40, 15 January 2024
Line 1:		Line 1:
	Each running Obsidian scheduler process requires a valid license. Here are some quick facts:		Each running Obsidian scheduler process requires a valid license. Here are some quick facts:
	* When you download Obsidian, it automatically obtains a free license key, which gives you one free license for permanent use, and a second ~~license valid~~ for ~~one year~~. ~~This lets you run a cluster of two nodes for one year, and you~~ can ~~continue to~~ use a single scheduler instance forever at no charge.		* When you download Obsidian, it automatically obtains a free license key, which gives you one free license for permanent use. We'd be happy to have you evaluate Obsidian clustering, so just reach out to us and we'll grant you a second instance on the same key for a few months. You can use a single scheduler instance forever at no charge.
	* Running the admin web app without scheduler does not require a license when used in conjunction with licensed instances.		* Running the admin web app without scheduler does not require a license when used in conjunction with licensed instances.
	* All standard licenses are ''floating'', meaning they are not restricted to particular hardware and can be moved around as needed.		* All standard licenses are ''floating'', meaning they are not restricted to particular hardware and can be moved around as needed.

Craig at 20:23, 18 July 2023

2023-07-18T20:23:40Z

← Older revision		Revision as of 20:23, 18 July 2023
Line 20:		Line 20:

	=Nodes=		=Nodes=
	Nodes are individual instances of Obsidian scheduler. Nodes can be running standalone, within the admin web app or embedded in an existing JVM application. Nodes typically are deployed one per host, but Obsidian supports multiple nodes per host. Each running host uses the hostname to designate the node running each scheduled instance of a job. Subsequent instances on the same host will suffix an ordinal to the end of the hostname. Optionally, you can specify a configuration property (see [[Advanced Configuration]]) or provide a System property (see [[~~https://wiki.obsidianscheduler.com/docs/~~Getting_Started#Setting_Host_Names\|Getting Started]]) choosing the host designator you wish to use.		Nodes are individual instances of Obsidian scheduler. Nodes can be running standalone, within the admin web app or embedded in an existing JVM application. Nodes typically are deployed one per host, but Obsidian supports multiple nodes per host. Each running host uses the hostname to designate the node running each scheduled instance of a job. Subsequent instances on the same host will suffix an ordinal to the end of the hostname. Optionally, you can specify a configuration property (see [[Advanced Configuration]]) or provide a System property (see [[Getting_Started#Setting_Host_Names\|Getting Started]]) choosing the host designator you wish to use.

	No extra work, special configuration or administration is required to add nodes. Simply setup the environment, ensure a node license is available and start it up. The same holds true for shutting down.		No extra work, special configuration or administration is required to add nodes. Simply setup the environment, ensure a node license is available and start it up. The same holds true for shutting down.

Craig at 20:22, 18 July 2023

2023-07-18T20:22:50Z

← Older revision		Revision as of 20:22, 18 July 2023
Line 20:		Line 20:

	=Nodes=		=Nodes=
	Nodes are individual instances of Obsidian scheduler. Nodes can be running standalone, within the admin web app or embedded in an existing JVM application. Nodes typically are deployed one per host, but Obsidian supports multiple nodes per host. Each running host uses the hostname to designate the node running each scheduled instance of a job. Subsequent instances on the same host will suffix an ordinal to the end of the hostname. Optionally, you can specify a configuration property (see [[Advanced Configuration]]) or provide a System property (see [[~~Getting Started\|~~https://wiki.obsidianscheduler.com/docs/Getting_Started#Setting_Host_Names]]) choosing the host designator you wish to use.		Nodes are individual instances of Obsidian scheduler. Nodes can be running standalone, within the admin web app or embedded in an existing JVM application. Nodes typically are deployed one per host, but Obsidian supports multiple nodes per host. Each running host uses the hostname to designate the node running each scheduled instance of a job. Subsequent instances on the same host will suffix an ordinal to the end of the hostname. Optionally, you can specify a configuration property (see [[Advanced Configuration]]) or provide a System property (see [[https://wiki.obsidianscheduler.com/docs/Getting_Started#Setting_Host_Names\|Getting Started]]) choosing the host designator you wish to use.

	No extra work, special configuration or administration is required to add nodes. Simply setup the environment, ensure a node license is available and start it up. The same holds true for shutting down.		No extra work, special configuration or administration is required to add nodes. Simply setup the environment, ensure a node license is available and start it up. The same holds true for shutting down.

Craig at 20:22, 18 July 2023

2023-07-18T20:22:20Z

← Older revision		Revision as of 20:22, 18 July 2023
Line 20:		Line 20:

	=Nodes=		=Nodes=
	Nodes are individual instances of Obsidian scheduler. Nodes can be running standalone, within the admin web app or embedded in an existing JVM application. Nodes typically are deployed one per host, but Obsidian supports multiple nodes per host. Each running host uses the hostname to designate the node running each scheduled instance of a job. Subsequent instances on the same host will suffix an ordinal to the end of the hostname. Optionally, you can specify a configuration property (see [[Advanced Configuration]]) or provide a System property (see [[Getting Started]]) choosing the host designator you wish to use.		Nodes are individual instances of Obsidian scheduler. Nodes can be running standalone, within the admin web app or embedded in an existing JVM application. Nodes typically are deployed one per host, but Obsidian supports multiple nodes per host. Each running host uses the hostname to designate the node running each scheduled instance of a job. Subsequent instances on the same host will suffix an ordinal to the end of the hostname. Optionally, you can specify a configuration property (see [[Advanced Configuration]]) or provide a System property (see [[Getting Started\|https://wiki.obsidianscheduler.com/docs/Getting_Started#Setting_Host_Names]]) choosing the host designator you wish to use.

	No extra work, special configuration or administration is required to add nodes. Simply setup the environment, ensure a node license is available and start it up. The same holds true for shutting down.		No extra work, special configuration or administration is required to add nodes. Simply setup the environment, ensure a node license is available and start it up. The same holds true for shutting down.

Craig at 22:17, 17 November 2021

2021-11-17T22:17:06Z

← Older revision		Revision as of 22:17, 17 November 2021
Line 31:		Line 31:
	After the lease time elapses (configured in [[Admin Scheduler Settings\|scheduler settings]] screen, or in the key proxy properties file), it is available for other nodes. In the meantime, if the instance goes down and you attempt to start a node in another location, the license will not be available for lease. If you restart the node in the same location, it will reacquire the same license.		After the lease time elapses (configured in [[Admin Scheduler Settings\|scheduler settings]] screen, or in the key proxy properties file), it is available for other nodes. In the meantime, if the instance goes down and you attempt to start a node in another location, the license will not be available for lease. If you restart the node in the same location, it will reacquire the same license.

	You can customize the leasing settings in the [[Admin Scheduler Settings\|scheduler settings]] screen under the ''License'' category. Key settings include ''clientKeyRefreshMinutes'' and ''clientKeyLeaseLengthMultiple'', which are documented on that page. Changing these settings allows you to find the right balance between tolerance for Internet outages, and the ability to deploy a used Obsidian license to a new installation ~~which having to wait~~ for locked licenses to expire.		You can customize the leasing settings in the [[Admin Scheduler Settings\|scheduler settings]] screen under the ''License'' category. Key settings include ''clientKeyRefreshMinutes'' and ''clientKeyLeaseLengthMultiple'', which are documented on that page. Changing these settings allows you to find the right balance between tolerance for Internet outages, and the ability to deploy a used Obsidian license to a new installation, affecting the length of time for locked licenses to expire.

	== Your License Key ==		== Your License Key ==

Craig at 14:34, 17 November 2021

2021-11-17T14:34:51Z

← Older revision		Revision as of 14:34, 17 November 2021
Line 24:		Line 24:
	No extra work, special configuration or administration is required to add nodes. Simply setup the environment, ensure a node license is available and start it up. The same holds true for shutting down.		No extra work, special configuration or administration is required to add nodes. Simply setup the environment, ensure a node license is available and start it up. The same holds true for shutting down.

	Nodes can be gracefully brought down out of the pool, allowing them to complete any in-process work while no longer claiming and ~~proccessing~~ any subsequently scheduled work. Graceful shutdown in the web embedded scheduler, either in the web admin app or your own web app, requires using the container's shutdown. Starting and stopping a standalone version of the scheduler uses a listener port to support graceful shutdown. See the [[Getting Started]] guide for details.		Nodes can be gracefully brought down out of the pool, allowing them to complete any in-process work while no longer claiming and processing any subsequently scheduled work. Graceful shutdown in the web embedded scheduler, either in the web admin app or your own web app, requires using the container's shutdown. Starting and stopping a standalone version of the scheduler uses a listener port to support graceful shutdown. See the [[Getting Started]] guide for details.

	== License Leasing ==		== License Leasing ==

Craig: /* License Verification */

2019-10-28T13:14:50Z

License Verification

← Older revision		Revision as of 13:14, 28 October 2019
Line 9:		Line 9:

	= License Verification =		= License Verification =
	The default Obsidian license requires a a live Internet connection to validate clustered scheduler instances~~. If you are running a single instance, this check is bypassed~~.		The default Obsidian license requires a a live Internet connection to validate clustered scheduler instances.

	Obsidian's license verification is built to handle sporadic outages to Internet connectivity. Customers using paid licenses can generally expect grace periods of over 48 hours during which Internet connectivity is not available. Obsidian will automatically attempt to re-validate your license key on a schedule based on configurable settings which control [[#License Leasing\|License Leasing]]		Obsidian's license verification is built to handle sporadic outages to Internet connectivity. Customers using paid licenses can generally expect grace periods of over 48 hours during which Internet connectivity is not available. Obsidian will automatically attempt to re-validate your license key on a schedule based on configurable settings which control [[#License Leasing\|License Leasing]]

Craig: /* License Verification */

2019-10-28T13:14:37Z

License Verification

← Older revision		Revision as of 13:14, 28 October 2019
Line 17:		Line 17:
	Obsidian also supports hardware licenses. These are tied to deployment hardware and are not floating. Contact [[Contact Carfey Software\|Carfey Software]] for further details.		Obsidian also supports hardware licenses. These are tied to deployment hardware and are not floating. Contact [[Contact Carfey Software\|Carfey Software]] for further details.

	As of Obsidian 2.1, Obsidian can also be run under a site license. When Obsidian is run under a site license, no Internet connectivity and verification is required and ~~an unlimited~~ number of nodes are permitted within the licensed organization. Contact [[Contact Carfey Software\|Carfey Software]] for further details.		As of Obsidian 2.1, Obsidian can also be run under a site license. When Obsidian is run under a site license, no Internet connectivity and verification is required and a specific maximum number of nodes are permitted within the licensed organization based on prior agreement. Contact [[Contact Carfey Software\|Carfey Software]] for further details.

	=Nodes=		=Nodes=

Carfey: /* Your License Key */

2016-07-01T17:42:17Z

Your License Key

← Older revision		Revision as of 17:42, 1 July 2016
Line 35:		Line 35:
	== Your License Key ==		== Your License Key ==

	You can find your license key in [[Admin Scheduler Settings ~~4.0~~\|Scheduler Settings]] as shown below.		You can find your license key in [[Admin Scheduler Settings\|Scheduler Settings]] as shown below.

	Obsidian will automatically acquire your free single node license and a second trial clustering node license which is valid for a year. If you are converting your trial backup node license to a paid license or are purchasing additional nodes, you can obtain your license key from the location show below.		Obsidian will automatically acquire your free single node license and a second trial clustering node license which is valid for a year. If you are converting your trial backup node license to a paid license or are purchasing additional nodes, you can obtain your license key from the location show below.

	[[Image:ClientKey_4.0.png]]		[[Image:ClientKey_4.0.png]]