Payara Platform Enterprise users will be pleased to hear that we released a refactor of the MicroProfile OpenAPI implementation we provide in Payara Platform Community 5.2020.3 with the aim of addressing a number of issues and requests that had been raised over time. The original blog, detailing some of these features, can be found here.
OpenAPI Refactor has now been included in the Payara Platform Enterprise 5.23.0 release.
New in the Payara Server 5.2020.4 release (August 2020), RMI calls to an EJB hosted on Payara Server from a Java SE client will now have the active Span Context automatically propagated to the server, with a counterpart server-side span being created as a child of this client call. This fills in a gap in our existing Request Tracing service, and comes with the added benefit of allowing a user to propagate key:value pairs from a Java SE client to Payara Server (or simply from server to server) in a request as OpenTracing baggage items - of particular interest to those who utilise Context Propagation or similar features in other application servers.
MicroProfile Health is an API designed specifically for use in cloud and containerized environments, where you want to quickly determine if an instance of an application is unhealthy and restart it. How exactly do you use it though? In this session, I’ll run through how to add some health checks to your application, and how to configure a number of cloud providers and containers to effectively use them to restart your application instances.
The first release of the Payara Platform in 2020 syncs the Stability and Community streams. For those not in the know, the Community stream is what we call our quarterly public releases, and the Stability stream is what we call our monthly bug fix-only releases for those with the supported version of Payara Platform Enterprise, (see here for more info on the release streams).
Encryption of the data stored within the data grid of Hazelcast (the technology underpinning our deployment groups and clustering in Payara Platform 5) has until now required a Hazelcast Enterprise subscription (see Payara Scales). While this remains an option for those who would like the additional features it provides (such as WAN replication), we’ve begun introducing this particular feature into Payara Server itself to provide it to you without needing an additional subscription.
When creating instances, it can sometimes be a chore remembering what names are already in use or even coming up with a name to use in the first place! The Dynamic Instance Naming feature, sometimes called auto-naming, introduces a new option to the create-instance & create-local-instance commands that, when enabled, will resolve any name conflicts or generate a name for you.
Request tracing has been a feature in Payara Platform for a number of years now, and over time it has evolved and changed in a number of ways. The crux of what the feature is remains the same, however: tracing requests through various parts of your applications and the Payara Platform to provide details about their travels.