PubSub Viewer

This stand-alone executable allows you to view PubSub activity - either the internal Responder publish/subscribe activity or OASyS PubSub. This is a debugging tool that can be used to identify a broken Data Services instance. For example, you may have two instances of Data Services running. Use the PubSub Viewer to see which one is transferring messages and which one is not. This tool is installed with Responder Server and requires no configuration.

You can run the PubSub Viewer from a client machine, as well. To do so, you will need to copy the tool and configuration file to the Responder\Client folder on the machine you want to run PubSub Viewer.

The grid shows all messages that travel through PubSub. The status bar at the bottom displays the current subscription as well as the name of your Remote Client Services (RCS) server.

Tools: This executable provides several tools:

Subscriptions: This is a pull-down list that displays the subscriptions that you can view. You may also enter a value in the field. It is automatically added to the list and will remain there.
Subscribe: Once you've selected a subscription, click the Subscribe button to start viewing data. You can view multiple subscriptions.
Unsubscribe: Click this button to unsubscribe from the last subscription selected.
Unsubscribe All: Click this button to unsubscribe from all subscriptions.
Clear: Use this button to clear the data displayed in the grid.
Change Subscribed Message types: The PubSub Viewer allows you to view various types of messages. By default all are selected. Use this pull-down list to modify the types of messages to view.
Send Test Message: Use this button to send a test message and verify that PubSub is working properly.

To start viewing PubSub information, follow the steps below:

Double-click ResponderPubSubViewer.exe to open the Viewer. By default, this file is installed here: C:\Program Files (x86)\Miner and Miner\Responder\Server.

Select a subscription from the Subscriptions field or type one in. The Viewer does not subscribe to anything by default. You must choose a subscription. For example, enter "msmq.oms" in the Subscriptions field to get all Responder PubSub traffic.

All Responder traffic runs under the default subscription of MSMQ.OMS.[Configuration Name] and can be subscribed to more specifically. Subscribing to MSMQ.OMS.* will pull in all OMS traffic. If more then one Responder environment is on the network; you'll want to append the configuration value used in Data Services. For example MSMQ.OMS.CLIENTNAME.* if the configuration is CLIENTNAME.

Click the Subscribe button.
Messages should start populating the grid. If not, you can use the Send Test Message tool to ensure PubSub is properly connected.