Enterprise grade Java.
You'll read about Conferences, Java User Groups, Java, Integration, Reactive, Microservices and other technologies.

Friday, September 25, 2015

WildFly 10 CR 2 Released - Java EE 7, Java 8, Hibernate 5, JavaScript Support with Hot Reloading

08:20 Friday, September 25, 2015 Posted by Test No comments:
, ,
Yesterday the WildFly team released the latest version of WildFly 10. The CR2 will most likely be the last before the final release which is expected in October. Many new features made it into this release, even if the mainly supported Java EE specification is 7 as with WildFly 8 and WildFly 9 which now makes three server versions, which implement the Java EE 7 Full and Web Profile standards. Ultimately WildFly 10 will lead to Red Hat JBoss Enterprise Application Platform (EAP) 7, the supported Java EE offering of Red Hat.
Learn more about JBoss EAP 7 in the Summit presentation (PDF) by Bilge Ozpeynirci  (Sr. Product Manager) and Dimitris Andreadis (Sr. Engineering Manag)

New Features At A Glance
  • Java 7 support has been discontinued allowing for deeper integration with the Java 8 runtime. While Java 9 is still in development, this release runs on the current development snapshots.
  •  WildFly 10 CR2 includes the ActiveMQ Artemis project as its JMS broker, and due to the protocol compatibility, it fully replaces the HornetQ project.
  • In addition to the offline CLI support (WildFly 9) for standalone mode, you can now launch a host-controller locally within the CLI. 
  • WildFly 10 includes the Undertow JS project, which allows you to write server side scripts that can pull in CDI beans and JPA Entity Beans. Learn more in this blog-post by Stuard Douglas.
  • WildFly 10 adds the ability to deploy a given application as a "singleton deployment" with automatic failover to another node in case of failure.
  •  HA Singleton MDBs and MDB Delivery Groups.
  • WildFly now pools stateless session beans by default, using a pool size that is computed relative to the size of the IO worker pool, which is itself auto-tuned to match system resources. 
  • Migration Operations for old subsystems such as jbossweb (AS 7.1), jacorb (WildFly 8), and hornetq (WildFly 9)
  • Hibernate 5 included
Getting Started
Download WildFly CR2 from the wildfly.org download site. Unpack into a folder of your choice and unzip the distribution. Change to the bin directory and type:
$ standalone.sh|bat
Which will start WildFly lightning fast:
08:09:58,353 INFO  [org.jboss.as] (Controller Boot Thread) Full 10.0.0.CR2 (WildFly Core 2.0.0.CR5) started in 3686ms
Access the main page with your browser at http://localhost:8080 and see the new admin console at http://localhost:9990

Please give it a try with all your latest projects and let the team know, what you need or missing. Reach out to them via:

Wednesday, September 23, 2015

50% Off for Top WildFly Books

12:27 Wednesday, September 23, 2015 Posted by Test No comments:
I do some reviews from time to time on this blog and as a reward for my readers, I was offered a 50% code from Packt Publishing for any of the following books. Please keep in mind, that the code is only valid until 07th October 2015. extended until October 30, 2015!

WildFly Configuration, Deployment, and Administration - Second Edition
The book starts with an explanation of the installation of WildFly and application server configuration. Then, it moves on to the configuration of enterprise services and also explores the new web container Undertow. It then covers domain configuration, application deployment, and application server management. By the end of the book, you will have a firm grasp of all the important aspects of clustering, load balancing, and WildFly security. This guide is invaluable for anyone who works with or is planning to switch to WildFly.
Find the complete book review on my blog.
Get 50% off with the code MULTIFOUR50 when ordering.

WildFly Performance Tuning
This practical book explores how to tune one of the leading open source application servers in its latest reincarnation. In this book, you will learn what performance tuning is and how it can be performed on WildFly and the JVM using solely free and open source tools and utilities.
Find the complete book review on my blog.
Get 50% off with the code MULTIFOUR50 when ordering.

