Posts tagged Payara Server 5

How to Use Single Sign-on with Payara Server Realms

When a user needs to access multiple applications in your environment, you should not require authentication for each application. If the user has already been authenticated for one of the applications, he or she should  should not be asked for credentials when he accesses one of the other applications during the same browser session. This concept is called Single Sign-on where the authentication credentials are 'shared' in the environment and can be used by any application in that environment.

Deploying to Payara Deployment Group Using the Maven Cargo Plugin

Introduction

The Apache Maven Cargo Plugin allows you to deploy your application to a Payara Server, running locally or remotely. Using Maven as a build tool is an easy way to immediately deploy the application during the build to a test or production server.

We have created a custom version of the Cargo Plugin which also supports the Deployment Group feature of the Payara Server.

Payara InSight Improvements in Payara Server Enterprise 5.23

In Payara Server Enterprise 5.23 we continued improving our monitoring solution released in Payara Server Enterprise 5.22.0 (read about it here) called Payara InSight. The main focus of improvements for this release is the representation of alerts in the user interface. We also had a closer look at how widget content is arranged and coloured which also lead us to add further configuration options.

Payara Platform 5 Community Edition Supports HTTP/2 on All JDK Versions

Payara Platform 5 brought with it an implementation of Servlet 4.0, which itself contains support for the HTTP/2 standard. HTTP/2 support in Java has been fairly obscure for JDK 8 users, causing issues for many depending on their JDK minor version. This blog hopes to clarify the state of HTTP/2 in Payara Platform 5.

If you just want a quick answer to which Payara versions support HTTP/2 on which JDK version, jump ahead to Does Payara Server Support HTTP/2?

The Health Check Service In-Depth - Payara Server 5

This is an updated blog of the original which was published in May 2016

Payara Server provides the Health Check Service for automatic self-monitoring in order to detect future problems as soon as possible. When enabled, the Health Check Service periodically checks some low level metrics. Whenever it detects that a threshold is not met, it triggers alert notifications that allow to detect undesired behavior and predict possible failures. All of these automatic checks are very lightweight and run with a negligible impact on performance.

Fine Tuning Payara Server 5 in Production

One of the biggest challenges when developing applications for the web is to understand how they need to be fine-tuned when releasing them into a production environment. This is no exception for Java Enterprise applications deployed on a Payara Server installation. 

 

Running a Payara Server setup is simple: download the current distribution suited for your needs (full, web); head to the /bin folder and start the default domain (domain1)! However, keep in mind that this default domain is tailored for development purposes (a trait inherited from GlassFish Server Open Source). When developing a web application, it’s better to quickly code features, deploy them quickly, test it, un-deploy (or redeploy) it, and continue with the next set of features until a stable state is reached. 

(last updated 06/04/2021)