Integration
Table Of Contents
- View Integration
- Contents
- View Integration
- Introduction to View Integration
- Integrating View with the Event Database
- Customizing LDAP Data
- Integrating View with Microsoft SCOM
- Setting Up a SCOM Integration
- Assign a Name to the View Connection Server Group
- View Management Packs
- Import the View Management Packs on the SCOM Server
- Enable a Proxy Agent on a View Connection Server Host or Security Server
- Run the Discovery Script in the Operations Manager Console
- View Connection Server and Security Server Managed Objects
- View Object Classes and Relationships
- Monitoring View in the Operations Manager Console
- Setting Up a SCOM Integration
- Examining PCoIP Session Statistics with WMI
- Setting Desktop Policies with Start Session Scripts
Table 2‑1. Event Database Tables (Continued)
Table Name Description
event_data_historical Data values for all events.
event_historical Metadata and search optimization data for all events.
View records details about events to all the database tables. After a certain period of time has elapsed
since writing an event record, View deletes the record from the event and event_data tables. You can use
View Administrator to configure the time period for which the database keeps a record in the event and
event_data tables.
Important View does not restrict the growth of the event_historical and event_data_historical tables.
You must implement a space management policy for these tables.
A unique primary key, EventID, identifies each event that View records in the event and event_historical
tables. View records data values for each event in the event_data and event_data_historical tables. You
can obtain the complete set of information for an event by joining the event and event_data tables or the
event_ historical and event_data_historical tables on the EventID column.
The EventType, Severity, and Time columns in the event and event_historical tables identify the type and
severity of an event and the time at which it occurred.
For information about setting up the event database, see the View Installation document.
Note Events might be lost if you restart View Connection Server instances while the event database is
not running. For a solution that avoids this problem see http://kb.vmware.com/kb/1021461.
Event Database Schemas
The following table shows the schema for the event and event_historical database tables.
Table 2‑2. Schema for the event and event_historical Tables
Column Name Oracle Data Type SQL Server Data Type Description
Acknowledged SMALLINT tinyint Whether View acknowledged the event.
n
0 = false
n
1 = true
DesktopId NVARCHAR2(512) nvarchar(512) Desktop ID of the associated pool.
EventID INTEGER int Unique primary key for the event.
EventType NVARCHAR2(512) nvarchar(512) Event name that corresponds to an item in
the message catalog. For example,
BROKER_USERLOGGEDIN.
FolderPath NVARCHAR2(512) nvarchar(512) Full path of the folder that contains the
associated object.
GroupId NVARCHAR2(512) nvarchar(512) SID of the associated group in Active
Directory.
View Integration
VMware, Inc. 8