Token licensing for Maximo Asset Management

Question & Answer

Question

How do I enable, configure, and use token licensing in Maximo® 7.6.1 and 7.6.1.1 systems?

Answer

This article is available as a PDF file.

For token licensing information for 7.6.1.2, see the Token licensing for Maximo 7.6.1.2 systems article (https://www.ibm.com/support/pages/node/6234000).

Overview

Token licensing is a fixed-term license control method. You can use token licenses, which are also known as tokens, to license IBM® Maximo® Asset Management, various Maximo industry solutions, and Maximo add-ons. The total number of tokens that you purchase is based on your predicted usage of the tokens. Tokens have a 1-1 relationship to license keys that you store and manage in IBM Rational® License Key Server. A request is sent from the Maximo server to Rational License Key Server whenever a token is consumed or released. The UserAnalyzer cron task in the Maximo system tracks and updates token usage data so that you can determine how tokens are being used.

Before you enable token licensing, consider the following information:

Perpetual or non-token licenses and tokens cannot be mixed on the same server.
The License Usage Monitor application does not report on token licenses and cannot be used with token licensing.

You enable token licensing after you set up your Maximo system. To enable token licensing, you complete the following steps:

Configure Rational License Key Server and IBM Rational License Key Administrator.
Configure the client file.
Configure the Token Licensing Setup application.
If you have 7.6.1, update the presentation.xml file.
If you have 7.6.1.1, activate the UserAnalyzer cron task.

Note: If you used token licensing for a Maximo 7.6.1 system and then you upgraded to a Maximo 7.6.1.1 system, contact your sales representative before you complete any token enablement or updates.

Token consumption

How many and when tokens are consumed and released varies according to the installed Maximo version and whether you have multiple Maximo environments or sessions. A request is sent from the Maximo server to Rational License Key Server whenever a token is consumed or released.
The UserAnalyzer cron task tracks and updates token usage data.

The tokens that are consumed at login are allocated by username and product combination. If a single username is logged in to several Maximo sessions simultaneously, and each session involves identical Maximo products, tokens are consumed for only one session. If the sessions do not involve identical Maximo products, tokens are consumed for each session.

Note: Closing the browser does not release the tokens. If a user does not release the tokens by exiting the application or logging out of the Maximo system before the browser or browser tab is closed, tokens are not released until the timeout value, which is specified in the web.xml file and is 30 minutes by default. If the timeout is longer than 30 minutes, the number of tokens that are in use might be higher than expected. The mxe.tokenlic.cleanupinterval property is used to locate sessions that are inactive after the timeout value. By default, every 5 minutes, the Maximo system is scanned for these sessions. If a session is located, it is automatically ended and the tokens are released. You can edit this frequency.

For more information about token consumption, review the section for your Maximo version.

Token consumption for 7.6.1.1

If you use token licensing with a Maximo 7.6.1.1 system, access types determine how many tokens a user consumes. Access types are automatically assigned according to a user's security profile. Configure your users' security profiles to ensure that each user is assigned the access type that you want the user to have. If a product is installed in your system but no user has access to that product, that product does not impact the number of tokens that are consumed for any user.

Access types are assigned to users when the UserAnalyzer cron task runs. By default, the UserAnalyzer cron task runs daily. In the Token Licensing Setup application, you can edit the schedule for the cron task by selecting More Actions > Data Collection Settings. For access types to be accurately assigned, all installed Maximo products must be specified in the Token Licensing Setup application. You complete this step when you enable token licensing.

Access types are associated with licenses, and each access type inherits the qualities of the lower access types. For example, for a user to be assigned a limited access type, the user must qualify for limited and express access types. All users qualify for the self-service access type. All users can access the Maximo self-service applications, such as the Self-Service Requestor and the Desktop Requisitions applications, and that access does not affect the assigned access type.

The following access types are available:

Self-service
This access type is assigned to users who can access only the self-service applications.
Express
This access type is assigned to users who have read-only access to one or more applications, can change the status of records, and can update work orders that are assigned to them. Users who are assigned the express access type consume fewer tokens than any other type of user except for users who are assigned the self-service access type.
Limited
This access type is assigned to users who can update data in three or fewer modules and have read-only access to one or more applications. For a user to be assigned a limited access type, they must not be able to the Administration module. Users can update work orders that are assigned to them, and the Work Orders module is not included in the three-module limit. Users who are assigned the limited access type consume more tokens than express users but fewer tokens than users who are assigned the full access type.
Full
This access type is assigned to users who have read-only and update access to four or more modules. Users who are assigned the full access type consume the most tokens.

The following table describes when tokens are consumed and released for a single user session in a single complete Maximo environment. The table does not describe the number of tokens consumed, which depends on the user’s access type. Note that if a user does not have an assigned access type or if the product is not specified in the Token Licensing Setup application, other rules are used to determine when tokens are consumed and released and how many tokens are used. A user might not have an assigned access type if the user is a new user and the cron task has not had the opportunity to run.

Token consumption for Maximo 7.6.1.1 products for a single user session
Scenario	Tokens consumed	Tokens released
User logs in to Maximo Asset Management.	The predefined number of tokens for the license that is associated with the user’s access type. If an access type is not assigned to the user or Maximo Asset Management is not specified as a product in the Token Licensing Setup application, only the predefined number of tokens for Maximo Asset Management are consumed.	When the user logs out of the Maximo system, the tokens are released.
User logs in to an instance of Maximo Asset Management that includes one or more industry solutions.	The predefined number of tokens for the license that is associated with the user’s access type. If a single industry solution is installed and if an access type is not assigned to the user or the industry solution is not specified in the Token Licensing Setup application, only the predefined number of tokens that are required for that industry solution are consumed. If multiple industry solutions are installed and an access type is not assigned to the user or the industry solutions are not specified in the Token Licensing Setup application, the highest predefined number of tokens for one of the industry solutions is consumed, and the predefined number of tokens for an add-on are also consumed for each of the other industry solutions. For example, IBM Maximo for Oil and Gas, which requires Y tokens, and IBM Maximo for Aviation, which requires Z tokens, are both installed on the same system, but Maximo for Aviation is not specified in the Token Licensing Setup application. Z is a higher number than Y. X is the predefined number of tokens for add-ons. When a user logs in, Z plus X tokens are consumed.	When the user logs out of the Maximo system, the tokens are released.
After a user logs in to Maximo Asset Management, the user accesses an application that is part of an add-on.	If an access type is assigned, no additional tokens are consumed. If an access type is not assigned to the user or the products are not specified in the Token Licensing Setup application, the predefined number of tokens for the add-on are consumed. For example, if Y is the predefined number of tokens for Maximo Asset Management, and X is the predefined number of tokens for the add-on, Y tokens are consumed when the user logs in to the Maximo system and X tokens are consumed when the user accesses an application that is part of an add-on. However, if the associated add-on is part of an industry solution, more tokens are not consumed for accessing that application. These rules do not apply to IBM Maximo Calibration or to IBM Maximo Linear Asset Manager.	When the user exits the application, X tokens are released.
After a user logs in to Maximo Asset Management, the user accesses an application that is part of IBM Maximo Calibration, IBM Maximo Linear Asset Manager, or both add-ons.	If an access type is assigned, no additional tokens are consumed. If an access type is not assigned to the user or the products are not specified in the Token Licensing Setup application, the predefined number of tokens for the add-on or, if an application is affected by both add-ons, the combined predefined number of tokens for both add-ons is consumed. For example, Maximo Calibration and Maximo Linear Asset Manager both affect the Work Order Tracking application. If both products are installed on the same system and if Maximo Calibration requires Y tokens and Maximo Linear Asset Manager requires Z tokens, Y plus Z tokens are consumed when the user accesses the Work Order Tracking application. Maximo Linear Asset Manager and Maximo Calibration both affect the following applications: The Work Order Tracking application The Assets application The Preventive Maintenance application	When the user exits the application, Y plus Z are released.
User accesses an IBM Maximo Anywhere application.	The predefined number of tokens for the license that is associated with the user’s access type. If an access type is not assigned to the user or Maximo Anywhere is not specified in the Token Licensing Setup application, the predefined number of tokens that are required for Maximo Anywhere are consumed.	When the user exits the application, the tokens are released.
User accesses IBM Maximo APM - Asset Health Insights On-Premises.	None. Tokens are consumed when the Maximo server is running. The number of tokens as determined by the resource value units (RVU).	When the Maximo server is no longer running, the tokens are released.
User accesses IBM Maximo Enterprise Adapter for Oracle Applications or IBM Maximo Enterprise Adapter for SAP Applications.	None. Tokens are consumed when the Maximo server is running.	When the Maximo server is no longer running, the tokens are released.
A Maximo integration framework user logs in to a Maximo system as part of an automated process.	No tokens are consumed.	Not applicable.

Token consumption for 7.6.1

If you use token licensing with a Maximo 7.6.1 system, the number of tokens that are used during a single user session in a single complete Maximo environment depends on which Maximo products are installed and which Maximo products are accessed during the session.

Note: If the March 2019 update is installed for 7.6.1 and you have only Maximo Asset Management or Maximo Asset Management and at least one industry solution installed, the number of tokens that are consumed for a single user session in a single Maximo environment depends on the assigned access type for the user. For more information about access types, see the Token consumption for 7.6.1.1 section of this article. In the March 2019 update, a user cannot be assigned a limited access type if the user can access the Administration, Integration, Security, or System Configuration module, and full access types are assigned to any user who does not qualify for any other access type.

The following table shows the token consumption for a single user session in a single complete Maximo environment, if the March 2019 update is not installed. If the March 2019 update is installed and the other conditions are met, the predefined number of tokens that are consumed when the user logs in is the number of tokens required for the user’s assigned access type. If a user is not assigned an access type, the rules described in the following table are used to determine token consumption.

Token consumption for Maximo 7.6.1 products for a single user session
Scenario	Tokens consumed	Tokens released
User logs in to Maximo Asset Management.	The predefined number of tokens for Maximo Asset Management.	When the user logs out of the Maximo system, the tokens are released.
User logs in to an instance of Maximo Asset Management that includes one or more industry solutions.	If a single industry solution is installed, only the predefined number of tokens that are required for that industry solution are consumed. If multiple industry solutions are installed, the highest predefined number of tokens for one of the industry solutions is consumed. For example, IBM Maximo for Oil and Gas, which requires Y tokens, and IBM Maximo for Aviation, which requires Z tokens, are both installed on the same system. Y is a higher number than Z. When a user logs in, Y tokens are consumed.	When the user logs out of the Maximo system, the tokens are released.
After a user logs in to Maximo Asset Management, the user accesses an application that is part of an add-on.	The predefined number of tokens for the add-on. For example, if Y is the predefined number of tokens for Maximo Asset Management, and X is the predefined number of tokens for the add-on, Y tokens are consumed when the user logs in to the Maximo system and X tokens are consumed when the user accesses an application that is part of an add-on. However, if the associated add-on is part of an industry solution, more tokens are not consumed for accessing that application. These rules do not apply to IBM Maximo Calibration or to IBM Maximo Linear Asset Manager.	When the user exits the application, X tokens are released.
After a user logs in to Maximo Asset Management, the user accesses an application that is part of IBM Maximo Calibration, IBM Maximo Linear Asset Manager, or both add-ons.	The predefined number of tokens for the add-on or, if an application is affected by both add-ons, the combined predefined number of tokens for both add-ons. For example, Maximo Calibration and Maximo Linear Asset Manager both affect the Work Order Tracking application. If both products are installed on the same system and if Maximo Calibration requires Y tokens and Maximo Linear Asset Manager requires Z tokens, Y plus Z tokens are consumed when the user accesses the Work Order Tracking application. Maximo Linear Asset Manager and Maximo Calibration both affect the following applications: The Work Order Tracking application The Assets application The Preventive Maintenance application	When the user exits the application, Y plus Z are released.
User accesses an IBM Maximo Anywhere application.	The predefined number of tokens that are required for Maximo Anywhere.	When the user exits the application, the tokens are released.
User accesses IBM Maximo APM - Asset Health Insights On-Premises.	None. Tokens are consumed when the Maximo server is running. The number of tokens as determined by the resource value units (RVU).	When the Maximo server is no longer running, the tokens are released.
User accesses IBM Maximo Enterprise Adapter for Oracle Applications or IBM Maximo Enterprise Adapter for SAP Applications.	None. Tokens are consumed when the Maximo server is running.	When the Maximo server is no longer running, the tokens are released.
A Maximo integration framework user logs in to a Maximo system as part of an automated process.	No tokens are consumed.	Not applicable.

Token consumption for multiple environments

For both 7.6.1 and 7.6.1.1, the existence of multiple Maximo environments, such as a development environment, a test environment, and a production environment, impacts your license usage. Usage of non-production environments is tracked by the same token consumption standards for your production environment for your version of your Maximo system. Each environment should be a complete Maximo instance on its own database.

The following examples reflect the behavior that you can expect when you use multiple Maximo environments:

Example 1: A system administrator logs in to Maximo Asset Management in the development environment. After the system administrator logs in, the system administrator opens another browser and logs in to Maximo Asset Management in the production environment. Because the user ID and product combination is the same and the system administrator logged in to the development environment first, tokens were consumed only when the system administrator logged in to the development environment. Tokens were not consumed when the system administrator logged in to the production environment.

Example 2: A system administrator logs in to Maximo Asset Management in the development environment. After the system administrator logs in, the system administrator opens another browser and logs in to Maximo for Oil and Gas in the production environment. The user ID is the same for each environment, but the product is different. Because the product is different, tokens were consumed when the system administrator logged in to the development environment and more tokens were consumed when the system administrator logged in to Maximo for Oil and Gas.

If you have Maximo Enterprise Adapter installed on your system and you have multiple environments, all environments consume individual sets of tokens and retain those tokens from the time that the Maximo server starts running until the Maximo server stops running.

For example, if you have a development environment, a test environment, and a production environment, when the Maximo starts running, each of those environments consumes Y tokens and retain those tokens until the Maximo server stops running.

Token usage data

After the UserAnalyzer cron task runs, you can review updated token usage data for your users. If you have 7.6.1, you can review token usage data in the tokenlicusers database table. If you have 7.6.1.1, you can review token usage data in the tokenlicusers database table, or you can enable a Token Profile tab that contains token usage data for the Users application.

To enable the tab, complete the following steps:

In the Security Groups application, select a security group.
On the Applications tab, in the Applications table, select the Users application.
In the signature option rows, open the row for the User Token Profile signature option.
Select the Grant Access check box, and then save the security group.

Triads

A triad, which is also known as a system of redundant servers, is an instance of three, connected license servers. By setting up a triad, you can increase the reliability of your licensing system.

For token licensing, one license server in the triad serves the tokens on behalf of the other license servers in the triad. If one of the license servers is down, your users are not affected because the other two license servers can still run. If two license servers are down, the remaining license server does not run.

You do not need a special port or URL to set up a triad. However, all license servers that are a part of a triad must be geographically aligned with the associated Maximo server. Significant time-zone differences between a triad and the Maximo server can result in increased latency or failure of a request.

For more information about triads, review Configuring a license server on Microsoft™ Windows™ (https://www.ibm.com/support/knowledgecenter/SSSTWP_8.1.4/com.ibm.rational.license.doc/topics/r_redundant_servers_win.html) or UNIX ™ (www.ibm.com/support/knowledgecenter/SSSTWP_8.1.4/com.ibm.rational.license.doc/topics/r_lic_server_unix.html).

Stand-alone servers

If you set up stand-alone license servers, each license server requires its own license file, and you must divide the token pool among the license servers. You cannot set up both triads and stand-alone servers.

If you have multiple stand-alone license servers and one of the license servers cannot complete a token request, another license server is used to complete the request. The order in which license servers are used is determined by the order of the addresses in the Server Address field of the Token Licensing Setup application, which you configure when you enable token licensing.

Performance

The performance of your license servers is affected by the network that is used, the number of users who are requesting tokens from the license server, and the availability of tokens on the license server. Performance is measurable in ping time.

Ping time is the time that is required for a request to be sent plus the time that is required for that request to be acknowledged; it is the round-trip time for requests that are sent from the originating host to a destination computer. Any value that is less than the request timeout for the associated product is an acceptable ping time for the license server. The request timeout varies according to the associated product.

To help to ensure connectivity and improve performance, complete the following tasks when you set up your license servers:

Connect your license server to a network that is at least 100 ms. The performance of a license server is directly proportional to the bandwidth and latency of the network that the license server is connected to. The consumption of network bandwidth is directly proportional to the number of users who are requesting tokens from the license server.
Add a license server to the same geographical region as the users of that server. Time-zone differences can cause tokens to not be served to users.
Use Linux™ or UNIX™ for the license server. By using Linux or UNIX, you can have more control over the file descriptor size, which you can use to control performance. If the license server is running on Windows™ and more than 3000 users are requesting tokens, distribute the token pool across multiple license servers, with each license server handing requests for no more than 3000 users.

Enabling token licensing

To enable token licensing, you must install and configure Rational License Key Server and Rational License Key Administrator, configure the client file, and then configure the Token Licensing Setup application. If you are using a Maximo 7.6.1 system, you also must update the presentation.xml file for the Token Licensing Setup application. If you are using a Maximo 7.6.1.1 system, you also must activate the UserAnalyzer cron task.

Checklist

You can use the following checklist to ensure that all of the following steps are completed successfully.

Checklist for enabling token licensing
Done	Task
	Complete the prerequisites.
	Install and configure Rational License Key Server and Rational License Key Administrator.
	Configure the client file.
	Configure the Token Licensing Setup application.
	If you are using a Maximo 7.6.1.1 system, activate the UserAnalyzer cron task.
	If you are using a Maximo 7.6.1 system, update the presentation.xml file for the Token Licensing Setup application.

Prerequisites

Ensure that you have the following products, permissions, and resources before you enable token licensing:

A Maximo 7.6.1 IFIX007 or later system.
An IBMid.
A Rational License Key Center (licensing.subscribenet.com/control/ibmr/login) account. You use this account to manage the license keys that are in Rational License Key Server. If you are the primary site contact or site technical contact for your Passport Advantage account, you are automatically a member of the Rational License Key Center account and receive a welcome email. Use the instructions in the email to access the account. As part of the account setup, you must create a password. You must create this password within 72 hours of receiving the welcome email.

If you cannot locate your welcome email and you are unable to access your account, in Rational License Key Center, select Forgot your password. Instructions for resetting your password are sent to your email.

If you are not the primary site or site technical contact, complete one of the following tasks to receive access to the Rational License Key Center account:
Request access from your primary site contact.
If you have the site number for the license purchase, on the Rational License Key Center (licensing.subscribenet.com/control/ibmr/login) login page, select Don’t have a password and complete the Join Account form. If you have the sales order number, specify it. An email is sent to the administrator of the Rational License Key Center account to request approval for your membership.

For more information about setting up a Rational License Key Center account, see How to access Rational License Key Center (https://www.youtube.com/watch?v=aLte61Ll4yc&feature=youtu.be).

Installing and configuring Rational License Key Server and Rational License Key Administrator

To set up Rational License Key Server and Rational License Key Administrator, you must install the product and then retrieve and import the license keys for each license server.

Install Rational License Key Server and IBM Rational License Key Administrator.
1. Download the files from Fix Central. For instructions, review the product documentation in IBM Knowledge Center (www.ibm.com/support/knowledgecenter/en/SSSTWP_8.1.6/com.ibm.rational.license.doc/topics/t_download_files_support.html).
2. Complete the installation. For installation instructions, review the installation product documentation in IBM Knowledge Center (https://www.ibm.com/support/knowledgecenter/en/SSSTWP_8.1.6/com.ibm.rational.license.doc/topics/c_node_installing.html).
For each of your license servers, generate your license key in Rational License Key Center.
1. Log in to Rational License Key Center (licensing.subscribenet.com/control/ibmr/login) by using your account user name and password.
2. On the Get keys screen, click IBM Tokens.
3. In the box for your product or unique sales order, in the LICENSE KEYS FOR THIS ORDER section, click the check box.
4. Click Next.
5. In the Number of keys to generate field, specify the number of tokens that you want assigned to the license server.
6. In the Existing hosts and Server Configuration fields, select the options for your license server.
7. In the Host ID Type field, select an option that is associated with the hardware to which you are registering your key.
8. In the Host ID and Hostname fields, specify the values that are included in Rational License Key Administrator. To view this information, in Rational License Key Administrator, select License Keys > Host Data.
9. Click Generate.
For each of your license servers, import the license key.
1. On the View Licenses By Host screen, click Download License Keys. Follow the steps that are provided in the License Key Installation Instructions section to download and import the license key.
2. After the steps are completed, in Rational License Key Administrator, review the license key information and ensure that accurate Maximo products, license types, and license quantities are displayed.

Review the Rational License Key Server product documentation (https://www.ibm.com/support/knowledgecenter/en/SSSTWP_8.1.6/com.ibm.rational.license.doc/helpindex_RCL.html) to learn how to configure, administer, and use license servers.

Configuring the client file

The client file enables your Maximo server to communicate with the license server.

Download the client files.zip file, which is attached to this article.
client files.zip
Extract the files from the client files.zip file. The client files.zip file contains two files.
Relocate your client file to any directory that your Maximo server can access. If you are using Windows, your client file is the rcl_ibmratl.dll file. If you are using Linux or UNIX, your client file is the librcl_ibmratl.so file.
Add the following text to the jvm parameter of all of the Maximo servers. Replace the client file directory variable with the client file directory.
-Djava.library.path=client file directory
Repeat these steps for all Maximo servers.
Restart the application servers.

Configuring the Token Licensing Setup application

After you configure the client file, you must configure the Token Licensing Setup application. You use the Token Licensing Setup application to connect your Maximo system to Rational License Key Server.

Procedure

Enable the Token Licensing Setup application.
1. Log in to your Maximo system as the system administrator.
2. In the Security Groups application, select the MAXADMIN security group.
3. On the Applications tab, filter for token licensing setup and then select the Grant Access check box for the application.
4. Save the security group.
5. Log out and log back in to the Maximo system.
In the Token Licensing Setup application, in the Server Address field, specify the address for your instance of Rational License Key Server. Your instance of Rational License Key Server is your license server.
- The format for a single address is port@hostname.
- The order in which license servers are used is determined by the order of the addresses in the field.
- If you are using a Linux™ or UNIX™ system, separate multiple addresses by using colons (:).
- If you are using a Windows™ system, separate multiple addresses by using semicolons (;).
- Separate multiple addresses for redundant license servers or a triad by using a comma (,).
- If you specify a hostname that is not fully qualified, the connection to the server might not be established. If the connection cannot be established, specify a fully qualified hostname.
Click Test. If the connection is successful, a confirmation message is displayed.
If the connection is successful, click Save. The server addresses are added to the mxe.token.licensepath system property. Do not click Save unless the connection is successful.
Complete the following steps according to your installed Maximo version.
- If you have 7.6.1, select OK and save the record.
- If you have 7.6.1.1, complete the following steps:
  1. Select Manage Products.
  2. In the Manage Products dialog box, select New Row.
  3. In the Product Name field, select a product that is installed in the current environment.
  4. In the License Type field, select the license type.
  5. Select OK and save the record.
  6. Change the status of the row to active.
  7. Repeat these steps for all other products that are installed in the current environment.

Activating the UserAnalyzer cron task

If you have 7.6.1.1, you must activate the UserAnalyzer cron task. The UserAnalyzer cron task gathers and updates token usage data. To learn more about token usage data, review Token consumption.

Procedure

In the Token Licensing Setup application, in the More Actions menu, select the Data Collection Settings action.
Select the Activate check box and then save and close the dialog box.
Rebuild and redeploy the EAR file.

When the cron task is activated, the cron task might not run immediately. By default, the cron task runs once in a 24-hour period.

Updating the presentation file

If you are using 7.6.1, you also must update the presentation.xml file for the Token Licensing Setup application. By updating the presentation file, you can ensure that you have the latest version of the Token Licensing Setup application in your system.

Create a tokenlic.xml text file.
Paste the following text into the tokenlic.xml file and then, in the Application Designer application, for the Token Licensing Setup application, import the tokenlic.xml file to replace the existing presentation.xml file.

<?xml version="1.0" encoding="UTF-8"?>

Verifying your token enablement

To verify your token enablement, for each of your license servers, you can generate a list of the tokens that are consumed.

Before you verify your enablement, ensure that tokens have had the opportunity to be consumed. For example, ensure that the Maximo server is running or have users of varying security permissions log in to the system. Review the token consumption sections of this document for more information about when tokens are consumed.

You also must ensure that the UserAnalyzer cron task has run. By default, the cron task runs once in a 24-hour period.

In a command line, open the Rational License Key Server directory.
Run the following command. Ensure that you replace the port and hostname variables with the port and hostname of your license server.
lmutil lmstat -a -c port@hostname

If token licensing is enabled, the output contains server details, feature names, the times that tokens were consumed, and the number of tokens consumed.

Troubleshooting token licensing

If you need to troubleshoot your token licensing configuration, set the tokenlic logger to DEBUG and set the UserAnalyzer cron task to a shorter frequency. To set the cron task to a shorter frequency, in the Token Licensing Setup application, in Data Collection Settings dialog box, update the Schedule field. By setting a shorter frequency, you can more quickly determine whether your configuration is working as expected.

Connecting to the license server

In the Token Licensing Setup application, when you test the connection to the server, if the connection is not successful, ensure that the license server is running. Then, from the Maximo application server host machine, telnet to connect to the lmgrd port of the license server.

Do not click Save unless the connection is successful. If the connection is not successful and the configuration is saved, you must undo the configuration by running the following database queries:

select * from propvalue where propname='mxe.tokenlic.licensepath';

update maxpropvalue set propvalue=null where propname='mxe.tokenlic.licensepath';

License server behavior

A license server can be unable to complete a request for the following reasons:

The license server is unavailable.
The network or firewall that is used for the license server is unavailable or the quality of the network is poor. If a poor network is used and if the Maximo server is unable to queue up simultaneous requests to load or adjust and adapt to the delay that is caused by the network, the requests can time out before the requests reach the license server.
The user who requests the tokens is blocked from the license server. You can block users from a license server by using the license option file.
The license server has no available tokens.
Too many users are requesting tokens from a license server simultaneously. If many users are requesting tokens, users can experience an unresponsive Maximo system and long delays between the time that the token is requested and when the token is consumed.

If a significant difference exists between the time zone of the license server and the time zone of the Maximo server, tokens are not served to users. In this case, the following error occurs in the license server log file after a license request is sent:

"Licensing Error: Clock Difference too large between client and server."

Token profile issues

If you have 7.6.1.1, you can enable a tab that contains token usage data for the Users application. After you enable the tab, an erroneously high number of token licenses might be tracked on the tab. To resolve this issue, complete the following steps:

In the Application Designer application, open the Users application.
Click the Token Profile tab and then right-click the Token Licenses table.
In the Table Properties dialog box, clear the Business Object field.
Save your changes.

UserAnalyzer cron task error

If the BMXAA4214E error occurs when you activate the UserAnalyzer cron task, ensure that you installed the latest interim fix for your Maximo system and then complete the following steps:

In the maximo_root/deployment directory, open the buildmaximoear.xml file.
Append the following text to the end of the maximo.businessobjectsclasspath property: lib/license_metric_logger_2.1.1.201507131115.jar

The following text is an example of this change:
<property name="maximo.businessobjectsclasspath"> lib/license_metric_logger_2.1.1.201507131115.jar

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"ARM Category":[{"code":"a8m0z0000001hDuAAI","label":"System->Token Licensing"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6.1","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Tips