You can use the predefined reports included with ZENworks Database Management to view information about the application events recorded by Application Launcher, or you can use your own database tools to create your own custom reports. The following sections provide information:
ZENworks Desktop Management includes predefined reports for successful application events and failed application events.
To generate a predefined report:
Right-click the Desktop Management Database object, then click
.In the
list, expand the category, then select the report you want.Click
.Using your database tools of choice, you can create custom database reports to search for information not included in the predefined reports, or to generate different report formats. The following samples are SQL queries you can use to generate reports from your database tools if you are using the Sybase database included with ZENworks. Refer to Database Tables and Fields for additional information.
The following queries return all information fields for a successful, failed, or rogue process management event stored in the database. Events are sorted by the order in which they where entered into the database.
SELECT * FROM T_SUCCESS
SELECT * FROM T_FAILURE
SELECT * FROM T_INFO
To sort the list on a specific field, add ORDER BY field_name, as in the following examples:
SELECT * FROM T_SUCCESS ORDER BY zenWSTDN
SELECT * FROM T_FAILURE ORDER BY zenAppTDN
SELECT * FROM T_INFO ORDER BY zenUserTDN
The valid field names are listed in the table in Database Tables and Fields
To include only a specific event type (launch, distribute, etc.) for an event (success, failure, etc.), add WHERE zenEventType="event_type", as in the following examples:
SELECT * FROM T_SUCCESS WHERE zenEventType="Launch Success"
SELECT * FROM T_FAILURE WHERE zenEventType="Launch Failure"
SELECT * FROM T_INFO WHERE zenEventType="Process Terminated"
The valid event types are listed in the table in Database Tables and Fields
To include only specific fields, replace the * with a comma-delimited field list, as in the following example:
SELECT zenEventType,zenDateTime,zenUserTDN,zenAppTDN FROM T_SUCCESS WHERE zenEventType="Cache Success" ORDER BY zenUserTDN
The database includes the following three tables:
T_Success: Stores information about successful events.
T_Failure: Stores information about failed events.
T_Info: Stores information about rogue process management events. For information about rogue process management, see Section 41.0, Controlling Rogue Processes.
Each database table contains as many as 17 information fields. The following table lists the fields and the database tables that include the fields. The data type for all fields is varchar(256).
Table 44-2 Database Tables and Fields
Field |
Tables |
Description |
---|---|---|
zenEventType |
T_Success T_Failure T_Info |
The event that occurred.
|
zenDateTime |
T_Success T_Failure T_Info |
The date and time the event occurred. |
zenUserTDN |
T_Success T_Failure T_Info |
The distinguished name and tree of the user for which the event occurred. |
zenWSTDN |
T_Success T_Failure T_Info |
The distinguished name and tree of the workstation on which the event occurred. If the workstation has not been imported into eDirectory as a Workstation object, the field contains WORKSTATION NOT REGISTERED. |
zenWSAddr |
T_Success T_Failure T_Info |
The IPX™ or IP address of the workstation on which the event occurred. |
zenAppTDN |
T_Success T_Failure T_Info |
The distinguished name and tree of the Application object for which the event occurred. Because rogue processes do not have an Application object, this field is always “ZEN Process Management” in the T_Info table. |
zenAppGUID |
T_Success T_Failure T_Info |
The global unique identifier assigned to the Application object. The GUID is located on the Application object's Options page (Distribution Options tab). Because rogue processes do not have an Application object, this field is always empty in the T_Info table. |
zenAppVer |
T_Success T_Failure T_Info |
The version number assigned to the Application object. Possible numbers range from 0 to 65535. The version number is located on the Application object's Options page (Distribution Options tab). Because rogue processes do not have an Application object, this field is always empty in the T_Info table. |
zenMajor |
T_Success T_Failure T_Info |
For successful events (T_Success table), this field is always 0. For failed events (T_Failure table), this field lists the error code generated by Application Launcher. For rogue process events (T_Info table), this field is left blank. |
zenMinor |
T_Success T_Failure T_Info |
For successful events (T_Success table), this field is always 0. For failed events (T_Failure table), this field lists additional error code information. For rogue process events (T_Info table), this field is left blank. |
zenEventString1 |
T_Failure T_Info |
For failed events (T_Failure table), this field might list additional information describing the reason for the failure. For rogue process events (T_Info table), this field lists the executable path for the rogue process. |
zenEventString2 |
T_Failure T_Info |
For failed events (T_Failure table), this field might list additional information describing the reason for the failure. For rogue process events (T_Info table), this field lists the original filename of the process. |
zenEventString3 |
T_Failure T_Info |
For failed events (T_Failure table), this field might list additional information describing the reason for the failure. For rogue process events (T_Info table), this field contains the process ID (PID). |
zenEventString4 |
T_Failure T_Info |
For failed events (T_Failure table), this field might list additional information describing the reason for the failure. For rogue process events (T_Info table), this field contains the parent process ID (parent PID). |
zenEventString5 |
T_Failure T_Info |
For failed events (T_Failure table), this field might list additional information describing the reason for the failure. For rogue process events, this field contains the event action, either “process ignored” or “process terminated successfully.” |
zenAppFlags |
T_Success T_Failure T_Info |
For successful events (T_Success table) and failed events (T_Failure table), this field lists the Application object bitmask. For rogue process events (T_Info table), this field is always 0. |