Using this method, the sending queue managers think that their messages are routed through an intermediate queue manager before reaching the target queue manager. The target queue manager doesn't actually exist. The 'intermediate' queue manager captures all the message traffic for this virtual target queue manager.
The via routing on the mobile device causes any messages that are put to SERVICEXQM to be directed to Server23QM. Server23QM gets the messages and notes that they are destined for the SERVICEXQM queue manager. It resolves the SERVICEXQM name and finds that it is an alias which represents the Server23QM queue manager (itself). The Server23QM queue manager then accepts the messages and puts them onto the queue.
As an alternative to the above, you can keep the SERVICEXQM in existence, but move it from its original machine to the same machine (but a different JVM) as the Server23QM queue manager. SERVICEXQM needs to listen on a different port, so the connection from Server23QM to SERVICEXQM needs to be changed as well.