Use the Discovery_AMHealth Knowledge Script to discover AppManager and Control Center resources installed on Windows servers. This Knowledge Script returns information about successful and failed discoveries, and it raises events to notify you of errors.
Run the Discovery_AMHealth script on computers with the one or more of the following AppManager components: AppManager repository (QDB), management server, Cache Manager, Command Queue Service (CQS), deployment service, AppManager managed client, Control Center repository (NQCCDB), and Task Scheduler service.
In a clustered environment, the Discovery_AMHealth script discovers only QDB and CCDB roles. For more information about the setup of the AMHealth Module’s AMHealth_QDBComponentsHealth Knowledge Script in a clustered environment, contact NetIQ Technical Support.
By default, this script is only run once for each computer.
Set the following parameters as needed:
|
Parameter |
How to Set It |
|---|---|
|
Event Notification |
|
|
Raise an event if discovery succeeds? |
Select Yes to raise an event when discovery succeeds. The default is unselected. |
|
Event severity when discovery succeeds |
Set the event severity level, from 1 to 40, to reflect the importance of an event in which when the discovery succeeds. The default is 25. |
|
Raise event if discovery fails? |
Select Yes to raise an event when discovery fails. The default is Yes. |
|
Event severity when discovery fails |
Set the event severity level, from 1 to 40, to reflect the importance of an event in which the discovery fails. The default is 5. |
|
Event severity when job fails |
Set the severity level, from 1 to 40, to indicate the importance of an event in which the Discovery_AMHealth job itself fails. The default is 35. |
|
SQL Server login |
Specify the SQL user name required for access to the AppManager repository (QDB). Leave this field blank to use Windows authentication. NOTE:If you want to use a specific SQL Server login account, use Security Manager to update the AppManager repository with the SQL Server logins that you want to use. For more information, see Section 2.4, Configuring Security Manager for AM Health. |