Licensing
Your Adeptia license defines what the platform allows you to do and how much you can do, from the number of users you can create to the CPU resources your deployment may consume. The platform continuously monitors your usage against these entitlements and alerts you when limits are approached or exceeded.
What your license governs
Your license sets limits across several categories of platform usage. The specific limits that apply depend on your license edition.
| Category | What the license controls |
|---|---|
| Users | The number of developer, business, hub, and partner users you may have active |
| Partners | The number of trading partners and partner users per partner |
| Process flows | The number of activated process flows permitted |
| Activities | The number of activities permitted |
| Groups | The number of groups permitted |
| Data interfaces | The number of data interfaces permitted |
| EDI trading partners | The number of EDI trading partners permitted (when the EDI capability is included in your license) |
| B2B relationships | The number of EDI inbound, outbound, and routing relationships permitted |
| CPU cores | The total CPU cores that all running containers may consume across your deployment |
| Accelerator groups | Whether required accelerator content is deployed in the product |
Some limits are set to unlimited in certain license editions, in which case the platform does not enforce a cap for that category.
How the platform validates your license
Adeptia continuously checks your license in the background. These checks cover several areas:
- License validity: The platform verifies that your license has not expired and that the installation has not been tampered with. If the license is found to be invalid or expired, access to the platform is restricted.
- Usage limits: The platform periodically compares your current usage, such as the number of active users, process flows, groups, and data interfaces, against what your license permits.
- CPU core usage: The platform monitors the total CPU cores consumed across all running containers and compares that figure against the maximum your license allows.
- Accelerator content: The platform checks that required accelerator groups are deployed and available.
Soft violations and the grace period
Not every limit breach results in an immediate hard stop. When the platform detects that a usage limit has been exceeded, it may first enter a grace period, giving you time to bring usage back within the licensed limits before enforcement becomes strict.
During the grace period, you will receive warnings indicating which limit has been exceeded, how many days remain in the grace period, and what your current usage is relative to the licensed maximum. If the violation is not resolved before the grace period ends, the platform escalates to a hard violation, which can restrict access to the application.
Hard violations
A hard violation occurs when a license check fails in a way that cannot be deferred. Examples include an expired license, an invalid license, or a soft violation whose grace period has elapsed. When a hard violation is detected, the platform restricts access until the underlying issue is resolved.
Resolving a license violation
If you receive a license violation warning or are blocked from accessing the platform, the corrective action depends on the type of violation:
- Usage over limit: Reduce the number of active users, process flows, groups, data interfaces, partners, or other entities to bring your usage within the licensed limits.
- CPU core usage over limit: Reduce the CPU core allocation across your running containers.