Configuration objects overview
TrueSight Server Automation allows you to present information and perform operations on various server objects, extended objects, and configuration files. Collectively, BMC refers to these objects as configuration objects.
An extended object is similar to a custom configuration object, but it provides less functionality. In particular, an extended object cannot be deployed like a custom configuration object.
A configuration file is a file that appears under the Configuration object of a server in the Servers folder. You can add your own configuration files to the system.
This topic includes the following sections:
- Managing configuration objects at the Application Server
- Job for managing custom configuration objects
- Standard custom configuration objects
Managing configuration objects at the Application Server
All configuration objects are managed at the Application Server level using the Configuration Object Dictionary. The following sections describe procedures for adding configuration objects to the Configuration Object Dictionary:
- Adding-a-custom-configuration-object
- Identifying-additional-configuration-files
- Creating-an-extended-object
Job for managing custom configuration objects
The following topics describe jobs TrueSight Server Automation provides for distributing custom configuration objects to servers as well as updating and deregistering those objects:
- Creating-or-modifying-Distribute-Configuration-Objects-Jobs
- Creating-or-modifying-Upgrade-Model-Objects-Jobs
- Creating-or-modifying-Deregister-Configuration-Object-Jobs
Standard custom configuration objects
A standard installation of an agent on a server includes several types of custom configuration objects. A standard installation of an Application Server includes additional custom configuration objects, which you can optionally deploy to agents. For more information about the standard custom configuration objects, see Custom-configuration-objects.