BMC MainView Console Automation

The MainView Console Automation (MVCA) Server is the component that provides the message processing infrastructure. The Automation server can connect to many sessions, receive messages from each session, process rules for each message, and then send the messages to MVCA Viewers for operators to respond to the messages.

GUID-D919F2CF-AA15-4A9A-B5FF-8C9FB5CCABF1-low.jpg

  • Message-Processing-Overview An MVCA server connects to mainframe consoles through CCS, and to Hardware Management Consoles (HMC) using IBM's Hardware Console Management API.
  • Sessions Each MVCA server can start up any number of sessions. A session is simply a source of messages. It can be a CCS session that connects to a mainframe console through CCS, or an HMC session that interacts with an IBM Hardware Management Console.
  • General-Server-Settings The General Setting page allows you to set the Viewer Port and the startup behavior for the selected Automation Server Pops up a new Logs Window allowing you to manage - view, delete or download - the log files available for this server.
  • Consoles A Console Automation Server can connect to one or more CCS console sessions. The Consoles page displays the currently defined CCS console sessions with their status and allows an Automation servers connections to individual consoles to be started, stopped and modified.
  • SecureHMC-Connections The HMC Connections page lists the HMC proxy connections that have been enabled for operator use from this web page. If the HMC Proxy service is active then the connection name may be clicked on to go to the logon page for access to that HMC.
  • Configuring-SNMP You can use the Console Automation Server to configure your Simple Network Management Protocol (SNMP) connections. The SNMP Connections page displays the currently defined SNMP configurations and trap ports. You can create new queries, upload MIB files, and configure Trap Formatters by filling out the respective wizards.
  • Syslog-Configuration The Unix Syslog listener captures messages and routes them through the MVCA rules. The messages are sent to the MVCA viewer and sent to the appropriate terminal emulator. The Syslog viewers will connect back the original host which supplied the message using Secure Shell (SSH), Telnet, and Web browsers.
  • BAROC-Event-Listener Each MVCA server can be configured to listen to BAROC events from remote cells. The BAROC tab provides the controls to enable the BAROC event handler and select which cell definition should be used. To enable the BAROC event handler, select Yes to enable the connection and select the appropriate cell definition. BAROC events are passed through the MVCA rule engine just like other event sources. All slots in a BAROC event are available to rules.
  • Watchdog-Session Each Console Automation server has a built-in session called the 'watchdog' session. This watchdog receives messages pertaining to the operation of all other sessions.
  • Rule-Assignments The Rules tab allows for rules to be assigned to sessions, and for the rule evaluation order to be specified. Form rules are also defined here.
  • RDL2-Language RDL2 is the Rules Definition Language used by the Console Automation Server. It provides the ability to script responses to events received by the Automation server and to create script that can be launched by operator from the Console Automation viewer. RDL2 is a simple procedural language based on the popular REXX scripting language. It provides simple and composite data types, as well as structured control flow. A rich set of built in functions are provided to examine and manipulate the events, create sophisticated data structures, and high level actions such as sending e-mail or running custom programs.
  • Form-Rules Form rules allow you to define rules for common situations without having to write RDL2 code. To create a rule, click on the Add FORM button on the Rules tab in the MVCA server configuration.
  • Viewer-Commands Commands are pre-configured operator inputs that are attached to a message via an RDL2 rule. When an operator right-clicks on a message in the viewer, the list of commands is presented as an 'Actions' sub-menu on the context menu. Each message may have an arbitrary number of commands. attached to it.
  • Input-Filter Input Filters are similar to rules except that input filters are applied to operator input entered in the Automation Viewer. The first executable line must be 'filter input boolean expr ' statement followed by body statements. Input filters have access to a variable named 'userinput.' The properties contained in userinput are listed below.
  • Viewer-configuration Console Automation Viewers are Java applets that are launched from the Automation Viewers page accessible from the navigation menu on the left side of most web pages. Viewers are created by administrators using the Viewer Configuration page. Only administrators can create a viewer configuration.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*