Appendix: License Caching and Expiration

The TIBCO Rendezvous daemon 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 TIBRV_LICENSE environment variable. The daemon uses the cache to verify entitlements. The cache helps ensure continuous access to TIBCO Rendezvous as defined by your entitlement.

The operating system determines the location of the license cache:

On Linux, the cached licenses are stored under /var/tmp/tibrv. If this directory does not exist, the daemon will create it. All Rendezvous daemons on the same host must have read and write access to this directory.
On Microsoft Windows, the cached licenses are stored in the directory designated for temporary files.

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 daemon regularly contacts the TIBCO Activation Service instance to refresh its cache and prevent service interruptions.

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

If the cache expires while disconnected from the TIBCO Activation Service instance, the Rendezvous daemon will exit immediately. Furthermore, the daemon will not start with an expired cache if it cannot contact the TIBCO Activation Service instance.

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

In-Product Activation

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

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

Did you find this helpful?

Yes No