User's Manual

Working with Running Sessions
Session Management 12-41
Deleting Resources
Inactive resources can be deleted from the session editor. The only way to bring the resource instance back
into the session editor is to drag it from the Resource Instances view or the Search results view; see the
“Adding Resource Instances” section on page 12-39.
To delete resources, perform the following steps:
1. Open a session editor.
2. Select an inactive resource in the editor.
3. Right-click and select Delete.
4. Save the Template for the changes to take effect.
Using Annotations
For detailed information about using annotations, see the “Using Annotations” section on page 11-46.
Associating Scripts to Sessions
You can associate scripts (and test cases associated with the Template being scheduled) with sessions at the
time of scheduling or post-scheduling. If there is an association, the script will be executed when the session
enters a Running state, and the Active System Manager server can monitor and report the test case
execution result.
Figure 12-4 on page 12-8 and Table 12-2 on page 12-8 define Active System Manager session states.
There are three types of scripts that you can execute:
• Shell scripts (CLI-based); remote hosts should be provisioned with remote shell access or SSH access.
• HTTP-based scripts; an administrator should provision, at least, one HTTP server using the Active
System Manager web interface (Tools > Script Servers > New).
Note One or more scripts can be applied to a session.
To associate a script to a session, perform the following steps:
1. Perform one of the following tasks to open the Script Association window/page:
• At the time of scheduling, using the scheduling wizard (see the “Scheduling Templates” section on
page 11-18. At step 9 in that procedure, stop, and continue with this procedure).
• In the Session view, edit a session and select the script property and the Association tab.
The Rescheduling Session—Associate Scripts/Test Cases dialog box displays; see Figure 12-38.