The "export" script which is part of the binary distribution is for a *nix environment. However, the export tool is written in Java so it can be run on any platform with a Java Virtual Machine (e.g. Windows). The script basically just takes care of setting the classpath, but you can do that yourself. You just need to include the files in the "lib" and "conf" directories on your classpath and then run "org.apache.activemq.cli.kahadb.exporter.Exporter" with the parameters described in the documentation.
The tool doesn't support the reverse migration from the ActiveMQ Artemis journal to KahaDB, and I don't believe there is any other tool which does. In any case, if you don't want to (or can't) use the KahaDB Export Tool then you can use something like Camel to move messages from one broker to the other while the brokers are running. With Camel you can move messages in either direction. Lastly, please don't post the same question to multiple mailing lists. Thanks! Justin On Mon, Oct 7, 2024 at 6:01 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 >
