How does JON intersect JBoss EAP 6 "Domain Mode"?

Latest response

Could anyone tell me if there are any feature matrixes for JON that I could compare with a features matrix for JBoss EAP mode? I am the lead JBoss admin for a small shop with limited resources in terms of bodies, time, and budget, and although I am familiar with administering JBoss EAP 5.1.2, I do not have any experience, and no training, with JBoss 6.3. We recently attempted to upgrade to 6.3, and had the servers working in clustered mode using static TCP/IP clusters, but again due to time and budget constraints, the development team was unable to successfully migrate their code to 6.3 and so we've put off migrating until April 2015 time frame. This is great as it gives us extra time to plan, but given that the team for designing and implementing the JBoss solution is very small, we need to make a decision whether to

a) implement JON and stick with standalone mode for the time Spring deadline, or
b) Implement (and learn how to administer) EAP 6.3 Domain mode, and forego implementing JON until a later date.

I understand that there is a lot of overlap between JON and JBoss EAP 6.* Domain mode in terms of functionality, but I would be very interested in hearing other administrators opinions on these two choices.

Specifically, is there anything JON buys me in terms of fucntionality that I can't get from Domain mode in EAP, and vice versa? I understand with JON that I can monitor more products than Just EAP, for example, as well as do code deployments.

thanks for your insights,



A feature matrix comparing JBoss ON to JBoss EAP does not exist. The feature set is very different and cannot really be compared. As you suggested, JBoss EAP configured in domain does have some overlap into JBoss ON capabilities--specifically dealing with grouping of like resources for the purpose of deploying applications and other resources.

JBoss ON can be used with JBoss EAP configured in standalone or domain mode. Obviously, standalone mode with JBoss ON provides you greater flexibility in how you treat each of your JBoss EAP servers but one could also have the opinion that domain is easier to maintain and configure when you prefer to do so outside of JBoss ON.

Whether using JBoss EAP standalone or domain, JBoss ON provides you with a unified management and monitoring system across all your JBoss deployments. Many of JBoss ON's capabilities are not available in JBoss EAP domain or standalone modes. To name a few:

  • alerting based on resource availability and statistics;
  • recording of availability and statistics;
  • provisioning of JBoss servers to supported operating systems;
  • grouping of servers and other resources based on logical types such as production vs. staging regardless of domain or standalone configurations;

I do not think you should consider JBoss EAP domain and JBoss ON equals or comparable in any way. Instead, you should decide whether you want to use JBoss EAP standalone or JBoss EAP domain. You can then use JBoss ON to manage and monitor either choice.

Hope this helps,


This is really helpful information and insight, thanks! I think that I am going to have to bite the bullet, take some time, and research the capabilities of JON, as well as sit down and read up on Domain mode. I was hoping to shortcut the research and see if I could find out where the overlap is between JON and domain mode, if it even exists. My biggest concernis that I'll get the domains set up, and our development customers will immediately change the topology and I"ll be constantly reconfiguring Domains. The flipside of that concern is that I"ll implement JON on standalone servers, and then decide we want to use domain mode, and it'll be a horrible headache to reconfigure JON.
Again, thanks for your insights.