Business-ready architecture. Work with an open source leader.
Try Payara Enterprise
Luxury German Vehicle Manufacturer Migrates from GlassFish to Payara Server
Download BMW Case Study PDF
This page offers an overview of the features provided by Payara Platform products. The majority of our features are available in both Payara Server and Payara Micro software and in both the Community and Enterprise Editions, but if a specific feature is only available in one of our products, it is noted in the description.
Almost all features available in the Payara Platform Enterprise Edition may be manually added and built in Payara Platform Community Edition as it’s an open source project, but may or may not be supported in the next release.
A PDF version of this guide is also available below:
Features Catalog PDF
Domain Data Grid
Health Check Service
Want to see how Payara integrates with other tools or build on the Payara Platform and technologies with the products and tools you need for your enterprise environments? Browse our growing library of ecosystem integrations.
Payara DocumentationLearn More
A Payara instance created on a Docker node is a Docker Instance. When the container starts, the instance can join a Deployment Group. At registration time, the instance can use a specified configuration available on the Domain and when it joins a Deployment Group, all application assigned to that Deployment Group are also deployed on the Docker Instance.
The Docker Node feature in Payara Platform allows you to create additional nodes and Payara instances running within a Docker container. Both your instances and Docker container are under the control of the Domain Server and can be managed using either the Admin Console or the Asadmin CLI tool.
The Deployment Group is the clustering feature of Payara Server. It can be used as a target for deployments and other resources so that each are performed on the instances assigned to the Deployment Group. Payara Server’s Deployment Groups are an extremely flexible form of clustering as each instance can be part of one or more Deployment Groups. When a Deployment Group is restarted, a rolling restart of each instance is performed to ensure the information contained in the Domain Data Grid is kept.
The Domain Data Grid makes it easy to create a cluster of Payara instances running your application and works right out-of-the-box in variety of network topologies with little to no configuration needed for Amazon AWS, Google Cloud, Microsoft Azure, Kubernetes, and LAN environments. The Domain Data Grid can also share and store information for your application, so it is accessible by all instances.
The Data Grid Encryption offers end-to-end encryption to store and exchange sensitive information between instances securely. Information exchanged with Data Grid Encryption can only be read by the Payara instance.
High Availability for the Domain Data Grid ensures there is always a backup of application and system information, such as web session information, stored in the event an instance goes down. The data is redistributed when a new instance joins the Domain Data Grid.
With the JCache functionality you can define how data is stored in a Cache in a standard way. Since the JCache implementation in Payara Platform is provided by Hazelcast, which also is used in the Domain Data Grid functionality, you have a robust data grid acting as a caching tier.
Using MicroProfile Health Check with Payara Platform allows developers to create your own health checks for your applications and automate the verification of your system’s health status using your custom checks.
Notification Service works in the background to allow services such as JMX Monitoring, Payara Health Check, and Request Tracing to send messages to the notifiers.
Payara Platform Notifiers deliver monitoring and alert messages to external systems. Payara Enterprise has a list of notifiers bundled by default, but in Community they have to be installed manually.
The Notifier API allows third parties to create Payara Platform notifiers for their system and allows developers to customize notifiers for their needs.
JMX Monitoring in Payara Server allows you to gather information from MBeans and push it to external systems for processing and reporting without the need for external applications such as JConsole or VisualVM.
The Payara Platform Monitoring Service identifies possible issues for troubleshooting, checks performance against specified rules, and sends alerts of potential problem areas.
Payara InSight is the built-in monitoring console and provides a visual representation of all metrics collected by Payara Server, including MicroProfile Metrics defined via annotations, making it possible to track application-level performance and status.
REST Monitoring in Payara Server makes monitoring data accessible over a standard HTTP connection.
The Payara Platform Enterprise Edition includes several security features as part of the standard installation (you do not need to install them separately).
The Payara Platform supports OAuth2, which is similar to the SAML protocol but uses JSON instead of XML. OAuth 2.0 is an authorization framework that enables a third-party application to obtain limited access to an HTTP service.
Use the OpenIdConnect (OIDC) support within the Payara Platform products to achieve a Single Sign-on with the users credentials managed by a third-party. If a user has already been authenticated for one of your applications, he or she should not be asked for credentials when he accesses one of the other applications during the same browser session. This can be used when the applications are running on different servers or even on a mixture of Payara Server and Payara Micro.
The authentication and authorization information required for your application can be looked up in your LDAP server. This allows you to combine this information for many services within your application regardless of the technology with which they are written.
Payara Platform DocumentationEcosystem Catalog