To use the monitoring CGI, you must first configure the PMDF Service Dispatcher and PMDF HTTP server. That is done by running the Dispatcher configuration utility as described in the PMDF Installation Guide. If you have not configured the Dispatcher, then do so now.
To connect to the monitoring CGI with your web browser, open the URL
host, use the actual IP host name of the system running the PMDF HTTP server. If you chose to run the PMDF HTTP server on a port other than port 7633, then specify that port number in place of
7633in the above URL.
After you select the style of monitoring to perform, your browser window will split into multiple frames.
When monitoring OpenVMS PMDF platforms, five frames will appear,
+---------+---------+ | Frame 1 | Frame 2 | +---------+---------+ | Frame 3 | Frame 4 | +---------+---------+ | Frame 5 | +---------+---------+
+-------------+ | Frame 3 | +-------------+ | Frame 4 | +-------------+ | Frame 5 | +-------------+
|Frame 1:||All OpenVMS processing queues used by PMDF throughout the cluster.|
|Frame 2:||When you click on a link in Frame 1, the results appear in Frame 2.|
|Frame 3:||Channel counters for all your PMDF channels; cluster-wide on OpenVMS.|
|Frame 4:||When you click on a link in Frame 3, the results appear in Frame 4.|
|Frame 1:||Red background if a queue is closed, disconnected, stalled, stopped, stopping, or has a stop pending, or if the periodic delivery job or message bouncer job is missing from the queues.|
|Frame 2:||Red background if a queue is closed, disconnected, stalled, stopped, stopping, or has a stop pending.|
|Frame 3:||Red background if the count of stored messages in a channel exceeds the threshold specified in the monitoring option file. See Section 33.7.2 for details.|
|Frame 4:||Red background if the count of stored messages in a channel exceeds the threshold specified in the monitoring option file. See Section 33.7.2 for details.|
Red background if
Figure 33-17 shows a sample of the web monitor display on OpenVMS.
Figure 33-17 Sample Web Monitor Display on OpenVMS
5 Owing to some Netscape Navigator 3.0 bugs, you may find that the frames are not actually updated. It's possible to get Navigator into a mode whereby it incorrectly updates frames from a client cache rather then from the remote server. For instance, resizing the frames can lead to this state. To correct this situation, clear Navigator's in-memory and on-disk caches with the Options, Network Preferences..., Cache menu. After clearing the caches, reload each frame one by one: select a frame and then select the View, Reload Frame menu item; repeat for the other frames. Do not reload the entire window as that will undo any adjustments made to the relative frame sizes.