Copyright 2023 Alemba, ASM EOS 10.4
Limited Support/End of Life Capabilities
If you need to request a hotfix or support for these features, please contact Alemba Support
ASM Core, Nano, and the Alemba API will all consume a license when logged in as an analyst.
Users use the Self Service Portal to submit incidents, requests, or service orders. They do not require licenses. You can also log in to the Alemba API as a user without consuming a license.
Concurrent licensing is being deprecated and a named licensing model is being implemented. Please contact your Technical Account Manager or info@Alemba.com for more information on the timeline of this change.
Concurrent licenses may be used by any Analyst, limited to the number of licenses purchased. All Analysts have access to any license.
Concurrent licenses are only used by Analysts currently logged on to the system. When an Analyst logs out, the license goes back into the pool and can be used by another Analyst.
The concurrent licensing model has advantages and disadvantages.
✅
Flexibility: As licenses are not bound to specific Analysts, it is easy to add new Analysts.
✅
Maximum usage of licenses: A single license can be used by multiple Analysts, so you get more use out of one license.
❌
No guaranteed access: Licenses are used on a "first come, first served" basis, so you cannot guarantee access to specific Analysts/roles. This can be overcome using Coralling, as described in Corraling (Reserving) Licenses.
❌
Cost: Concurrent licenses cost more than named licenses.
All licenses are allocated to a single "default" corral when ASM Core is first installed. You can create new corrals, and allocate licenses to them. You can even associate session timeouts for particular license corrals so that an Analyst can remain logged in under the license only for the specified time limit.
The licenses in the default pool are used if they are available. When they are all in use, Analysts with access to the corralled licenses can still log in and will be assigned one of the corralled licenses. Corralled licenses do not restrict Analysts named in that corral when there are other licenses still available. They are only reserved when the remaining general licenses have been used.
Say, for example, you are running a service desk that must have at least five Analysts logged in at all times. To ensure that there are always five logins available, you could corral five licenses for the Service Desk. This would mean that if all of the default licenses are used, five Analysts in the Service Desk corral can still log in.
To leverage the advantages of both named and concurrent licenses, you can purchase a combination of both types of license. This may be particularly useful, for example, in organizations with a dedicated service desk as well as a pool of general Analysts.
A named license can be assigned to each service desk Analyst to ensure they have 24/7 access to the system, while a separate pool of concurrent licenses can be shared by other Analysts on a system.
