1.3 Installing the Module

Run the module installer on the proxy agent computers you want to monitor to install the agent components, and run the module installer on all console computers to install the Help and console extensions.

NOTE:Installing the module automatically installs NetIQ SNMP Trap Receiver (Trap Receiver). For more information, see Working with NetIQ SNMP Trap Receiver.

Access the AM70-AvayaCM-8.x.x.0.msi module installer from the AM70_AvayaCM_8.x.x.0. self-extracting installation package on the AppManager Module Upgrades & Trials page.

You can install the Knowledge Scripts into local or remote AppManager repositories (QDBs). Install these components only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to 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 on a remote computer where an agent is installed. For more information, see Deploying the Module with Control Center. However, if you do 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:

  1. On all proxy agent computers, stop the NetIQ AppManager Client Resource Monitor (NetIQmc) service to ensure that any existing version of qNQAvayaCM.dll is updated correctly during installation of the module.

  2. Double-click the module installer .msi file.

  3. Accept the license agreement.

  4. 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 will install the agent components.

  5. To install the Knowledge Scripts into the QDB:

    1. Select Install Knowledge Scripts to install the repository components, including the Knowledge Scripts, object types, and SQL stored procedures.

    2. Specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.

  6. (Conditional) If you use Control Center 7.x, run the module installer for each QDB attached to Control Center.

  7. (Conditional) If you use Control Center 8.x or later, run the module installer only for the primary QDB, and Control Center automatically replicates this module to secondary QDBs.

  8. Run the module installer on all console computers to install the Help and console extensions.

  9. Run the module installer on all proxy agent computers to install the agent components.

  10. Configure all necessary SNMP community strings in AppManager Security Manager to enable access of remote Communication Managers and to enable the functionality of Trap Receiver. For more information, see Configuring SNMP Community Strings.

  11. Enable Communication Manager to send RTCP packets. For more information, see Configuring Communication Manager To Send RTCP Packets and CDRs.

  12. Update configuration settings for your SIP phones to identify the proxy agent computer. For more information, see Updating the 46xxsettings.txt File.

  13. (Conditional) If you have not discovered Avaya Communication Manager resources, run the Discovery_AvayaCM Knowledge Script on all proxy agent computers where you installed the module. For more information, see Discovering Avaya Communication Manager Resources.

  14. To get the updates provided in this release, upgrade any running Knowledge Script jobs. For more information, see Upgrading Knowledge Script Jobs.

  15. Run the SetupSupplementalDB Knowledge Script to:

    1. Apply improved SQL indices to the CDR and Traceroute tables in the Avaya CM supplemental database.

    2. Update the CDR table in the Avaya CM supplemental database to allow the database to store Facilities Restriction Level (FRL) codes.

After the installation has completed, you can find a record of problems encountered in the AvayaCM_Install.log file, located in the \NetIQ\Temp\NetIQ_Debug\<ServerName> folder.

IMPORTANT:Configure the gateways to send traps directly to the trap receiver instead of forwarding them through the Communications Manager. For additional information about how to configure the gateways, see https://downloads.avaya.com/css/P8/documents/100059440.