Your architecture isn't 100% clear to me, but if I understand correctly:
- Machine A has your Java program which uses JMS. The JMS makes use of MQ
Client as the messaging provider.
- Machine B has an MQ queue manager installed, and the MQ Client from
Machine A is connecting to it.
- Machine C has WESB installed.

I'm not a WESB expert by any means, but I know that WESB can support "MQ
Export" and "MQ Import" bindings that can connect to an MQ via MQ Client.
So that means that your program running on Machine A could certainly send
(and receive) messages to the QM on Machine B, and WESB on Machine C could
receive (and send) them.

In this scenario, however, I wouldn't use the term "message could be
forwarded". Your JMS client program would just be depositing messages in a
queue (physically on Machine B) and the WESB would be retrieving them from
that same queue on Machine B. There is no queue manager forwarding here....
the QM is just holding the messages.

An alternative scenario that could probably be looked at would be to have
the WAS SIBus which underlies your WESB connect (via an "MQ Link") to the QM
on Machine B. In this case, there really would be "store and forward" of
messages between "queue managers" (the MQ queue manager and the SIBus). The
result would be the same, but there are some significant differences. Hope
this is clear.

--
Carl

Thanks for your invaluable comment.



have a nice day.