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.
Related
My organization's development environment is quite old and still uses JBoss 4.0.5 GA as a Development Application server. We would like to switch to modern servers such as wildlfly. What are the steps to be taken for the same? are there any resources available online for this? which version of Wildfly should we migrate to considering our application uses primarily JAVA EE8 API?
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
We got farm of Red Hat servers which has Jboss 6.1 in our environments. Now we need to upgrade Jboss AS to 6.4. The easy way is to deploy the new version on the server and copy the config files and modules to the new jboss instance. It requires additional space in the filesystem.
Is there any other way to upgrade to 6.4 without having multiple instances. I am looking something like a patch upgrade on the existing Jboss 6.1 instance in CLI mode.
Please update your valuable thoughts.
Cheers,
Jose
You can use patch in CLI mode, See the guide[1]
[1]https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Installation_Guide/sect-Patching_JBoss_EAP_6.html
need to migrate from Fuse ESB Enterprise 7.0.0.fuse-061 to latest jboss-fuse-6.2.0.redhat-133.what are the main difference between these two versions?
what new features that are evolved in the latest jboss-fuse-6.2.0.redhat-133 that not exists in Fuse ESB Enterprise 7.0.0.fuse-061.can you please provide the links which gives us differences?
what are the camel,karaf ,cxf and activemq versions in these two versions?
jdk 1.6 can be used on former one and jdk1.7,jdk1.8 will be used in latest one.
You can find the release notes here: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2/html/Release_Notes/index.html.
Also checkout Jon Anstey's blog: http://janstey.blogspot.de/2015/06/jboss-fuse-62-is-out.html
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.