Looks like we have some confusion here.
In EntireX 7.3 you find:
EntireX RPC BMQ Bridge
EntireX RPC Broker Message Queue (BMQ) Bridge allows standard RPC clients to send and receive asynchronous messages and to make those messages persistent in the Broker. This enables customers to use the existing EntireX Communicator wrappers for asynchronous and persistent messaging.
EntireX WMQ Bridge
EntireX WMQ Bridge runs as an RPC server and processes RPC client calls. It is used to send messages to and receive messages from a WebSphere MQ Queue. This means that existing EntireX wrappers can be used for communication with WebSphere MQ.
EntireX WMQ Bridge Listener runs as a listener on a WebSphere MQ queue and passes messages to an RPC server. It is used to send messages received from a WebSphere MQ queue to an RPC server applications. This means that existing RPC servers can be used for communication with WebSphere MQ.
With EntireX 8.0 we streamlined the naming conventions and renamed
EntireX WMQ Bridge to EntireX WebSphere MQ RPC Server
and EntireX WMQ Bridge Listener to EntireX WebSphere MQ Listener.
Also with 8.0 the EntireX RPC BMQ Bridge has been dropped because this functionality is now available directly with Reliable RPC.
#EntireX#Mainframe-Integration#webMethods