|
|
|
For Web MV to receive a session's messages, that session must either be defined as automated, or managed by an external REXX program that sends messages through the CA Automation Point rules engine using the CA Automation Point MSG command processor.
Only messages that originate from Web MV-approved sessions (sessions for which Web MV has been enabled) are forwarded to the Web MV Command Processor. Once inside the Web MV Command Processor, these messages are sent to the Web MV Web Server, which temporarily stores them in the Web MV database. The Web MV Web Server then forwards these messages to all Web clients who are currently registered to receive messages from the specified session.
The AP Msg Recall, CA-OPS/MVS Messages, and AP Notification Messages windows are internal sessions. The AP Msg Recall window is not configurable from the session definition set and will always appear on the CA Automation Point desktop. The CA-OPS/MVS Messages and AP Notification Messages windows are configurable under function windows. These three sessions are Web MV-enabled through the Configuration Manager Web Message Viewer dialog. All other sessions must be web-enabled through their session definitions in the session definition set in order to be viewed from the Web MV graphical user interface.
Note: For information on how to enable the AP Msg Recall, CA‑OPS/MVS Messages, and AP Notification Messages sessions using Configuration Manager, see the section Enabling Web MV in this chapter .
Important! Any time you pause a session from CA Automation Point, the word PAUSED displays on the top of the Web MV GUI screen at the end of the toolbar. While a session is paused, you will not be able to view its messages, because messages of paused sessions do not go through CA Automation Point Rules, and therefore are not forwarded to Web MV.
| Copyright © 2012 CA. All rights reserved. |
|