Discovery enables you to inspect servers for the presence of software or software components. The success of Discovery, however, depends on certain key elements being specified properly within the Blueprint.
Test Discovery lets you verify that you have set up many of the Component Blueprint elements correctly while you are developing a new or editing an existing Component Blueprint. You can use Test Discovery to verify such things as indicators, registry elements, and managed and configuration files.
Note: Test Discovery cannot test for software components if the specified servers are not available or none of the components are found.
To test Blueprint Discovery success on a server
The Blueprints tab page appears.
The Blueprint Details page for the selected Blueprint appears.
The Test Discovery page appears in a new browser window.
By default, the drop-down list initially displays the first managed server in the list.
Test Discovery searches for either files or directories down to the level in the file system that matches the path text string you specify in the Search Root and displays the results in a tree view.
The File Search Directory field displays the directory and file elements as you select them in the in the tree view. When you are satisfied with the contents of the File Search Directory field, click Discover.
The discovery runs and one of the following appears:
No components found with Test Discovery
Apache HTTP Server (UNIX) v1.0.0 (Test)
IP address of host host_name conflicts with another host in the DB - Run Reconcile Servers to correct it
|
Copyright © 2013 CA.
All rights reserved.
|
|