Posts tagged DevOps
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.
Since Java EE 6 it's possible to define data sources in a portable way.
This does mean though that the data source is embedded in the application archive. For some use cases, this is exactly what's needed, but for others it may not be ideal.
Now that the ForgeRock tools have been installed, we will configure them with some basic access configuration. First, proceed to login to the OpenAM application (context /openam) with the amadmin user, and the application will show you the current realm configuration for your domain:
Today, one of the most important concerns for enterprise applications is to implement robust security mechanisms that allow developers and operation staff to easily integrate applications in a stable infrastructure and allow their users to interact with them in a seamless way. While many developers prefer to implement their own security mechanisms or use third-party libraries, a good alternative is to use already established products that handle authentication, authorization, confidentiality, identity, and entitlement on behalf of already developed 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.
Recent versions of Payara Server provide the HealthCheck Service for automatic self-monitoring, in order to detect future problems as soon as possible. When enabled, the HealthCheck Service periodically checks some low level metrics and logs warnings whenever it detects that a threshold is not met. All of these automatic checks are very lightweight and run with a negligible impact on performance.
The HealthCheck Service was introduced in Payara Server 161 and some new metrics have been added in Payara Server 162. It is also available in Payara Micro edition, and we will cover the details on how to make use of it in another post soon.
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.