Difference between revisions of "Licenses & Nodes"

From Obsidian Scheduler
Jump to navigationJump to search
m
Line 1: Line 1:
Obsidian scheduler requires a licence for each instance running the scheduler engine. Admin web app without scheduler does not require licensing when used in conjunction with licensed instances. Licences are floating meaning they can be used on any one host at a time.  Running instances must have access to the Internet to lease and verify the licence.  Obsidian also provides a licence proxy should you wish to restrict Internet access to a single server.  Obsidian instances can then be directed to the deployed licence proxy.
+
Obsidian scheduler requires a licence for each instance running the scheduler engine. Admin web app without scheduler does not require licensing when used in conjunction with licensed instances. Licences are floating, meaning they can be used on any one host at a time.  Running instances must have access to the Internet to lease and verify the licence.  Obsidian also provides a licence proxy should you wish to restrict Internet access to a single server.  Obsidian instances can then be directed to the deployed licence proxy.
  
 
Contact [[Contact Carfey Software|Carfey Software]] for licensing pricing.
 
Contact [[Contact Carfey Software|Carfey Software]] for licensing pricing.

Revision as of 17:59, 21 June 2011

Obsidian scheduler requires a licence for each instance running the scheduler engine. Admin web app without scheduler does not require licensing when used in conjunction with licensed instances. Licences are floating, meaning they can be used on any one host at a time. Running instances must have access to the Internet to lease and verify the licence. Obsidian also provides a licence proxy should you wish to restrict Internet access to a single server. Obsidian instances can then be directed to the deployed licence proxy.

Contact Carfey Software for licensing pricing.

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 provide a System property (see 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 licence 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.

Licence Leasing

When an Obsidian instance is validated, a licence is locked the the leasing node. Other nodes or instances will not be able to use this licence until the lease expires. After the lease time elapses (configured in System tab, 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 licence will not be available for lease. If you restart the node in the same location, it will reacquire the same licence.