Troubleshooting guide

2 — 5620 SAM user security tasks
2-6 Alcatel-Lucent 5620 Service Aware Manager
5620 SAM
System Administrator Guide
The User Activity form displays a filterable list of the logged user activities, and a
filterable list of the logged client and server session activities. Client session
activities include connection, disconnection, and access violation. Server session
activities include startup and shutdown. The properties form of a client connection
log record lists the activities performed by the user during the client session.
The 5620 SAM GUI allows direct navigation between the following objects:
• activity record and the associated session record
• activity record and the activity target object
• object properties form and the associated user activity list form
• 5620 SAM Task Manager task and the associated user activity list form
• session record and the associated user activity list form
The User Activity form lists the recent user session and activity entries; older entries
are purged according to configurable storage criteria. See Procedure 5-25 for
information about configuring the user activity log retention criteria using the
System Preferences form.
To archive user activity log entries before they are purged from the 5620 SAM
database, an OSS client can use a time-based filter to retrieve entries from the sysact
package using the find and findToFile methods. See the 5620 SAM-O XML
Reference for information about using the find and findToFile methods.
User activity logging is a valuable troubleshooting function. For example, if a port
unexpectedly fails, you can quickly determine whether misconfiguration is the cause
by doing one of the following:
• opening the port properties form and clicking User Activity to view the recent
user activity associated with the port
• opening the User Activity form, filtering the list by object type or name, and then
verifying the associated user activities
See “Troubleshooting using the 5620 SAM user activity log” in the 5620 SAM
Troubleshooting Guide for more information.
The following conditions and restrictions apply to user activity logging.
• A Deployment activity typically does not have an associated Save activity for the
following reasons:
• A Deployment activity takes place only after a successful Save activity, so a
Deployment implies a Save.
• A Save activity typically contains the same information as the associated
Deployment activity.
Note — Script execution is logged, but the actions that a script
performs are not.
Release 12.0 R6 | November 2014 | 3HE 08861 AAAF TQZZA Edition 01