Message Queuing

Responder uses Message Queuing (MSMQ) in two different ways. MSMQ .NET Remoting Channel is built on top of MSMQ to facilitate communication between Responder components. Responder PubSub uses MSMQ Multicast and PGM to provide reliable multicasting between Data Services and Responder Explorer using message queues.

MSMQ must be enabled on the machine that hosts the Responder services (Data Services, Prediction Services and Archive Services) and on the client machine. When you run the Responder services and Responder Explorer, the necessary queues are automatically created and the appropriate permissions assigned.

MSMQ .NET Remoting Channel

Responder .NET Remoting Channel uses MSMQ to provide one-to-one communication between the various Responder components.

Enable Message Queueing
Assign Permissions to the Oracle Directory (Responder services only)
Control Network Interface Binding

MSMQ Multicast (PubSub)

Responder PubSub uses MSMQ Multicast to provide one-to-many communication between Data Services and Responder Explorer.

Control Network Interface Binding

IP Multicast (Responder Events)

Responder events .

Control Network Interface Binding

More detailed information about MSMQ .NET Remoting Channel and MSMQ Multicast is available at the ArcFM Solution Resource Center. The Resource Center also provides troubleshooting information.