+

Search Tips | Advanced Search

For up-to-date product documentation, see the IBM MobileFirst Foundation Developer Center.


Troubleshooting token licensing problems

Find information to help resolve issues that you might encounter with token licensing if you activated this feature when you installed MobileFirst Server.

When we start the MobileFirst Server administration service after you complete Install and configure for token licensing, some errors or exceptions can be emitted in the application server log or on MobileFirst Operations Console. These exceptions might be due to incorrect installation of the Rational Common Licensing library and configuration of the application server.

Important: If token licensing is installed on WebSphere Application Server Network Deployment or a cluster, we must check the log of each server.

Here is a list of exceptions that might occur after the installation and configuration for token licensing:


Rational Common Licensing native library is not found

FWLSE3125E: The Rational Common Licensing native library is not found. Make sure the JVM property (java.library.path) is defined with the right path and the native library can be executed. Restart IBM MobileFirst Platform Server after taking corrective action.


Rational Common Licensing shared library is not found

FWLSE3126E: The Rational Common Licensing shared library is not found. Make sure the shared library is configured. Restart IBM MobileFirst Platform Server after taking corrective action.

Possible causes to this error might be:


The Rational License Key Server connection is not configured

FWLSE3127E: The Rational License Key Server connection is not configured. Make sure the admin JNDI properties "mfp.admin.license.key.server.host" and "mfp.admin.license.key.server.port" are set. Restart IBM MobileFirst Platform Server after taking corrective action.

Possible causes to this error might be:


The Rational License Key Server is not accessible

FWLSE3128E: The Rational License Key Server "{port}@{IP address or hostname}" is not accessible. Make sure that license server is running and accessible to IBM MobileFirst Platform Server. If this error occurs at runtime startup, restart IBM MobileFirst Platform Server after taking corrective action.

Possible causes to this error might be:


Failed to initialize Rational Common Licensing API

Failed to initialize Rational Common Licensing (RCL) API because its native library could not be found or loaded com.ibm.rcl.ibmratl.LicenseConfigurationException: java.lang.UnsatisfiedLinkError: rcl_ibmratl (Not found in java.library.path)

Possible causes to this error might be:


Insufficient token licenses

FWLSE3129E: Insufficient token licenses for feature "{0}".

This error occurs when the remaining number of token licenses on the Rational License Key Server is not enough to deploy a new MobileFirst application.


Invalid rcl_ibmratl.jar file

UTLS0002E: The shared library RCL Shared Library contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at {0}/rcl_ibmratl.jar.

Note: For WebSphere Application Server and WebSphere Application Server Network Deployment only Possible causes to this error might be:

Parent topic: Install and configure for token licensing

Related links

Connecting MobileFirst Server installed on Apache Tomcat to the Rational License Key Server

Connecting MobileFirst Server installed on WebSphere Application Server Liberty profile to the Rational License Key Server

Connecting MobileFirst Server installed on WebSphere Application Server to the Rational License Key Server