Appendix: License Caching and Expiration

The TIBCO FTL server maintains a cache of the license. The source of the cache is a license file or the TIBCO Activation Service instance loaded using the -license command-line parameter or by setting the TIBFTL_LICENSE environment variable. The FTL server uses the cache to verify entitlements. The cache helps ensure continuous access to TIBCO FTL as defined by your entitlement.

The operating system determines the location of the license cache. On Linux and Microsoft Windows, the cached licenses are stored in the data directory inside the tib-lm folder. If this directory does not exist, the FTL server will create it. The FTL server must have read and write access to this directory.

There are some differences in behavior depending on the source of the license.

TIBCO Activation Service

When the source of the license is a TIBCO Activation Service instance the cache may have an expiration date that is earlier than the license itself. The FTL server regularly contacts the TIBCO Activation Service to refresh its cache and prevent service interruptions.

An alert is logged if the FTL server fails to reach the TIBCO Activation Service instance during a cache refresh, indicating potential service disruption.

If the cache expires when disconnected from the TIBCO Activation Service instance, the FTL server exits immediately. Furthermore, the FTL server does not start with an expired cache if it cannot contact the TIBCO Activation Service instance.

If the cache has not expired and the FTL server is restarted with the same configuration while the TIBCO Activation Service instance is unreachable, an alert is logged indicating the potential for service disruption. If the FTL server cannot contact the TIBCO Activation Service instance, the FTL server will exit when the cache expires.

In-Product Activation

When the source of the license is a license file for In-Product Activation, the cache expiration and the license expiration are identical. The FTL server periodically reloads the license file to check for updates. The license cache can be updated with new entitlements without stopping the FTL server by simply updating the license file.

If the license file is moved, deleted or otherwise invalidated, the FTL server logs an alert indicating the potential for service disruption.