jBASE Licensing Configuration

This section explains the required configuration to be done for jBASE Licensing.

License Server Configuration

All the configuration settings for the license server are held in a properties file, that is, jlicensing.properties. This file is located in the %JBCRELEASEDIR%/properties folder. The following settings are available.

jSLIM Server Configuration

All the configuration settings for the jSLIM server are held in a properties file called jlicensing.properties, located in the $JBCRELEASEDIR/properties folder. The following settings are available.

jLicense Console configuration

The configuration settings of jLicense console is given below.

Environment Variables - JBASE_SVR_SESSION

On a machine with mixed enterprise and server licenses available, this variable indicates that a server license is required.

Values

Set or unset

Default

Unset

Setting

On sites with both server and enterprise licenses installed, an enterprise license will be assumed unless JBASE_SVR_SESSION is set to 1. With server only licenses installed, JBASE_SVR_SESSION must be set in order to obtain a license. Failure to do so will res- ult in a licensing error. With enterprise only licenses installed, setting this environment variable will not allow a license to be allocated and a license error will be produced.

Stand in Processing

The System Licence Manager has a stand in capability whereby if contact is lost with the Licence Server, licence requests can still be processed for a limited time to allow recovery. This is known as grace period.

The standby processing is designed to be resilient, such that the users will not notice any change in system behaviour. Because of this, a notification mechanism has been included to send a message to inform the system administrator (see below).

Operation

The operational criteria when contact is lost with the Licence Server are as follows:

If an RMI request fails, messages are displayed in the jSlim window as below:

Connecting to Licence Server......> ERROR: RemoteException: Connection refused to host: 127.0.0.1; nested exception is: java.net.ConnectException: Connection refused: connect 
jSlimServer has lost contact with Licence Server!!! setLicenses() Standby Processing (239 mins left) 
Please restart Licence Server to recover before time expires. 

This is repeated every 10 seconds (default refresh time) and will allow licence allocation as normal for up to 4 hours during which time the Licence Server must be recovered. After that time no new licences will be issued, and the message:

Stand in processing period now expired, Licence Server must be restarted.

As soon as the Licence Server has been restored, normal processing resumes without interruption (unless the 4 hour grace period has expired).

Notification Scheme

If any failure is detected, a message will be sent to the specified user using a notification scheme. This is done using the MSG command on Windows or /etc/wall command on Unix. The message is sent a maximum of three times to ensure it is seen and then suppressed.

A sample message is “jSlimServer has lost contact with Licence Server!!!”.

To configure this, three entries have been added to the jslim.properties file:

jslim.warn.path = C:\\WINDOWS\\SYSTEM32\\MSG jslim.warn.user = * 
jslim.warn.text = jSlimServer has lost contact with Licence Server!!!

The .path option specifies the path to the notification program to use. Ensure that this is correct for the target system. This can be set as:

C:\\WINDOWS\\SYSTEM32\\MSG  for Windows and

/etc/wall for Unix.

It is blank by default, which disables the warning message display.

The default .user option is to broadcast the warning to all logged on users. It is strongly recommended that this option be updated to either specify a single Windows user name, or to specify a text file pathname of multiple users as @pathname. See Windows help on MSG for more details. On Unix using /etc/wall, the .user option must be left blank.

The .text message displayed is shown above and can be modified.

Logging and Diagnostics

A logging mechanism is provided in both jLicServer and jSlimServer to write diagnostic and progress messages to a log file. This is created in $JBCRELEASEDIR/logs directory as jslimserver.log and jlicserver.log.

Logging is controlled by the ‘log.level’ parameter (see Configuration above) and is normally effectively off by being set to zero. This default setting records the starting and stopping of the daemons and any fatal errors that occur. The levels range from1 to 7, with increasing detail recorded as the value goes up. Not all levels are currently used. The levels imple- mented are shown below.

jLicServer

The licence server is ‘driven’ by RMI requests from jSlimServer every 10 seconds, rather than sitting in a loop polling for requests. Each request is logged at various levels of detail as follows:

• 0 - Logs the starting and stopping of the daemons and any fatal errors that occur.
• 4 - Logs the occurrence of the request and the number of licences free:

  02/01/07 13:58:39 Request from jSlimServer
  02/01/07 13:58:39 :Static Licences Free:
  02/01/07 13:58:39 :Product ID 1 = 15
  02/01/07 13:58:39 :Product ID 13 = 10

• 5 - Logs all of the users holding licences.

  02/01/07 13:58:39:ukdsk-swaters_4 (port number shown for Server licence)
  02/01/07 13:58:39:ukdsk-swaters_192.168.80.3 (host shown for Enterprise)

• 6 - Logs the Licence Metrics counts (not currently used).

  Therefore level 4 or 5 is recommended for this testing. You can edit the jlicensing.properties file, which is available in the %JBCRELEASEDIR%\config\ path and change the entry jLicensingSrv.log.level as required. This value is only read at startup of daemon.

jSlimServer

The jSlimServer issues request to licence server every 10 seconds. Each request is logged at various levels of detail as follows:

• 0 – Logs the starting and stopping of the daemons and any fatal errors that occur.
• 4 - The connection request is logged as follows:

  02/01/07 14:02:39 : Connecting to Licence Server > OK
  02/01/07 14:02:49 :2 ports found

• 5 - Each port with a licence is reported:

  02/01/07 14:02:49 : Port No. 4
  02/01/07 14:02:49 : Port No. 5 client:ukdsk-swaters_192.168.80.3