Licensing FAQs

• How does the Relibase+ licensing system work?
• How do I install the Relibase+ server licence key?
• When registering my client site, I am asked to enter a Masterkey. What is this?
• How do I diagnose problems with my Relibase+ licence?
• I have spare licences yet my browser always displays the message "The client browser is not registered. There are no more client licenses available on this server."

How does the Relibase+ licensing system work?



There are two components to the Relibase+ package - the server and client. A standard Relibase+ licence will allow you to run a single Relibase+ server on Linux on a single designated computer. This server can then be accessed via the client package, which should ideally be installed on each user's workstation. Access to the Relibase+ server is controlled via client workspaces:

For limited user workspace licences, Relibase+ client workspaces are user and browser-locked; use of a specific browser by a user on a single machine will require the use of one of your Relibase+ licences.

For unlimited user workspace licences, users have the ability to log on and log off their workspace accounts so that workspaces can be accessed from different browsers on different machines. This functionality is not available to users with limited numbers of workspaces.

How do I install the Relibase+ server licence key?

The Relibase+ 3.0 licence key file "relibase_licence.dat" should be copied into the $RELIBASE_ROOT/etc directory of your server installation.

When registering my client site, I am asked to enter a Masterkey. What is this?

When registering a client site with a Relibase+ licence for only a limited number of seats, each client must give the Masterkey code from the Relibase+ server. This Masterkey can be identified by running the command

$RELIBASE_ROOT/bin/relihost.x

after first sourcing the Relibase+ environment.



How do I diagnose problems with my Relibase+ licence?

If the Relibase+ server will not start, the problem may be due to your licence file. To determine if this is the case, start the Relibase+ server with the command:

relibase -server start serverlog=server.log

This will create a file called server.log that should contain more information about why the server is failing to start. You can check your licence file details with the command:

relibase -licence_info

This should inform you if the licence file can be correctly read, and what expiry date and workspace limit it was created with.

If problems persist, please send the server.log file, the -licence_info output and the output of "hostid" (for linux users) or "sysinfo -s" (for IRIX users) to support@ccdc.cam.ac.uk who should be able to help further with your query.

I have spare licences yet my browser always displays the message "The client browser is not registered. There are no more client licenses available on this server."

This error can occur if you are using your own Apache web server with Relibase+ 2.1 or 2.2 and the Relibase+ environment is not correctly being passed to it.

In order to resolve this, ensure that LD_LIBRARY_PATH in your Apache environment contains $RELIBASE_ROOT/lib (this can be achieved by ensuring this is in your environment when Apache is started, or with the Apache SetEnv and PassEnv directives).

Alternatively, if you have updated from Relibase+ 2.0, you can revert to the old licensing executable that does not require this environment. This can be done by copying $RELIBASE_ROOT/reli-cgi/relilicence.2.0.0 back to replace $RELIBASE_ROOT/reli-cgi/relilicence (doing so will remove the ability to recognise case differences in workspaces that was introduced in 2.1).