Knowledge Base

• Print
• Save to list
• E-Mail
• Subscribe

This article is intended to provide answers to frequently asked questions about Concurrent Licenses for Deep Exploration

For the Right Hemisphere License Server Pack, please click here: http://www.righthemisphere.com/support/kb/index.php?article=1368

Concurrent Licenses are deployed across a shared Network, allowing a specific number of uders to be actively using Deep Exploration at any point in time.

1.       What are my licensing options when purchasing Deep Exploration?

There are 3 different licensing options:
• Perpetual – requires purchase of annual maintenance
• 3 year subscription – includes maintenance
• 5 year subscription – includes maintenance

2.       What are the benefits of the Concurrent License?

Customers with a number of Deep Exploration users can benefit from purchasing Concurrent Licenses. These can be shared among a group of people that use Deep Exploration on a shared network, but do not require access at all times. For those users who require access at all times, a Fixed License is the best fit. This license is "locked" to a particular machine.

3.       Can I run two different versions of Deep Exploration on the same computer?

Yes. When installing a new version of Deep Exploration on a computer with Deep Exploration already installed, you will need to specify a separate installation directory during the installation wizard process.

4.       What versions of Windows can I use with Right Hemisphere’s Reprise License Manager?

Right Hemisphere’s Reprise Manager 6.0 (RLM) is compiled to run on all Windows 32bit and Windows 64 bit machines. This includes Windows Server 2000, 2003, Windows XP, and Windows Vista. 

5.       Can I use a Concurrent (Network) License over the Internet?

Concurrent Licenses are only supported by the Right Hemisphere License Server. The License Server requires a host server to be available via a Local Area Network (LAN). If you want to use a concurrent License over the Internet, then a Virtual Private Network (VPN) connection is required.

6.       What is required in order to use Concurrent Licenses for Deep Exploration?

For Customers with groups of Deep Exploration users, the Right Hemisphere license server is a perfect fit. Once the number of concurrent licenses is determined, Right Hemisphere will distribute the software necessary. This includes a zip file executables, a license file and an Installation Guide. Deployment is simple and straightforward.

All that is required is a machine with a Windows operating system connected to the network that serves the Deep Exploration users.

7.       What are the minimum requirements for the Right Hemisphere License Server?

The machine where the network license utility is installed must have a Windows operating system.

8.       Can I use the Right Hemisphere License Server on a virtual machine or virtualization software?

Yes, we now provide support for hosting your license server on a virtual machine. Please refer to the 'Network License Installation & Deployment' knowledgebase article for further information:

http://www.righthemisphere.com/support/kb/index.php?article=1368

9.       When will my 3 year or 5 year Network License expire?

Your concurrent License will expire from the date of purchase. For example, if you purchase a 3 year Concurrent License on June 25th 2008, then your license will expire 3 years from this date, i.e. June 26th 2011. More information about your license expiration date can be found under the main menu > Help > About Deep Exploration.

10.   Is there support for a redundancy or failover license server to host the Concurrent licenses?

Yes, however the redundancy or failover license server needs to be on the same network.

11.   Where do I get my license file?

Right Hemisphere creates the license file (*.lic) and will be distributed after purchasing Deep Exploration Concurrent licenses.

12.    How do I use the Right Hemisphere license server across a firewall?

If you want to serve licenses across a firewall, generally you will need the license server to have a known port number in order to allow your firewall to pass requests on the port.  The network license server itself is always at a known port number (contained in the license file on the SERVER or HOST line).  Typically, the network license starts up all the ISV servers with dynamic port numbers which are not known before startup time.

However, it is possible to have license server assign fixed port numbers to any of the ISV servers.  In order to do this, you need to specify the port number for the ISV server on the ISV line.  The port number is the fourth parameter in the isv line:

        ISV isvname options-file port-number

 Once you have specified the port number, instruct your firewall to allow connections to both the port number on the SERVER line (for rlm) and the port numbers on ISV line.

13.    What product is being used for the Right Hemisphere License Server? 

We are using Reprise License Manager (RLM) from Reprise Software Inc. http://www.reprisesoftware.com/

14.    What types of reporting metrics is there, such as number of concurrent users, max number at any one time.

The RLM system includes a reporting function from the license server. More information about accessing the report can be found in the 'concurrent License Installation and Deployment Guide' PDF, available here: http://www.righthemisphere.com/support/kb/index.php?article=1368

15.    What are the requirements from Right Hemisphere for using your software globally once purchased from within the United States?

Global usage is generally fine. Specifically:

The US Department of Commerce has all of Right Hemisphere's products classified under Export Control Classification Number ("ECCN") 5D002 and are eligible for export under License Exception ENC "unrestricted", which means they can be exported to all destinations except those countries designated by the U.S. Government as state-sponsors of terrorism.

16.   On Windows, RLM fails to start the ISV server with a select() error.  What's wrong?

Reprise has had reports on a very limited number of systems that rlm fails to start the ISV server, with errors similar to the following written to the debug log (note: the ISV name will be your ISV name, not necessarily "demo"):

03/16 04:12 (demo) select() failure: Unknown error
03/16 04:12 (demo) Out of file descriptors: Cannot clone communications handle: Unknown error
<last error repeats 10 times>
03/16 04:12 (demo) Too many errors on main socket, exiting

This can be caused by corruption of some values in the Windows registry. Reprise has no reason to believe that RLM is responsible for this registry corruption. Microsoft has published the following article on how to correct the registry when this occurs. Note that the error message indicating the problem is different in the article than the RLM error message indicating the problem, but the underlying cause is the same.
http://support.microsoft.com/default.aspx?scid=kb;en-us;817571