Posts tagged How-to
One major issue when developing modern enterprise applications is the "works on my machine" problem: when an application works well on your machine but is not functional in production or even on a colleague's machine. An even more prevalent problem is to maintain the quality of ever-changing applications during development and maintenance.
This is especially prevalent when Jakarta EE applications are developed and not properly tested in an isolated and cohesive manner. Proper integration testing helps to avoid both the "works on my machine" problem, and ensures developers can change the application effectively without breaking it. However often teams struggle with it, due to a lack of standardized testing solutions and the unpredictability of real-world conditions.
Here, I present an effective method for Jakarta EE integration testing, using Payara Platform and Testcontainers in my example.
Within Payara Server, the JMX system is used to store all the data that the monitoring service captures of the modules within the runtime.
You can use any tool that can connect to the JMX system to collect these data and monitor the environment. Besides this direct access, the notifier service can send this information to various channels so that the data can be integrated with external systems.
The Notifier service is modular since October 2020 with version 5.2020.5 so that you can include only those notifiers that you are interested in and use within your environment. These notifiers cover a wide range of channels, from typical destinations like email, JMS Queues, over APM tools like DataDog and NewRelic to communication platforms like Teams, Slack, and Discord.
In this blog, we take a look at enabling JMX Monitoring for the JVM Heap Size, monitoring the process Heap Size, and then sending that information to a Discord channel.
One of the cornerstones of any modern Payara Platform architecture is the use of the Domain Data Grid. The Domain Data Grid allows multiple Payara Server or Payara Micro instances to join and form a robust cluster of interchangeable nodes that can share data between each other and grant High Availability and Failover capabilities to any applications deployed in the cluster.
This is an updated blog of the original which was published in May 2016
Payara Server provides the Health Check Service for automatic self-monitoring in order to detect future problems as soon as possible. When enabled, the Health Check Service periodically checks some low level metrics. Whenever it detects that a threshold is not met, it triggers alert notifications that allow to detect undesired behavior and predict possible failures. All of these automatic checks are very lightweight and run with a negligible impact on performance.
La mayoría de las aplicaciones web modernas necesitan alguna manera de almacenar datos en una base de datos. Generalmente, Oracle proporciona la mejor solución de RDBMS en lo que respecta a seguridad, soporte y escalabilidad. Oracle XE es la versión más adecuada para desarrolladores para proyectos pequeños o personales, y además debería ser compatible con la versión completa de la base de datos Oracle. Esta guía te adyudará a configurar tanto Oracle XE y Payara Server.
Cuando estás probando una aplicación para ejecutarla en Payara Server, continuamente probar la aplicación desde tu IDE es extremadamente util (ese es su proposito, despues de todo). Si estás utilizando NetBeans esto es muy sencillo. Sigue los pasos de este blog para configurar Payara Server en NetBeans para ejecutar tus aplicaciones web.