Elytron is a new security framework that ships with WildFly version 10 and Red Hat JBoss Enterprise Application Platform (EAP) 7.1. This project is a complete replacement of PicketBox and JAAS. Elytron is a single security framework that will be usable for securing management access to the server and for securing applications deployed in WildFly. You can still use the legacy security framework, which is PicketBox, but it is a deprecated module; hence, there is no guarantee that PicketBox will be included in future releases of WildFly. In this article, we will explore the components of Elytron and how to configure them in Wildfly.
The Elytron project covers the following:
- Secure credential storage
In this article, we are going to explore using SSL/TLS in WildFly with Elytron.
Continue reading “Elytron: A New Security Framework in WildFly/JBoss EAP”
JBoss Enterprise Application Server 7 has been out since June, and if you build and deliver using a Java EE environment and haven’t yet upgraded to EAP7, it’s time to make the jump.
Here’s a look at what’s new in JBoss EAP 7, what has changed since JBoss EAP 6, and how to get the most out of JBoss EAP 7 as your Java EE7 server.
JBoss EAP 7 is bassed on WildFly Application Server 10, which provides a complete implementation of the Java EE 7 Full and Web Profile standards. WildFly 10 does much to simplify modern application delivery based on containers and microservices.
JBoss EAP 7 features certified support for Java EE7 and Java 8 SE. The WildFly integration brings experimental Java 9 support, too. It also supports current development snapshots of Java 9, which is expected for release this fall.
The JBOSS EAP 7 release is available for download from JBoss.org.
Continue reading “Five features of JBoss EAP that help you get production ready”
In this blog series we will present several ways to deploy an application on an EAP Domain. The series consists of five 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. In the part one, we set up a simple EAP domain with the following topology:
Continue reading JBoss EAP 7 Domain deployments – Part 3: Domain deployment with Common Language Interface CLI.
If you are using JBoss Enterprise Application Platform (EAP) for J2EE development, the CloudBees Jenkins Platform provides an enterprise-class toolchain for an automated CI/CD from development to production.
The CloudBees Jenkins Platform now supports integrations with both Red Hat JBoss Enterprise Application Platform (EAP) and Red Hat OpenShift across the software delivery pipeline. This enables developers to build, test and deploy applications, with Jenkins-based continuous delivery pipelines in JBoss via JBoss EAP 7 or JBoss EAP 7 on OpenShift.
The following examples are based in Jenkins Pipeline plugins, which create complex pipelines, if needed, , to model their software delivery process. If you are not familiar with with the CloudBees Jenkins Pipeline plugin you may find these two blog posts helpful for ramping up: Using the Pipeline Plugin to Accelerate Continuous Delivery — Part 1 and Part 2.
Let’s get started. In a typical CI/CD pipeline, your process would be similar to this one:
- Developers commit code to the SCM, which will notify Jenkins via web-hooks.
- Jenkins compiles the code and execute a series of test on it: static code analysis, code metrics, unit testing, etc.
- If everything goes well, Jenkins would deploy the code to a development environment. This step typically /may require a manual approval depending on the use of that environment. A typical use case is having the application deployed just to be able to run further validations with tools like Selenium.
- The steps that follow would promote the application between the various environments and to validate that the deployment was correct.
Let’s see how the build, deployment and promotion between the various environment can be done for both types of JBoss installs, to JBoss EAP7 and to JBoss EAP 7 on OpenShift, and the differences between them.
Continue reading “Continuous Delivery to JBoss EAP and OpenShift with the CloudBees Jenkins Platform”
JBoss EAP 7 was recently released, and brings with it a whole host of new features and support, such as support for Java EE 7, Undertow (a highly scalable web server), reduced port usage, graceful shutdown, improved GUI and CLI management, and much more.
Go ahead and download it, unzip, and run
bin/standalone.sh and check out all these great features. What’s that? It didn’t work? Did you check that your JRE is compatible? Are there outstanding incompatibility or security issues that may be resolved in an available patch? Perhaps you’ve already installed it elsewhere on your system and you are trying to install a conflicting version. You’re not running it as root are you?
ZIP files are awesome for getting bits up and running quickly (as a developer I use them myself quite a bit), but its simplicity hides many issues related to production software management, such as those I just mentioned. It’s perfect for cross-platform developers or those non-RHEL CI/CD setups but for production RHEL systems it’s the tl;dr of enterprise software deployment. This is where Red Hat and RPM can help. You can be sure of what you’re installing, that it’ll work securely, that you’ll know it’s there when asked, and that it’ll be manageable using your other investments (think RHEV+RHEL+Satellite+JBoss).
Continue reading “Installing JBoss EAP 7 on RHEL using RPMs”
Over the years, I’ve come across many command line interfaces (CLI) to larger applications, each with varying levels of access and power. Having a CLI at all is a great first step for an application, as it opens up a much wider range of possibilities: administration, extension, and trust.
CLIs also promote scriptability – the ability to create and maintain repeatable scripts, and the easier it is to develop said scripts, the better. Sometimes scripts can solve issues that developers of the app never thought of. (Pro tip: find good user experience designers who know the product and are comfortable on the command line, then put them in charge of the CLI user experience. Your users will love you.
Continue reading “Offline CLI with JBoss EAP 7”
Automated testing is one of the hardest, but also the most important thing to get right when doing Continuous Delivery or DevOps. Recently Aslak Knutsen and I hosted a webinar with the title “Continuous Development with Automated Testing”. The webinar had quite a few viewers (and maybe that was one of the reasons that the demo in the webinar didn’t exactly go as planned.)
Continue reading Continuous Development with Automated Testing
The Java Persistence API (JPA) provides Java developers with an object/relational mapping facility for managing relational data in Java applications. The latest version of the JPA standard is 2.1 and is part of Java EE 7.
JBoss Enterprise Application Platform is a fully certified Java EE application server and JBoss EAP 7 which is currently in Beta is certified according to the most recent Java EE 7 specification.
Hibernate is one of the most popular JPA implementations and is known for it’s High Performance, Scalability and Reliability.
For more details about JPA and Hibernate I recommend reading Java Persistence with Hibernate, Second Edition.
Continue reading “What’s new with JPA 2.1 and Hibernate 5 in JBoss EAP 7”
This article describes how efficient development is on JBoss EAP 7. It will also give example of different build tools and Integrated Development Environments (IDEs) to use for application development on JBoss EAP 7. Additionally it will briefly explain how dependency management works for Java EE 7 and JBoss EAP specific artifacts.
Finally there is a step-by-step guide that demonstrates how fast and efficient it is to develop on JBoss EAP 7.
Continue reading “Run your first Java EE application with JBoss EAP 7 Beta”