To install the AppManager agent components, run the module installer on the AppManager agents that will monitor traps sent by remote devices. To install the Help and console extensions, run the module installer on all console computers.
Access the AM70-SNMPTraps-8.x.x.0.msi module installer from the AM_SNMPTraps_8.x self-extracting installation package on the AppManager Module Upgrades & Trials page.
For Windows environments where User Account Control (UAC) is enabled, install the module using an account with administrative privileges. Use one of the following methods:
Log in to the server using the account named Administrator. Then, run the module installer .msi file from a command prompt or by double-clicking it.
Log in to the server as a user with administrative privileges and run the module installer .msi file as an administrator from a command prompt. To open a command-prompt window at the administrative level, right-click a command-prompt icon or a Windows menu item and select Run as administrator.
You can install the Knowledge Scripts into local or remote AppManager repositories (QDBs). The module installer installs Knowledge Scripts for each module directly into the QDB instead of installing the scripts in the \AppManager\qdb\kp folder as in previous releases of AppManager.
You can install the module manually, or you can use Control Center to deploy the module to a remote computer where an agent is installed. For more information, see Section 2.4, Deploying the Module with Control Center. However, if you use Control Center to deploy the module, Control Center only installs the agent components of the module. The module installer installs the QDB and console components as well as the agent components on the agent computer.
To install the module manually:
Double-click the module installer .msi file.
Accept the license agreement.
Review the results of the pre-installation check. You can expect one of the following three scenarios:
No AppManager agent is present: In this scenario, the pre-installation check fails, and the installer does not install agent components.
An AppManager agent is present, but some other prerequisite fails: In this scenario, the default is to not install agent components because of one or more missing prerequisites. However, you can override the default by selecting Install agent component locally. A missing application server for this particular module often causes this scenario. For example, installing the AppManager for Microsoft SharePoint module requires the presence of a Microsoft SharePoint server on the selected computer.
All prerequisites are met: In this scenario, the installer installs the agent components.
To install the Knowledge Scripts into the QDB:
Select Install Knowledge Scripts to install the repository components, including the Knowledge Scripts, object types, and SQL stored procedures.
Specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.
(Conditional) If you use Control Center 7.x, run the module installer for each QDB attached to Control Center.
(Conditional) If you use Control Center 8.x or later, run the module installer only for the primary QDB. Control Center automatically replicates this module to secondary QDBs.
Run the module installer on all console computers to install the Help and console extensions.
(Conditional) If you are monitoring SNMP trap source devices that require the use of SNMP version 3, run the Discovery_SNMPTraps Knowledge Script on all agent computers from which you plan to monitor those source devices. For more information, see Section 2.6, Discovering SNMP Traps Resources.
After the installation has completed, the SNMPTraps_Install.log file, located in the \NetIQ\Temp\NetIQ_Debug\ServerName folder, lists any problems that occurred.