Tool behavior
After a tool is defined, the tool is available to users with sufficient privileges, filtered by any tool access criteria where applicable. Subsequent tool behavior depends on the type of tool, the event selection fed to the tool and the tool configuration.
Tool context
You can select to run tools against single or multiple events that come from single or multiple
data sources, this selection determines the context in which you run the tool.
- Tool type
- For example, Script tool, Command tool, SQL tool, CGI/URL tool.
- Selection
- Your selection consists of events and those events may come from one data source, or multiple data sources. Your Event Viewer configuration determines the data sources for your events.
Tool functions
During the tool creation and configuration phase, the Administrator selects the tool functions.
- Tool options
- The tool options are defined and either enabled or disabled by the Administrator when they
define the tool. The following tool options are available options.
- The
Execute for each selected rowtool option, is available for all tools. - The
Window for each selected rowtool option, is available for CGI/URL tools.
- The
- Tool syntax
- The tool syntax is likely to contain references to the events fields, in the following forms.
- A list reference, for example
{$selected_rows.Serial}. - A field reference, for example
{@Serial}.
- A list reference, for example
Both the context in which the tool is run (the selection) and the tool configuration
(options and syntax) determine the tools behavior. For examples about tools behavior, go to the
following IBM DeveloperWorks link. Within this link, open the spreadsheet and each spreadsheet tab
represents the behavior for one tool. https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Netcool%20OMNIbus/page/Web%20GUI%20tool%20behaviors/edit.