This section provides guidelines for executing local actions.
Before you begin
When you execute a local action for the first time, all required jar files are taken from the BMC TrueSight Infrastructure Management Server. Your permission for executing these files may be requested.
If any local action requires your input, a screen for you to enter your input is displayed. For example, if you select the Telnet to EVENT Origin local action, the Execute Local Action screen requires you to enter inputs for the attributes listed in the table below.
Execute Local Action screen attributes
Local actions are executed, but the results are not displayed in an output window.
If you select single or multiple events in an Event View, the event data is logged in the home directory\.econsole\webconsole\smss2k642\etc\event_op\celleventdata.xml file. This data helps you customize the local action script execution method.
Log output to file
To save the output and errors, to a file, browse and enter the directory/folder name. The output and error files are created and saved in the directory/folder you specified. You can see the content of these two files when you click the Output and Errors tabs on the Feedback window.
If you select Log output to file option, the Feedback window is not displayed
By default, if no inputs are given, local actions are executed and the output is displayed on the output screen.
The system in which the local action is executed must have Java version 1.8.031 or later installed.
Commands used to execute local actions must be entered in the PATH environment variable.
To execute local actions
From the event list, select an event.
Click the blue wrench icon in the Tools Menu column.
Click Local Actions and select the out-of-the-box local actions from the list displayed.