Licences

In order to use Reality, you must have licences for your users and any optional features you wish to use. If you wish, you can install an evaluation version - this is not for commercial use (it gives you only three user licences and none of the optional features). For a full installation, you will need the following software keys:

• A Serial Number Key for the date on which you intend to install the software. This is valid for installation only on the specified date and the two days following.
• A Customer ID.
• A version number key for the version of Reality that you are installing.
• A software key for the required number of user licences.

When you purchase your software keys, you will be supplied with a file that contains the following standard keys:

ALL 1.4.
WORDMATE 2.1.
ISIS Package.

Note, however, that your Reality installation may not include this software.

User licences

User licences are used, not only to allow users to log in to a Reality database, but also for most features that require a process to run on the database. These include printing (despoolers), background processes (TIPH), SQL, RealWeb and Remote DataBasic. If you intend using any of these features, you must make sure that you have sufficient user licences.

Optional features

The following optional features are only enabled if you have installed the corresponding software key:

Database isolation

This feature makes it possible to run multiple independent instances of the same version of Reality. Each instance is licensed separately: you must purchase the required number of user and other licences specifically for that instance. See Database Isolation for more details.

Installing software keys

There are a number of ways of installing your software keys:

• You can install them as part of the Reality installation process - see the UNIX or Windows Installation Guide as appropriate.

• If installing on a UNIX host, you can use the installkeys host utility.

• If installing on a Windows host, you can use the Reality installation utility. Run the Windows Control Panel, choose Add or Remove Programs and select Reality from the list. Then click Change/Remove and from the list of Reality versions, choose the one on which you wish to install the keys. Click the Install Keys button and then follow the procedure described in the Reality on Windows Installation Guide.

• You can use the Install_Key host utility.

  Note

  Install_Key does not install serial numbers. To install serial number keys, on UNIX use installkeys or, on Windows the Reality installation utility. Alternatively, on both platforms you can use the Install_SN host utility.

Reserved licences

If you wish, you can assign some of your user licences for particular purposes by setting host environment variables to the number of licences required:

Environment Variable	Purpose
REALRESERVERLTYXDSP	Printing (despoolers)
REALRESERVEROSFS	Remote file access
REALRESERVESQLSRVR	SQL/ODBC and SQL/JDBC
REALRESERVERWSRVR	RealWeb
REALRESERVERSCSRVR	Remote Basic

See also the topic Reserved Licences in the section Reality Configuration on the Host.

Database configuration

User licences can be shared between all the Reality databases on the host system (or those associated with a Reality instance: see Database Isolation). If you wish, you can configure each database to limit the number of connections, and thus the maximum number of user licences that can be used on that database. There are three parameters you can set:

MaxPortNum This sets the maximum number of "real" ports; that is, the number of ports to which PLIds can be mapped in the database's devices file. A PLId that is configured in this way will always connect using the associated port. The default is 400.

NumPseudoPorts This sets the number of virtual ports - those that are available for use by any user or process. Virtual ports number from MaxPortNum + 1 and are allocated on a first-come-first-served basis. By default, there are 400 virtual ports.

NumConnections The maximum number of connections to the database (default, 128).

Licence expiry

In general, your user licences will be valid for only a limited period. You can find out when your user licences will expire in the following ways:

• A licence view special file called REALITY-LICENCE is provided in the SYSMAN account. This can be viewed by listing its contents with the following TCL command:

  LIST REALITY-LICENCE

  If you prefer, you can create your own licence view special file with the MAKE-SPECIAL TCL command.

• View the installed software keys with the show_key host command. If you specify the -e option, the expiry dates will be displayed.

Starting 60 days before expiry, warnings will be logged in the daemon log, so that you can renew your licences in good time. These warnings will appear with increasing frequency as the expiry date approaches.

Although it is not recommended, if you wish you can suppress the expiry warnings by running the killreal host command with the -w option. You will be prompted for the part number of the licences concerned and for your user name - the action is logged in the daemon log. To do this, you must be logged on as the super-user (UNIX) or a user with administrator privileges (Windows).

Extending your licences - grace period

If for any reason, your licences expire before you receive the new ones, you can enable a licence extension (grace period) for any user licences that have expired or are about to expire, starting immediately. This is done by running the killreal host command with the -g option, and then restarting the central daemon (UNIX) or Reality services (Windows) - see Starting and Stopping Reality.

To instantiate grace on UNIX:

$killreal
$killreal -g
$realstart

To instantiate grace on Windows:

>killreal -g
>realserv -e
>realserv -s

The extension ends after 20 days, or 10 days after the licences expire, whichever is the sooner. Therefore if the keys have already expired you only have 10 days from the expiry date in order to invoke the grace period. Unexpired licences are not affected.