IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > IBM Tivoli Monitoring Web Services for the SOAP server > IBM Tivoli Monitoring web services scenarios
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Create collaborative automation using SA IO
You can create a System Automation for Integrated Operations Management REXX application that calls JSCRIPT SOAP functions to forward any SA IO trapped message and display it on a Universal Message console. You can use SA IO scripts to trap and send any log messages, console messages, and so on, to IBM Tivoli Monitoring using SOAP methods.
You can create an application that provides these benefits:
- You can monitor devices, such as HP NonStop Kernel, by trapping VT100 messages and raising Universal Messages.
- You can send commands to SA IO monitored Telnet sessions and send replies back to those commands.
- Source messages can be either excluded or included, based on any criteria using powerful regular expressions.
- A local log can keep audit information about the status of messages received and messages sent.
- A local log can keep information about the source hub connection/retry status.
The graphics that follow show a sample Telnet session, a Universal Message console showing messages received, and a sample message log.
Figure 1. Universal Message Console Showing Messages Received
Figure 2. Message Log Details
Parent topic:
IBM Tivoli Monitoring web services scenarios