A CPU license creates a pool of available connections, which allows for an unlimited
number of user to make connections.
This topic describes the CPU License option you have for purchasing licenses to ensure
that a sufficient pool of licenses is available for users connecting to a server to run your
applications.
A CPU license provides for an infinite pool of available connections. The CPU license is
so called because the number of physical or virtual CPUs (cores/threads) in the server where the
product is installed must match the number encrypted in the license when verified by the license
controller.
Degraded Mode
CPU licenses operate in degraded mode if the physical CPUs on the server do not match the CPUs
purchased on the license. The license controller will limit the size of the license pool to the
number of CPUs purchased multiplied by 25. So, for example, if a server has 32 CPUs and the license
is only for 16, then the available pool will be 400 connections. If you see the following message,
it means that your CPU license is operating in degraded mode. To resolve this, you will need to
contact your local Four Js sales
office.
-6180 CPU limit exceeded. The users control is reactivated.
Important: Before ordering CPU licenses, you need to run the license controller command, for
example, fglWrt -a cpu on the application server where the Genero runtime is
installed, to determine the exact number of CPUs (cores/threads) for licensing.
CPU licensing is recommended for the following:
- Large sites
- Large sites may potentially have many active users. CPU licenses are better suited than User
licenses because they provide for an infinite pool of connections.
- Genero Web Client (GWC) applications
- For GWC applications, detecting when the user has left the application or simply closed the
browser (as opposed to stopping the application by explicitly exiting it taking the appropriate
action) has implications for licensing. If the user closes the browser without exiting the
application, the DVM stays running and continues to consume a license. While the DVM will eventually
timeout, timeout configuration is not as critical to license management when CPU licenses are used.
- Web services applications
- A Web Service consumes a license in the same way that a user does, with one notable difference.
On reaching the available limit in the connections pool, Web services are queued rather than
blocked as with users. However, the greater the number of connections you can allocate for
the Web service pool, the greater the Web service throughput. This is why it is generally
recommended to opt for CPU licenses for Web services.
- Logical Partition (LPAR) and Virtualization
- Where Genero is installed on LPAR or Workload Partitions (WPARs) using virtualization
technology, such as that used on IBM® Advanced Interactive
eXecutive (AIX®) systems, CPU licenses are recommended. In this case, you will
need to provide the number of virtual CPUs allocated, not the number of physical CPUs in the server,
to determine the exact number of CPUs for licensing.