Leasing floating licensees for off-line usage
Posted: Wed Mar 02, 2011 3:16 am
Hi
My company has purchased a number of floating licenses of OxygenXML. We are currently changing our team to use laptops over desktops and thus make our working arrangements more flexible. Part of this flexibility is for users to work off-line, off-site at different work locations and from home. Unfortunately, we will not have network access when off-line.
I would like to know if there is a way to use floating licenses off-line (not connected) from the network. One solution would be if the OxygenXML license server can 'lease' licenses to individual users. I have seen this model used with other designer tools such as Enterprise Architect.
Here, the license server gives a 'leased' license for a fixed time (say three days to allow use at home on weekends). Every time a user opens OxygenXML, the lease should be refreshed so it is three days from the last connection to the license server. During the lease the license is not available to any other user. When the lease expires, the license returns to the license pool available for other users.
In fact, we have setup Enterprise Architect with two license pools with different license lease periods of zero and three days. The 'zero' lease period for who always expect to be online. The user can easily select which pool they take a license.
What can you suggest?
My company has purchased a number of floating licenses of OxygenXML. We are currently changing our team to use laptops over desktops and thus make our working arrangements more flexible. Part of this flexibility is for users to work off-line, off-site at different work locations and from home. Unfortunately, we will not have network access when off-line.
I would like to know if there is a way to use floating licenses off-line (not connected) from the network. One solution would be if the OxygenXML license server can 'lease' licenses to individual users. I have seen this model used with other designer tools such as Enterprise Architect.
Here, the license server gives a 'leased' license for a fixed time (say three days to allow use at home on weekends). Every time a user opens OxygenXML, the lease should be refreshed so it is three days from the last connection to the license server. During the lease the license is not available to any other user. When the lease expires, the license returns to the license pool available for other users.
In fact, we have setup Enterprise Architect with two license pools with different license lease periods of zero and three days. The 'zero' lease period for who always expect to be online. The user can easily select which pool they take a license.
What can you suggest?