Hi Balint- Yes, you can migrate Artemis to ActiveMQ Classic. There are a couple approaches:
1. Naturally drain the Artemis brokers using application consumers, and then cut-over to ActiveMQ Classic brokers. In this scenario, there are no messages to migrate, since the applications have consumed all of them. This is the simplest and most straight-forward. 2. Build JMS Bridges from Artemis to ActiveMQ Classic. You can do this using Apache Camel or other integration tools 3. Extend tooling to take Artemis exports and import into ActiveMQ. #3 hasn’t been built into the Apache ActiveMQ command line tools, but I recently did some work on the export tooling and would have some cycles to add import capabilities as well. The next step would be to open a JIRA requesting a new feature in AcitveMQ for import support of the Artemis export message format. Thanks, Matt Pavlovich > On Oct 7, 2024, at 5:58 AM, Nagy, Balint, Dr. (AHA/FP-1) > <balint.n...@audi.hu> wrote: > > > Hi, > > I'm writing this email regarding the ActiveMQ Artemis Migration, specifically > the KahaDB Export Tool. > > When I tried to migrate my ActiveMQ Classic broker to Artemis, I found that > the KahaDB Export Tool is a Linux tool, but my environment is on Windows and > couldn't execute the export. Because of our policy, I mustn't use features > like WSL to solve this issue. > Is there a Windows-based KahaDB Export Tool or is there any solution that > could work without any extra application? > > > My other topic: is it possible to "migrate back" to ActiveMQ Classic from > Artemis? In some cases, that would be useful if I could export the message > store of Artemis and import it in the a Classic broker. > > > Thanks in advance for your support. > > Best Regards > > > > > > INTERNAL --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org For additional commands, e-mail: dev-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
