The Domain Data Grid feature of the Payara products is powered by the Hazelcast library. It provides the necessary functionality for the Deployment Group (clustering functionality), Cache functionality, CDI cluster singleton, and monitoring data storage within Payara to name just a few features.

Since Hazelcast can cluster multiple instances into a data grid, it is possible to create a Hazelcast grid that comprises the Payara instances and some other instances included in other applications running outside of Payara.

The JBatch Jakarta EE specification describes the process of how background jobs can be executed on a Jakarta EE compatible runtime. Using the Batch Specification, the runtime can execute some jobs that don't require any user input. Most of the time they are scheduled to execute at a certain moment of the day, but they can be triggered on-demand.

Introduction

The Payara Enterprise Release 5.22.0 is the first Payara Enterprise release to include our fully integrated and greatly improved real-time monitoring and alerting solution called Payara InSight (formerly known as Payara Monitoring Console in Payara Community).

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 them, un-deploy (or redeploy) them, and continue with the next set of features until a stable state is reached. 

(last updated 06/04/2021)

In the previous blog of this series, we learned about 5 production features of the Payara Server 5. This blog will continue to introduce 5 more production features of Payara Server 5 that you might not know about - but should.

Webアプリケーションを開発する際における最大の挑戦の一つは、商用環境へのリリース時にアプリケーションをどのように調整すべきかを理解することです。これはJavaのエンタープライズ・アプリケーションをPayara Serverへデプロイする場合でも例外ではありません。

Back in 2016, we wrote about the importance of automation in taking applications from development to production with Payara Server. Since then, there have been a lot of changes both in Payara Server and Payara Micro and the wider tech landscape.

In the last few weeks, we have released two builds of Payara Server; our new major version 172 and third patch build of version 171 - 171.3. This is the first time we've ever released two distinct builds in the same month, so why are we doing it?

Kick-starting yet another year, we are pleased to announce our largest release yet - Payara Server 4.1.1.171. Building on a year's worth of updates and improvements, in this release, you can find 18 brand new features and over 60 new fixes and enhancements for Payara Server & Payara Micro! Given the size of the additions, look out for detailed blogs in the near future. For now, check out below for a summary of the changes in 171 release, and have a look at the full release notes.