I am planning to migrate from Fuse jboss-fuse-6.3.0.redhat-329 to Fuse 7. I am using camel version 2.17.0.redhat-630329. Can anyone please guide me on the steps and issues faced while migrating?
First of all its good that you plan to upgrade from Fuse 6.3 to 7.x.
I recommend to upgrade to the latest Fuse 7.7 release in order to benefit from additional bug fixes, CVE fixes and enhancements.
Your migration to Fuse 7 will upgrade Camel from 2.17 to 2.21.
I suggest you have a read over the Fuse 7.0 migration guide [1], which specifically covers the migration from Fuse 6.3 to 7.
Then you may also want to peak at the migration guide of the specific 7.x release that you are upgrading to, for 7.7 it will be [2].
Please also check for deprecated components...
In terms of Camel, it will depend on the Camel components used if there are any code changes needed or not. For the vast majority of components no changes should be required.
Potentially you only need to recompile your application against the latest Fuse 7 BOM and redeploy the application (in case of Karaf of EAP runtime).
I hope this helps as a starting point.
[1] https://access.redhat.com/documentation/en-us/red_hat_fuse/7.0/html/migration_guide/index
[2] https://access.redhat.com/documentation/en-us/red_hat_fuse/7.7/html/migration_guide/index
Related
Need to migrate all indexs or upgrade the indexs
Is it possible 6.x to 8.x directly or 6.x to 7.x and then 7.x to 8.x
Kindly help me on this any one done
You should start reading the complete documentation provided to upgrade to Solr 8.x from pre 7.x version, before starting the update process.
When upgrading between major versions (for example, from a 7.x release to 8.x), a best practice is to always reindex your data.
When even skipping a major version, like in your case, an index migration is not supported and requires a reindexing of the complete data.
We are looking to upgrade from Apache Solr 4.7.2 to ApacheSolr 7.6. The documentation is not very clear.
Please reply with your valuable notes
Thanks in advance
No. As seen on the reference page for the Index Upgrader tool:
Indexes can only be upgraded from the previous major release version to the current major release version.
This means that the IndexUpgrader Tool in any Solr 7.x release, for example, can only work with indexes from 6.x releases, but cannot work with indexes from Solr 5.x or earlier.
If you are currently using an earlier release such as 5.x and want to move more than one major version ahead, you need to first upgrade your indexes to the next major version (6.x), then again to the major version after that (7.x), etc.
There's also an indexupgrader tool that attempts to perform this sequence automagically for you from your current version.
I am using camel-salesforce component in jboss-fuse-karaf-6.3.0.redhat-187. Camel version 2.18.x provide replay with push-topic. If the client subscription got lost we can replay the old notification.
As per Red hat component details page , JBoss Fuse 6.3 support camel version 2.17.0.
https://access.redhat.com/articles/348423
Is there any way we can use camel 2.18.x version with jboss-fuse-karaf-6.3.0.redhat-187, so we use salesforce replay.
Will highlty appreciate if someone could provide any link , document or any red hat jira issue.
We already tried different stuff
1.) Try to merge 2.18 replay classes with 2.17 , there is lot of changes in 30-40 classes so tough doable.
2.) Try to build with 2.18 classes with 2.17 jars .Still not worked with karaf
3.) Fuse 6.3 not support camel 2.18.x so directly using 2.18 not making sense.
Kindly let me know if need any further information.
Thank you so much in advance.
No you should use the version that is shipped with JBoss Fuse, that is the certified version. Use Red Hat customer portal to get help/support with your fuse product. If there is a bug/feature in camel-salesforce you are looking for in JBoss Fuse 6.3 that is only available in later Camel release, then the Red Hat team can help you by looking into whether that can be backported and provided to you or what else you can do.
I am trying to build a highly available, scalable and performance optimistic Jboss cluster system. I will be using Infinispan subsystem for caching service.
I started off with Jboss 7.1.1 Final version but later on found that it has some really serious bugs. Also, the infinispan subsystem was not behaving as per my requirements in the same.
As of now, I need to evaluate different versions of Jboss which suffices above mentioned requirements.
Please let me know which the most stable and latest version of Jboss currently available.
Just for information, I am performing the whole stuff in Cloud (AWS).
JBoss Application server was renamed to Wildfly, checkout its downloads page. Right now it is stable 9.0.1 (I think this is using Infinispan 7.x) and unstable 10.0.0.Beta2 (I think it still uses 7.x too since Infinispan 8 was not released yet, but it's possible that version 8 will get into the final release).
I have been working with Jboss Fuse 6.1.0.redhat-379 for about a month with great results and higher productivity in EIP. Thank you very much to the community for building such a great product.
Now I am getting ready to deploy my bundles in a dev enviroment with several camel routes and even multiple camel contexts in a single bundle and I'm noticing a weird behavior regarding camel contexts JMX display. The bundle with the multiple camel contexts is only showing the first context, others contexts work fine but they are missing in camel JMX display in hawtio.
After research about this behavior I encountered with this JIRA issue https://issues.apache.org/jira/browse/CAMEL-7545 opened by Claus, describing exactly this problem and manifesting that there are Fix Versions (2.12.4, 2.13.2, 2.14.0)
AFAIK my Jboss Fuse version is distributed with camel 2.12.0.redhat-610379 version and there is a mayor 2.14.0.redhat-620031 version that supposedly will fix this issue and it will be bring many other features like json path and sql generated keys.
Is there a way to upgrade versions of camel features in Jboss Fuse?
UPDATE
There is a similar question for this topic (Updating camel version in fuse esb) accepted answer discourages trying to update the version, however, I think it should be better to permit version upgrades if they fix issues
Not a 100% on this but the rollup patches might include the 2.12 fixed versions. Install the latest patch and see if that fixes the issue.