Appendix A: License Caching and Expiration

The TIBCO Enterprise Message Service™ server maintains a cache of the license. The EMS server uses the cache to verify entitlements. The cache helps ensure continuous access to TIBCO EMS as defined by your entitlement. It is located inside the configured store directory.

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

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

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

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

If the cache has not expired and the EMS 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 EMS server cannot contact the TIBCO Activation Service instance, the EMS 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 EMS server periodically reloads the license file to check for updates. The license cache can be updated with new entitlements without stopping the EMS server by simply updating the license file.

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