Glossary

A user who has successfully activated their access to a Payara Qube installation.

A user with comprehensive administrative privileges, including the ability to deploy, configure, and manage applications, as well as control user access and roles within the Payara Qube installation. The administrator also has the unique ability to manage namespace-specific roles and perform important namespace-level operations, such as creating new namespaces, setting up custom domains, and deleting namespaces.

A user responsible for managing the administrative aspects of an installation, such as overseeing user management and system configuration tasks. The Billing Manager can also invite new users to the installation and modify their roles, except for granting or revoking Billing Manager roles.

A special role that combines the permissions of both the Billing Manager and Administrator, granting full access to both the administrative and technical aspects of a Payara Qube installation.

A unique token used to authenticate and authorize access to the Payara Qube Command Line Interface (CLI) for managing namespaces and applications from a terminal or command prompt.

The process of launching an uploaded and configured application, making it accessible and operational within the Payara Qube environment on your infrastructure.

A hierarchical and decentralized naming system that translates human-readable domain names (e.g., https://www.example.com) into machine-readable IP addresses, enabling users to access websites and services over the internet.

A snapshot of the Java Virtual Machine’s (JVM) memory at a specific point in time, capturing information about objects, their sizes, and references.

A user whose access to a Payara Qube installation has been temporarily deactivated or suspended.

An email sent to a user, granting them access to an existing Payara Qube installation. The invitation contains a unique link that the recipient can follow to activate their access and join the installation.

A user role with full access to existing Payara Qube namespaces. Managers can upload new applications, delete existing ones, and perform various application management tasks, but they cannot access administrative data or perform namespace-level operations.

A user with limited access to a Payara Qube installation, typically restricted from performing certain administrative tasks.

A logical grouping or container within a Payara Qube installation that isolates and organizes related applications, providing a distinct environment for application deployment and management. Each namespace has its own unique domain and allows applications to be deployed at specific sub-paths within that domain.

A user role focused on application reconfiguration and diagnostics. Operators can analyze and adjust application settings but cannot delete applications or access sensitive configuration properties.

A user who has received an invitation to a Payara Qube installation but has not yet accepted or activated their access.

The allocation of resources, primarily CPU and memory, assigned to an application instance in Payara Qube. The available runtime sizes depend on your infrastructure capacity and impact the application’s performance and resource usage.

The combination of Java and Jakarta EE versions that an application is developed against and requires for execution in Payara Qube. For Spring Boot applications, this refers to the Java version and Spring Boot framework version. Selecting the correct runtime type ensures compatibility and optimal performance.

The specific phase or environment in which an application is deployed, such as development, testing, pre-production, or production. Stages help organize and manage applications based on their development lifecycle.

The fundamental licensing unit in Payara Qube, representing a defined set of resources and access levels granted to users within the platform installation. Each installation operates under its subscription terms and provides access to the platform’s features and capabilities.

A snapshot of all the threads running within the JVM at a specific moment, capturing their states, stack traces, and other relevant information.

A user role with read-only access to deployed applications. Viewers can monitor application metrics, view logs, and access configuration details (excluding sensitive properties) but cannot make any modifications.