PreviousInstalling AS Licenses Development System UsersNext"

Chapter 3: Administering AS Licenses

This chapter describes how to administer AS Licenses.

3.1 Monitoring License Use

You can monitor the use of AS Licenses on your system using the AppTrack license administration utility. To do this, type:


You will be asked to enter your password. A menu is then displayed.

Select option 2 (License Summary) from the menu. A report is displayed showing the number of licenses installed, and the number of copies of an application running at that moment.

The report shows all installed Application Server applications. Each different application is listed separately, together with the directory in which the Application Server is installed. Entries that follow **Developer Usage refer to AS Licenses that have been automatically installed by a Micro Focus Development System. For each Development System License unit, five Development AS License units are installed on the AS License database. These licenses can neither be installed nor uninstalled using the license administration utility, although they appear in the License List (displayed by selecting option 1 from the license administration utility menu), marked as Developer Usage. The majority of systems do not have a Micro Focus Development system installed, so Developer Usage entries are not usually displayed.

3.2 Statistics collection

It can be useful, for statistical purposes, to take a snapshot of license use at regular intervals over a period of time and get an average number of license uses at the end of the data collection. To do this, use the command:

$COBDIR/asadmin stats p f

where the parameters are:

p The period, in seconds, between each statistics collection
n The number of statistics collections to make

For example, the command:

$COBDIR/asadmin stats 60 10

takes 10 snapshots, with 60 seconds between each.

By default, the statistics are displayed on the screen. It is usually more useful to direct them into a file; for example:

$COBDIR/asadmin stats 60 10 >> userfile

As the output file is fixed format, it can be further processed or edited into a different format for presentation purposes.

3.3 Special Action On No-license Condition

If you have more users trying to run your application than you have licenses installed, there will be times when some users will receive the response that there are no more license units available at that moment. You can monitor how often this happens, so that you can determine how many additional AS Licenses you need to purchase.

To help you monitor no-license conditions, AppTrack runs the shell script /var/mfaslmf/nolicense every time that it is unable to satisfy a license unit request. A single parameter is passed to the script; this parameter identifies the directory of the installed Application Server, so that different applications can be separately identified. The script then writes the name of the directory, and the date and time at which the attempt to run failed, to the file /var/mfaslmf/USERLOG.

You can edit the nolicense script to your requirements. For example, the script contains a line that is commented out, that demonstrates how each time the script is invoked, a message could be mailed to a specified user.

If you do not want to use this monitoring facility, you can delete the nolicense script.

3.4 Troubleshooting

If users cannot run an application even though AS Licenses are installed, check that the licenses were installed for the correct Application Server. Start , and select option 1 (License List).

If the licenses are listed correctly, check that the setting you are using for the Application Server directory matches the correct application.

If you have installed to the wrong Application Server, uninstall the licenses, set COBDIR to the correct directory, and reinstall the licenses to the Application Server.

If you are installed to the correct directory, but you still cannot run the application, then try selecting option 6 (Reinitialize Licensing) of the license adminstration utility. If this fails to work, then you should contact your application supplier and explain the problem.

3.5 Overdraft

If you intend to run more than one copy of your application at the same time, you must ensure that you have sufficient license units to cover the number of concurrent users. During an exceptional period, for example, at year-end, you might need to run more concurrent copies of your application than usual. You need to order sufficient AS licenses to cover this situation. However, to help you cope with unexpected fluctuations in use, and to give you time to purchase additional licenses, AppTrack has a built-in limited overdraft facility. The first time that an attempt is made to run more concurrent copies of an application than there are applicable license units, the overdraft facility is started. This enables you to run additional copies of the application for a period of thirty days. After this time, the licensing reverts to standard use. The number of additional overdraft copies that you can run depends on the number of license units installed for the application:

License units
Overdraft License
units available
1 0
2 - 9 1
10 - 19 2
20 - 29 3
30 - 39 4

For each further ten license units installed, an additional overdraft license becomes available.

Copyright © 1999 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.

PreviousInstalling AS Licenses Development System UsersNext"