We need to decide how we are going to support remote JMS client on EAP7. There are basically two options:

1. We can use ActiveMQ Artemis client library and directly communicate with the same JMS provider on the server side. I have verified that this works unless you use secured connection. If you turn on SSL in our remote JMS client, it uses HornetQ-specific connection factory. If we decide to go this way, we need to update JMS client to be able to use HornetQ or ActiveMQ Artemis client libraries (based on if you communicate with Business Central on EAP6 or EAP7) when you turn on SSL.
2. The other option is not to do any changes in the remote JMS client and set up EAP7 legacy connectors for HornetQ. However, this will need a lot of configuration on the server side. According to the EAP7 documentation, this approach will also require us to create legacy HornetQ JMS destinations. I haven't managed to configure EAP7 this way even in unsecured mode yet but will try to do it soon.