Reporting

Use this property page to have Novell® Application LauncherTM/Explorer report event information for the application. You can define the events you want Application Launcher/Explorer to report and also define the destination where you want the event reports sent.

Reports contain the following information: event type, date and time, user distinguished name, workstation distinguished name, workstation address, application distinguished name, application global unique identifier (GUID), application version string, and event strings.

Events
Select the events you want reported and the destinations where you want them reported. If necessary, you can send an event report to multiple destinations. All events and destinations are described below.

EVENT DESCRIPTION
Launch Success Occurs when a user double-clicks the Application object and Application Launcher/Explorer successfully starts the application.
Launch Failure Occurs when a user double-clicks the Application object and Application Launcher/Explorer cannot start the application.
Distribution Success Occurs when Application Launcher/Explorer successfully modifies the workstation to support the application. Modifications include installation of files, changing of settings (registry, .INI, etc.), creation of shortcuts, and so forth.
Distribution Failure Occurs when Application Launcher/Explorer cannot modify the workstation to support the application. Modifications include installation of files, changing of settings (registry, .INI, etc.), creation of shortcuts, and so forth.
Uninstall Success Occurs when Application Launcher/Explorer successfully uninstalls the application from the workstation.
Uninstall Failure Occurs when Application Launcher/Explorer cannot uninstall the application from the workstation.
Cache Success Occurs when Application Launcher/Explorer successfully caches the application to the workstation.
Cache Failure Occurs when Application Launcher/Explorer cannot cache the application to the workstation.
Filter (Icon Hidden) Occurs when Application Launcher/Explorer cannot display an Application object on a workstation because the workstation does not meet one or more of the Application object's system requirements (Application object > Availability tab > System Requirements page) and the system requirement's Show Application Icon Even If Criteria Are Not Met option is set to False. The Application object's icon is hidden, or not shown, on the workstation.
Filter (Icon Shown) Occurs when Application Launcher/Explorer can only display a disabled (dimmed) Application object on a workstation. This occurs because the workstation does not meet one or more of the system requirements (Application object > Availability tab > System Requirements page) and the system requirement's Show Application Icon Even If Criteria Are Not Met option is set to True. Users can right-click the disabled icon and click Details to see what system requirements are not being met.
DESTINATION DESCRIPTION
Database Application Launcher/Explorer can write events to any ODBC-compliant database (for example, the Sybase* database included with ZfD). To use a database, you must also:
  • Create a ZENworks® Database object to use for Application Management reporting. This cannot be the same database object used for Inventory reporting.
  • If necessary, create a Service Location Package. Associate the Service Location Package with the containers where the users or workstations reside whose reports you want sent to the database.
  • Enable the ZENworks Database Policy in the Service Location Package.
  • Associate the ZENworks Database Policy with the ZENworks Database object.
  • Make sure users have the appropriate ODBC database driver installed and configured.
  • After you've set up database reporting, you can use one of the predefined reports to see information about specific application events. To access the reports, right-click the ZENworks Database object you created for Application Management reporting > click Reporting.
SNMP Traps Application Launcher/Explorer can send SNMP traps to any SNMP management console. To use SNMP traps, you must also:
  • Enable an SNMP Trap Target Policy in a Service Location Package. It may be necessary to first create the Service Location Package.
  • Associate the Service Location Package with the containers where the users or workstations reside that you want the SNMP Trap Target Policy applied to.
  • Add the SNMP Trap Targets (IP addresses) for the locations you want the traps sent.
  • Have a management console that displays the SNMP traps.
Text Log File

Application Launcher/Explorer can write events to a text log file. You use the Log File Location field (described below) to specify the location of the log file.

Log File Location
If you selected a log file as the destination for any of the event reports, enter (or browse to and select) the location and name for the log file. You can specify a local drive or a network drive. If you enter a location that does not exist, Application Launcher/Explorer will create it. Do not use extended characters in the path; extended characters are not supported.

If you want Application Launcher/Explorer to log events to a file in a common network location, you need to establish the network directory and provide users with Read and Write rights to files in the directory. Because log file names are established on a per-application basis, you can have individual log files for each application (by specifying a different log file name for each Application object) or one log file for all applications (by specifying the same log file name for all Application objects).


ZENworks for Desktops Online Documentation

A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk denotes a third-party trademark. For information on trademarks, see Legal Notices.