Teach Yourself e.net - Syspro

Licensing
class against them. For example, if a class allows four concurrent users, there may be ten
people in the sales department of an organization, and at any point in time six are always
on the road. Specifying this class against all ten operator codes means that whichever four
are in the office can logon and use the web-based applications.
When a member of a class attempts to logon to the web-based applications it is detected
that they are a member of a class, and instead of checking the licensing for the operator
code, all the checking s done for the class. A check is made in the state file to see how
many existing members of this class are logged on. If it is less than the number of
concurrent users for this class the operator is given their own UserID (which is added to
the state file) and they are allowed to logon. Whenever this operator accesses a business
object a timestamp is updated against their entry in the state file. When operators that are
members of a class logout their UserID and state information is removed from the state
file.
When a member of the class attempts to logon and the number of members of this class,
already in the state file, is equal to the number of allowed concurrent users, a check is
made to see which member of the class has the greatest period of inactivity. If this period
of inactivity is greater than the timeout value set against this class, then the existing user is
logged out and the new user is logged on. If the period of inactivity was less than the
timeout value the new operator is prevented from logging on and a message to this affect
is passed back to them.
To manage licensing for SYSPRO e.net solutions web-based applications you implement
either "Named User", "Guest/anonymous", or "Class" licensing (or a combination of all
three methods).
The advantages of the e.net solutions licensing are three fold:
a. A greater number of users can have access to the system.
b. Licensing is optimized across the system on a per functional area basis.
c. Both the above result in reduced costs and greater customer value.
The number of licenses may therefore be viewed as a limited resource that must be
appropriately managed. When managed correctly, all users will receive an adequate level
of service from the system.
8.1.4. Installing and Configuring License.xml
8.1.4.1. Importing the License.xml file
The e.net solutions license is always provided in a file called License.xml. This has
been done to simplify the creation and maintenance of the e.net solutions license. There
are many e.net solutions functional areas, and each one could have a different number of
licensed users. By providing an import for this license file it is impossible to make a
8–7