Technical Blog Post
Monitoring License Compliance
Maximo and other ISM applications can be licensed in different ways and measuring license compliance can get confusing. IBM does not 'lock out' users when licenses are exceeded but we do perform occasional audits. There are a few tools within the system that you can use to self-monitor your license compliance.
If you are licensed by registered users, User Types will be important. Out of the box we ship Type 1 through Type 10 as values in a standard domain. You can add more values and descriptions at they meet your business needs. For example, if you have TSRM and Maximo on your system you will have a mix of full users of each product and casual users of each product and maybe some users that use both. Set up a 'type' for each user community and associate the appropriate IDs with the appropriate types.
If you are licensed for concurrent users, User Sessions will be the metric you need to measure. There is an option within the User application 'Manage Sessions' that will let you view current sessions and also login history. In addition, there are two properties that can help you operate your system in compliance.
- mxe.enableConcurrentCheck - this will allow only one session on the server for each user id
- mxe.webclient.maxuisessions - this will allow you to set the maximum number of UI sessions allowed
If you have a 100 concurrent user license you can set the value of mxe.webclient.maxuisessions to 100 and mxe.enableConcurrentCheck to 1 and you will never have more than 100 concurrent sessions on the server. This can impact your users if theyare used to having multiple Maximo sessions open at once - to work on multiple work orders or purchasing documents at the same time, for example.
There are also standard KPIs for both user sessions and user types that can be added to an administrator's start center to keep up on compliance metrics.
If users have a limited license or only some users are licensed for particular applications (such as industry solutions), we suggest identifying those users as a specific type and then using security groups to associate the users in a particular type with the appropriate applications.
Auditing can also be enabled to prove compliance over time.
There is a tech note that provides more details. It references TSRM but applies to any TPAE based product.