WildFly Cookbook
With practical and accessible material, you will begin by learning to set up your WildFly runtime environment, and progress to selecting appropriate operational models, managing subsystems, and conquering the CLI. You will then walk through the different balancing and clustering techniques, simultaneously learning about role-based access control and then developing applications targeting WildFly and Docker.
Get 50% off with the code MULTIFOUR50 when ordering.

Tuesday, September 22, 2015

Running OpenShift Origin on Windows

09:56 Tuesday, September 22, 2015 Posted by Test No comments:
OpenShift is the most interesting PaaS offering these days for me. Not only because it is part of the Red Hat family of products, but because it holds everything I expect from a modern PaaS. It supports image based deployments (with Docker-Images), abstracts operational complexity (e.g. networking, storage and health checks) and greatly supports DevOps with an integrated tooling stack. On tiny drawback for now is, that the latest v3 isn't available as a free online service. If you want to play around with it, you can set it up on AWS yourself or run it locally. As usual, most of the documentation available only covers Linux based systems. So, I am going to walk you through the first steps in getting OpenShift v3 Origin up on your local machine.

Install the latest versions of Vagrant and Virtualbox. You'll need both and they will make your life easier. Also, please install the OpenShift client for windows. Download the one for your os from the origin project on github. The windows build has 16 MB. Next is to unpack it into a folder of your choice. Make sure to add this folder to your PATH environment variable.
set PATH=%PATH%;"D:\Program Files (x86)\openshift-origin-v1.0.3"

Method One: Fabric 8 Vagrant All In One
The Fabric 8 team has a complete Vagrant based all-in-one box ready for you to run. It also contains Fabric8 but you get a fully operational OpenShift Origin too. All you have to do is to clone the fabric8 installer git repository:
$ git clone https://github.com/fabric8io/fabric8-installer.git
$ cd fabric8-installer/vagrant/openshift
You need to install an additional vagrant plugin:
vagrant plugin install vagrant-hostmanager-fabric8
Unfortunately for Windows no automatic routing for new services is possible. You have to add new routes manually to %WINDIR%\System32\drivers\etc\hosts. For your convenience, a set of routes for default Fabric8 applications has been pre-added. If you expose new routes, you will have to add them manually to your hosts file. Now you're ready to start vagrant:
$ vagrant up
If you do that for the first time, a bunch of Docker images will get pulled. So prepare for a little coffee+++ break. When that is done, point your browser to http://vagrant.f8:8443 and use any user/password combination to access the OpenShift console.
Login with the oc command line tool and see, if that works, too:
$oc login https://vagrant.f8:8443

Method Two: Use the pre-built Vagrant Box 
Using the pre build vagrant box from the v3developer training is probably the most convenient way to get everything up and running. The following is part of the complete v3 Hands-On-Lab and there will be a more polished version available soon, hopefully.
Go to: bit.ly/v3devs and change to the BinariesAndVagrantFile folder. Download the openshift-bootstrap-1.0.6.box (Attention 4.5 GB!) and the Vagrant file.
Rename the .box file to openshift.box using your file manager and edit the Vagrant File with notepad and change all references from openshift3­bootstrap to openshift and then save the changes. Now you need to add the box:
$vagrant box add openshift openshift.box
And you're ready to bring up the vagrant box:
$ vagrant up
When that is done, point your browser to http://localhost:8443 and use any user/password combination to access the OpenShift console.
Login with the oc command line tool and see, if that works, too:
$oc login https://localhost:8443

Method three and four: Build from Source and Docker Container
The OpenShift documentation mentions two other methods of getting OpenShift Origin to run locally. Either as a docker container or by building in locally in a vagrant box. I couldn't make any of them work on my Windows 7.

This was just a little exercise to lay some groundwork for the upcoming blog-posts. I am going to show you more about how to build your Java EE projects with OpenShift's source-to-image technology and how to run and scale Docker containers.