Managing discoveries

You can use the Discovery Management Console to manage the discovery process.

Capturing discovery results on the discovery server
In a streaming server deployment, discovery data flows from the discovery server to the primary storage server. This data is processed and stored in the database on the primary storage server. You can alternatively capture and store this information in the file system on the discovery server. This information can be analyzed and transferred to the storage server for processing and storage at a later time.
Loading a discovery scope from a file
You can use the loadscope command to manage and load the discovery scope from a file.
Exporting scopes for use on another TADDM server
Use the api.sh command to export scopes.
Creating and managing custom server templates
You can create custom servers to discover and categorize servers that are not, by default, supported by TADDM. This is an advanced technique for configuring TADDM to discover servers that it does not know about by default.
Creating and managing computer system templates
You can customize how computers systems and other devices are discovered by creating computer system templates. A computer system template can specify additional information you want to gather from a type of discovered system, and can specify the model class to use for a category of discovered device.
Extending custom server and computer system templates
Your infrastructure might contain software applications and server types, such as custom Java™ servers, that are not automatically categorized by TADDM. Using the Discovery Management Console, you can create custom server templates to discover and categorize these servers.
Anchors and gateways
You can use anchors and gateways to extend discoveries to restricted network zones and to offload some of the discovery process from the TADDM server to improve the overall discovery performance.
Discovery schedules
You can schedule discoveries to ensure that information presented in the Discovery Management Console is always current and accurate.
Viewing the discovery history
Each time that a discovery is run, the Discovery Management Console updates the discovery activity and error information that is displayed in the History pane.
Using discovery profiles
Discovery profiles help you discover your IT environment.
The bulk load program
The bulk load program, which is the loadidml.sh file on UNIX systems and the loadidml.bat file on Windows systems, loads Discovery Library books into the TADDM database.
Using Bidirectional (BiDi) support for sensors and the bulk load program
Bidirectional language support is provided for Arabic and Hebrew languages.
Delta books utility program
Instead of loading the full DLA book when data changes occur, TADDM provides the possibility to generate and load the delta book only. With the delta books utility program, you can generate the IdML delta book sets that contain delta or changes between two sets of books. In typical situations, the program greatly increases the speed of the book loading process.
Application descriptors
You can use application descriptors to associate components to business applications and specify further details about the applications.
Suppressing sensor warnings
You can filter selected warning messages, when the same set of warnings is reported each time the discovery is run.

Parent topic: Discovery Management Console