Posts tagged DevOps (2)
Payara Micro allows you to run web applications in a self-contained and easy way. Since the release of the Payara Server in May 2016, there is a simple way to generate an "Uber" JAR that bundles the contents of a WAR file and the classes and resources that compose Payara Micro!
Note that this "Uber" Jar is not the best way to run your application in a Docker container as it requires an update of the entire binary for each small code change you make in the application. A better solution is just to start a Payara Micro Instance and point to the application that needs to be installed. More information can be found on our Payara Micro Docker Image documentation.
(last updated 06/04/2021)
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.
One of the most exciting new features in the Payara Server 162 release is the Asadmin Recorder - a tool especially useful for the Operations Teams!
Asadmin Recorder allows you to create runnable scripts of asadmin commands that mirror configuration done in the administration console. Have a look at our video walkthrough below for a quick overview of this new Payara Server feature.
Once you have developed applications on Payara Server and moved these applications into a production environment, control will pass over to your Operations Teams. This guide will introduce some features of Payara Server that you may not know about, which are especially useful for the operations teams.
Taking an environment from development through to production is often an afterthought and can all too often be too far down the list of priorities. Initially, there may not be any obvious problems or issues with manually configuring a new production environment to match an existing one in development or test. As some customers I have visited have found, however, this will only lead to bigger and bigger inconsistency between platforms with ad-hoc changes causing different environments to diverge.