hello from a "green" user of OpManager

The question is actually very simple, I guess. How to run batch-file on the NMS server(Opmanager v11)? Batch-file is located locally on the NMS server.  Batch-file functionality was already tested with some freeware NMS systems and on WhatsUP Gold and it works fine. In all NMS applications, it's quite intuitive(Alarm->Action), but in OM..... I need only to trigger this batch-file, when Alarm happens and trigger another batch, if the device recovers(unavailable ping, as the example). After reading the OpManager manual, I assume, it has to be done in Workflow. But how… I’m a bit confused.

 The topology is the following:

NMS server has got two connections

-          - “First connection” goes to an ordinary TCP\IP network with Windows-based devices, Cisco switches, which are monitored via SNMP, WMI, ICMP, SSH.

-         - “Second connection” goes to the APCS network, based on the company proprietary protocol.

OpManager gets alarm from “First Connection” and after the execution of the  batch-file, the alarm goes to “Second Connection” with the help of the script in the batch-file. There will two batch-files per device – “UP.bat”, initiated when the device recovers, “DOWN.bat”, when the device is offline (not pingable, for example). So, as the example, a Domain Controller will have two dedicated batch-files – DC_up.bat and DC_down.bat. They have to be initiated in OpManager, when the applicable alarm(pingable(up)\non-pingable(down)) comes to NMS server.

thank you in advance