We are excited to announce the General Availability release of Red Hat JBoss Web Server 5.0 for Red Hat Enterprise Linux (RHEL). Other platforms are will be released shortly. This release includes a technology preview of transactions processing through Narayana. JBoss Web Server 5 is available in the ZIP or RPM format from the JBoss Web Server 5.0 Maven repository and Container Catalog.
JBoss Web Server combines market-leading open source technologies with enterprise capabilities to provide a single solution for large-scale websites and lightweight web applications. It combines the world’s most deployed web server (Apache) with the top servlet engine (Tomcat) and the best support in middleware (from Red Hat).
Continue reading “The wait is over: JBoss Web Server 5 with Tomcat 9 is here!”
The JBoss Ecosystem is very large and diverse, while you are looking for step by steps and practical introduction to the major JBoss products or looking for tips to improve your business by coupling JBoss Products, this book is for you.
Continue reading “JBoss Developer’s Guide Book is out”
Tomcat by default ships with a couple of Realm implementations like,
JNDIRealm etc. But sometimes it is not sufficient for your organization’s requirements and you are required to apply your own implementations.
Continue reading “How to implement a new realm in Tomcat”
An introduction to microservices through a complete example
Today I want to talk about the demo we presented @ OpenShift Container Platform Roadshow in Milan & Rome last week.
The demo was based on JBoss team’s great work available on this repo:
Continue reading “The CoolStore Microservices Example: DevOps and OpenShift”
In this series of articles, I will present several ways to deploy an application on an EAP Domain. The series consists of four parts. Each one will be a standalone article, but the series as a whole will present a range of useful topics for working with JBoss EAP.
Continue reading “JBoss EAP 7 Domain deployments – Part 2: Domain deployments through the EAP 7.0 Management Console”
One of the common requirements for Java based applications on OpenShift is to have these workloads connect back out to an enterprise database that resides outside of the OpenShift infrastructure. While OpenShift natively supports a variety of relational databases (including Postgres and MySQL) as Docker based deployments within the platform, connecting to an existing enterprise database infrastructure is preferred in many large organizations for a variety of reasons including:
- Inherent confidence in traditional databases due to in house experience around developing and managing these databases
- Ability to leverage existing backup/recovery procedures around these databases
- Technical limitations with these databases in being able to be deployed in a containerized model
One of the strengths of the OpenShift platform is its ability to accommodate these “traditional” workloads so that middleware operations can take advantage of the benefits/efficiencies gained from Dockeri’zed applications while giving development teams a platform to start designing/architecting applications that would fit into more of a Microservice based pattern that would leverage a datastore such as MongoDB or MySQL that OpenShift supports.
In addition to that, another common workflow in many organizations from a deployment point of view is to externalize the database connection information so that the application can be migrated from environment to environment (example Dev to QA to Prod) with the appropriate database connection information for the various environments. In addition, these teams typically work with the application binary (.war, .ear, .jar) deployment as the artifact thats promoted between environments as opposed to Docker based images.
In this article, I will walk through an example implementation for achieving this. A sensitive aspect of this migration process are the credentials to the database, where storing credentials in clear text is frowned upon. I will cover a variety of strategies in dealing with this in a follow on article. For this example, I will be using the following project which contains the source code that I will be covering in this article.
Lets get started!
Continue reading “Connecting to a Remote database from a JWS/Tomcat application on OpenShift”