-
15. Re: Last value queue and delivery delay
I'm not aware of any specific migration documentation. Here is the general documentation for the messaging subsystem. Since HornetQ and Artemis are very similar the configuration should be largely the same. I believe the XML changed a bit so that sub-elements are now attributes, but all the element/attribute names should be the same. Take a look at the standalone-full.xml from Wildfly 10 and you'll see what I mean.
-
-
17. Re: Last value queue and delivery delay
There is migration guide for EAP 7 - https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0.beta/migration-guide/#migrate_messaging_application_changes
I would suggest to copy-paste your messaging subsystem into standalone...xml of WF10. Start in admin-only mode like: "sh standalone.sh -c standalone-full.xml --admin-only" and then call :migrate operation on /subsystem=messaging:migrate in CLI. It will create equivalent configuration for Artemis.
For migrating data you need to export them to xml and then import this xml to WF10. There is CLI operation for import of journal in WF10. How to export the journal to xml file check HornetQ doc.
-
