AppPoints

AppPoints are credits or units of value by which IBM® TRIRIGA® Application Suite can be licensed. Application usage, runtime, and user access for TRIRIGA Application Suite are managed by using AppPoints. Administrative users use the License Manager to assign AppPoints to users. From a user perspective, AppPoints usage is not visible. A user logs in and works without having to know anything about AppPoints.

Each TRIRIGA Application Suite instance has a number of allocated AppPoints, which is set by the license. These AppPoints are used as users are assigned to a license tier. You can configure your environment to enforce the AppPoints entitlement and block users from being assigned to an AppPoints consumption tier. If compliance is not enforced, users are able to log in, but you might be charged for the overage.

License Key Center (LKC) License File

The TRIRIGA Application Suite license that gets generated is specific to the SLS installation instance that the license gets loaded into by TRIRIGA. The license is generated in LKC by using the HostID of the SLS instance.

TRIRIGA Application Suite SLS

Multiple instances of TRIRIGA Application Suite (Production, Development, Test, and so on), and all the pods that are running the TRIRIGA Application Platform container in an instance, must be configured to point to a single SLS instance, even when those instances are running in different Red Hat® OpenShift® environments. That SLS instance can run in the Red Hat OpenShift environment of any of those instances. One license file is used across all of the instances. SLS handles users with the same username as a single user across different instances of TRIRIGA Application Suite and deducts AppPoints once per user.

If different SLS instances are used for different TRIRIGA Application Suite instances, then separate LKC licenses are needed, each containing their own AppPoint allocation. AppPoint usage is duplicated for the same user. When users are released across all instances, those AppPoints are released for the user in SLS.
  • Server = Red Hat OpenShift Pod
  • Instance = Red Hat OpenShift Installation (which can contain multiple Pods). For example, Production Instance and Development Instance. Each of them can have different configurations of numbers of Pods.

User AppPoints allocation

The following table provides an overview of the AppPoints allocation for user and room entitlements:
License Description License ID AppPoint Consumption Metric AppPoints
IBM TRIRIGA Application Suite - Self-Service No-Charge User TAS-SS-No-Charge Per Application Instance 0
IBM TRIRIGA Application Suite- Self-Service Limited User TAS-SS-Limited Per 500 Authorized Users 2
IBM TRIRIGA Application Suite - Self-Service Base User TAS-SS-Base Per 500 Authorized Users 10
IBM TRIRIGA Application Suite - Limited User TAS-Limited Per Authorized User 2
IBM TRIRIGA Application Suite - Limited Occasional User TAS-Limited-Occasional Per 3 Authorized Users 2
IBM TRIRIGA Application Suite - Base User TAS-Base Per Authorized User 5
IBM TRIRIGA Application Suite - Base Occasional User TAS-Base-Occasional Per 3 Authorized Users 5
IBM TRIRIGA Application Suite - Configure User TAS-Configure Per Authorized User 10
IBM TRIRIGA Application Suite - Room Panel TAS-Room-Panel Per 100 Rooms 2