About system users with special licensing

These users are special cases:

• The 'sa' user - The 'sa' user does not require licensing. By default, this user has the ability to open any form and run any process in the site. The 'sa' user should be reserved for system administration tasks and should not be used to run multi-site processes.

  Only one instance of the 'sa' user can be logged in at any time, even under a concurrent license or a usage-tracking license. With a usage-tracking license, form and IDO consumption is not tracked for the 'sa' user.

  Do not assign any license modules to this user.

• Multi-session or concurrent user - This capability is designed for web service automation scenarios, where an application that is accessing the IDO layer can have multiple threads that process simultaneously, with each thread sharing the same configured multi-session user.

  Under a named user license, each standard user is only allowed one session per site. The multi-session user gives an administrator one user that can have multiple concurrent sessions. Under a concurrent license, all users except 'sa' can have multiple concurrent sessions. Therefore the multi-session user provides no real significance in a concurrent license environment.

  When the multi-session user is assigned to a license module, the tokens consumed are the number of concurrent sessions defined for that user. In other words, if the multi-session user is defined by the license to allow seven concurrent sessions, assigning that user to a module consumes seven license tokens for that module. Multi-session users and their concurrent session limits are defined in the license document generated by the vendor. You cannot create or modify a user to be a multi-session user.

  Multi-session users are shown in the Multi-Session Users tab on the License Management form.

• Infor ION - ION uses a direct connection to the application when retrieving BODs, so no license token is required.
• Infor Framework services - Framework services such as the Replicator use '$service' sessions to connect to the application. The '$service' session does not consume a license.