Client Management Suite

In Parts 1-3 of this series we covered the standard platforms (Windows, Unix, Linux, Mac) data classes. In Part 4 we'll cover what Agentless Inventory provides. Whether you need to create a custom report, or a custom resource filter based on Agentless Inventory Data in Inventory Solution 7.0, knowing the database schema is important. Agentless Inventory contains very similar data classes to what was seen in version 6.x of Inventory Solution for Network Devices. However, there are changes thus this document provides technical details on the new data structure and is useful when working with the Agentless Inventory section of Inventory Solution.

Introduction

Documenting database schema is not an easy task. SQL can provide a table-column view of all selected tables, yet this does not include descriptions of what the values represent. This helps provide valuable feedback when trying to put together a specific type of report or when simply looking for a data point collected via SNMP.

It is important to note that Agentless Inventory is primarily driven by SNMP, and requires the use of Network Discovery as a starting point for using Agentless Inventory against the devices. This requirement will change as additional functionality is added to Inventory Solution 7.0.

NOTE: The information in this document may change, though at the time of publication this is believed to be the accurate information for the release of Inventory Solution 7.0.

Database Schema

The following list reveals data classes and their structure. First, the name of the table is given, followed by a designation as a Base or Sub Class data class. The following label system is used:

• STANDARD Class - This is a data class that contains no dependencies or sub classes
• BASE Class - This is a table that contains data that is then extended by a SUB Class. There is only one BASE class, so unless otherwise specified, all data classes are STANDARD classes.
• SUB Class - This contains data extended from another data class. There is only one SUB class so unless otherwise specified, all data classes are STANDARD classes.

Note the following when reviewing the grids:

1. Field Name represents how the column will be labeled when working within the Symantec Management Console, including reports, Resource Manager details, Pickers, etc.
2. Data type indicates in what data format the data is managed in.
3. Qualifiers provide a Description of the Column (if applicable) and potentially other data elements, such as if the column is key or not, or if there is ENUM data to be described.
4. MIB information contains the SNMP information used to gather the data.

For help in navigating dependent data classes, use the following guide:

• SNMP Host Devices
• SNMP Host Resources
• SNMP Win32 Services
• SNMP Win32 Shares
• SNMP Win32 Print Queues
• SNMP Software
• SNMP Storage
• SNMP Physical Entities
• Printer Related Data classes (Non-Netware)
  • SNMP HP Printer
  • SNMP Printer Cover
  • SNMP Printer Input Tray
  • SNMP Printer Output Tray
  • SNMP Printer Supply
• Netware Data classes
  • SNMP NW Adapters
  • SNMP NW Disk Storage
  • SNMP NW NLM
  • SNMP NW Partitions
  • SNMP NW Printers
  • SNMP NW Server
  • BASE class: SNMP NW Settings
    • SUB class: SNMP NW Settings Descriptions
  • SNMP NW Volume

Conclusion

Hopefully this provides a guide that will allow you to upgrade or implement Inventory Solution 7.0 armed with the necessary data to manage your reports, filters, or anything else based off of Agentless Inventory (formerly known as Inventory Solution for Network Devices). The intent is to broaden Agentless Inventory to support Protocols such as WMI, allowing a greater flexibility in gathering data from devices without a local agent. Note that there are no dates planned to add this functionality at the time of this publication
 

Inventory Solution 7.0 Database Schema, Part 3: Software and User Inventory