Archive from June 2016
GlassFish has traditionally used Project Shoal to power its clusters. Since Shoal is no longer actively maintained, Payara Server intends to replace Shoal with Hazelcast, which has the added benefit of being JCache compliant.
Today at the DevNation conference in San Francisco, Payara’s Mike Croft appeared onstage during the Keynote, joined by Mark Little from Red Hat, Alasdair Nottingham from IBM, Theresa Nguyen from Tomitribe and Martijn Verburg from the London Java User Group to announce a new community collaboration called MicroProfile.
The goal of the MicroProfile initiative is to make it easier for developers to use familiar Java EE technologies and APIs for building microservice applications.
The HealthCheck Service provides automatic self-monitoring in order to detect future problems as soon as possible. The HealthCheck Service was introduced in Payara Server and Payara Micro version 161 and some new metrics have been added in version 162.
All the functionality of the HealthCheck Service that is available in Payara Server is also included in Payara Micro. However, as Payara Micro differs in some concepts from Payara Server, the usage and configuration of the HealthCheck Service is slightly different. In this post, we will focus on how to use it in Payara Micro.
Payara Micro 162 can now deploy your artifacts stored in Maven repositories simply by providing the GAV coordinates. This should provide another option for continuous delivery scripts!
Since Payara Server is on a regular and frequent release cycle, we get a lot of questions on how to upgrade to the latest version while maintaining existing domain configurations.
The answer to the question of “how do I upgrade?” is always “it depends”, because everyone’s situation is going to be slightly different. This blog will cover some of the most straightforward ways which should apply in the majority of cases.