We are using Wildfly 10 and we want to use Red Hat AMQ 7 (standalone) remotely. I checked few documentation and found that ActiveMQ Artemis is also inbuilt in Wildfly 10, and I also configured it successfully to send and receive messages.
But as per our requirement, we want to use a remote AMQ broker so that it can be used as a centralized server and will be best suited in our enterprise requirement. Even I also want to understand the exact difference in using the ActiveMQ Artemis embedded in Wildfly and a remote Red Hat AMQ 7 instance, but I could not find enough information about it. If anyone is having any idea about it, please explain it.
I think there are three approaches to implement remote Red Hat AMQ.
Use the embedded ActiveMQ Artemis as a standalone server. I mean if we will install this Wildfly 10 in a separate server and if we can use that only for integration purpose and use the embedded ActiveMQ Artemis to connect with our Java application running on separate servers.
Install Red Hat AMQ 7.x as separate broker and connect it from the java application deployed on Wildfly 10. I checked Red Hat documentation and one point bothered me about this implementation as Red Hat claims "Currently AMQ 7.2 is only supported as a stand-alone broker. It has not be certified with EAP 7.0 or earlier. It is planned to be tested both as the internal broker of EAP 7.1 and as an external broker with EAP.". This is my preferred approach but I am not getting any documentation to implement it even Red Hat also not did it yet.
Install Apache ActiveMQ Artemis 2.x and integrate it from the application deployed in Wildfly 10.
I tried to get this information but as of now there is not much information available on internet for Artemis. It will be a great help if someone can explain the differences with pros and cons in above approaches.
Regard's
Ram
Related
I have done everything possible from my end.
OS Linux data is coming from server.
but data of wildfly (i.e heap thread etc.) is not coming.
does anyone have template of wildfly 20?
There are several solutions widely available on the internet
Zabbix-JBoss-Agent
Zabbix_wildfly_eap_jboss_monitoring
WildFly (formerly JBoss) is a Java application and can be monitored with JMX agent
I would strongly recommend upgrading to a newer version of Zabbix, as version 4.0 will become unsupported on October 31, 2021.
I am new to Redhat and trying to deploy Redhat decision manager( decision central) V7.2 on tomcat server(v 8).As per online help I don't see any documentation to deploy decision central on tomcat. Please let me know if anyone has tried it before?
Red Had Decision Manager is not supported for Tomcat. Only Kie Server can be used with Tomcat.
See Red Hat Decision Manager 7 Supported Configurations and anchor [5] near different servers for more details.
We are migrating from old Fuse Source ESB to JBoss Fuse ESB 6.2 version, so we look for better deployment strategies using the newer version of JBoss Fuse ESB 6.2 with Disaster recovery (multi data center deployments) & with in same data center - a Master/Slave (Primary/Secondary) nodes with automatic fail over options.How to achieve this in newer version?
Based on your requirements, I believe Fuse Fabric will work well. You can read more here
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.0/html/Getting_Started/files/Deploy-Scalable.html
What is the question exactly? What is your architecture?
DR for what, Fabric, A-MQ, Camel containers...
I've blogged on the topic here that might be a good start.
Is communication by JMS between JBoss 5.x and JBoss 6.x possible?
Or do you need same version on both sides because of class version compatibility reasons?
JBoss 5 and 6 use different JMS implementations (JBoss Messaging and HornetQ, respectively), so I suspect that they're not interoperable. However, since HornetQ is based on the Jboss Messaging codebase, it's possible that the HornetQ broker in JBoss 6 can be made interopable, but it's not going to be easy.
I suggest trawling the HornetQ documentation to see if it's even possible.
I have to set up a Hornetq Core-Bridge to a Hornetq 2.1.X Server, but I would like to use a more updated version on my side of the architecture (2.2.X). Is it compatible?
I haven't found info about it on documentation (as always btw, regarding to hornetq).
Obs: The 2.1.X Server is running on a JBoss AS, and mine is on stand-alone mode.
Until hornetq 2.2.2, hornetq didn't have version compatibility support. That means that you would need all your servers on the same version. (same as you would need for your clients).
After hornetQ 2.2.2 we offer version compatibility, however the client has to be older than the server. We don't test a 2.2.5 talking to a 2.2.2 server.
So, if the core-bridge is installed in a 2.2.2 talking to a 2.2.5, you would be fine.
a 2.2.5 talking to a 2.2.2.. probably not
A 2.1.X talking to 2.2.x.. definitely not.