Continue reading “Announcing Red Hat Developer Studio 11.1.0.GA and JBoss Tools 4.5.1.Final for Eclipse Oxygen.1A”
To be as simple as possible, we will walk through a stand-alone use-case.
Usually, when we require having messaging features in our stand-alone environment, we use full profile for EAP container.
Continue reading “How to start multiple Artemis brokers inside Red Hat JBoss EAP-7 container in Master/Slave fashion”
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”
“I used WildFly Swarm to shrink my app from 45 megabytes to only 2243 bytes.”
I was recently playing around with various techniques for packaging Java microservices and running on OpenShift using various runtimes and frameworks to illustrate their differences (WildFly Swarm vs. WildFly, Spring Boot vs. the world, etc). Around the same time as I was doing this an internal email list thread ignited discussing some of the differences and using terms like Uber JARs, Thin WARs, Skinny WARs, and a few others. Some folks were highlighting the pros and cons of each, especially the benefits of the thin WAR approach when combined with docker image layers.
Continue reading “The Skinny on Fat, Thin, Hollow, and Uber”
JBoss Application Server ships with
PicketLink module for enabling
SAML based SSO.
PicketLink is an open source module and it is
SAML v2.0 complained, for more information about ‘PicketLink’ please visit picketlink.org.
Now the requirement is to enable SAML based SSO in JBoss Application Server where IDP is OKTA.
Continue reading “Integrating PicketLink with OKTA for SAML based SSO”
Continue reading “Announcing Red Hat Developer Studio 11.0.0.GA and JBoss Tools 4.5.0.Final for Eclipse Oxygen”
Camel Quartz can be a useful component for jobs that need to run at a particular time every day. Recently on a client site, we had a need for about 15 different jobs that each created a differently formatted file and send each file to a particular destination. While this was straightforward to get setup on a single machine, once we started deploying our camel routes to multiple servers the jobs started to kick off on both machines. To resolve this issue we needed to create a job store.
Continue reading “Using Clustered Camel Quartz Jobs on JBoss EAP”