Contents of the Live node


The contents of the Live node vary by operating system.

Virtual environments contain specialized Live node children, which are described in Browsing-virtual-inventory.

OS

Server Objects

IBM AIX

  • BLPackages
  • Components
  • Configuration
  • Daemons
  • Extended Objects
  • File System
  • Hardware Information
  • Packages
  • Patches
  • Processes
  • System Info
  • UNIX Groups
  • UNIX Users

HP-UX

  • BLPackages
  • Bundles
  • Components
  • Configuration
  • Daemons
  • Extended Objects
  • File System
  • Hardware Information
  • Patches
  • Processes
  • Products
  • System Info
  • UNIX Groups
  • UNIX Users

Linux

  • BLPackages
  • Components
  • Configuration
  • Daemons
  • Extended Objects
  • File System
  • Hardware Information
  • Processes
  • RPMs
  • System Info
  • UNIX Groups
  • UNIX Users

Oracle Solaris

  • BLPackages
  • Components
  • Configuration
  • Daemons
  • Extended Objects
  • File System
  • Hardware Information
  • Packages
  • Patches
  • Processes
  • System Info
  • UNIX Groups
  • UNIX Users

Microsoft Windows

  • .NET Global Assemblies
  • Active Directory
  • Applications
  • BLPackages
  • Complus
  • Components
  • Configuration
  • Event Logs
  • Extended Objects
  • File System
  • Hardware Information
  • Hotfixes
  • Local Groups (shows no data if server is domain controller)
  • Local Users (shows no data if server is domain controller)
  • Metabase (if Microsoft IIS is installed)
  • Registry
  • Security Settings (some limitations apply — see Creating-a-Deploy-Job)
  • Services
  • System Info

The following list provides additional information about nodes that are children of the Live node:

  • Active Directory — Provides a hierarchical listing of the groups, shared folders, and users associated with Active Directory domains and sub-domains on a Windows server.
  • BLPackages — Shows all BLPackages that have been deployed to a server. For more information about using this object, see Tracking-BLPackage-deployments.
  • Components — Shows components associated with a server. Components are objects representing a higher level of abstraction than server objects. Using a component, you can manage an application rather than the server objects that make up the application. For more information, see Components and component templates.
  • Configuration — Lists files that present the contents of configuration files for the operating systems BMC Server Automation supports. To deliver this information in a standard format, BMC Server Automation parses the contents of those files using grammar files. (In this respect, configuration file objects are similar to extended objects.) If necessary, you can identify additional configuration files. For more information, see Identifying-additional-configuration-files and Configuration-files.
  • Extended Objects — Shows custom objects that consist of information after it is parsed by a BMC Server Automation grammar file (see Grammar-files-supported-by-BMC-Server-Automation) so it can be presented in a standard format. Extended objects can deliver information not included in a standard BMC Server Automation installation, such as local user account data or network settings. For more information, see Creating-an-extended-object.
  • File System — Provides a hierarchical listing of the server's files and directories. When browsing a file system, you can traverse symbolic links to files and directories.
  • Hardware Information — Provides information about a server's hardware configuration.

    Note

    Different operating systems, especially in virtual environments, expose different levels of details relating to hardware information. The level of detail provided by the hardware information object typically varies for different platforms.

  • Hotfixes — Provides a list of Windows Security Patches installed on the target server based on patch metadata from Shavlik. The first time that you click this branch, BMC Server Automation retrieves the Shavlik metadata and populates the list. If the Shavlik file needs to be downloaded through a proxy, ensure that the proxy settings in Patch Global Configuration (which are used for this download) are up-to-date.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*