Run the module installer on the proxy computers you want to monitor (agents) to install the agent components, and run the module installer on all console computers to install the Help and console extensions.
Access the AM70-CiscoCM-7.x.x.0.msi module installer from the AM70_CiscoCM_7.x.x.0.exe 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 .
You can install the Knowledge Scripts and the Analysis Center reports 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:
Selectto 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.
Run the module installer for each QDB attached to Control Center.
Run the module installer on all console computers to install the Help and console extensions.
Run the module installer on all proxy agent computers to install the agent components.
Configure AXL passwords in AppManager Security Manager. For more information, see Section 2.6, Configuring AXL Passwords in Security Manager.
To use the SNMPTrap_Async Knowledge Script, configure SNMP permissions in AppManager Security Manager. For more information, see Section 4.50.6, Configuring SNMP Permissions in Security Manager.
Enable the collection of Call Management Records and Call Detail Records. For more information, see Section 2.7, Collecting Call Management and Call Detail Records.
(Conditional) If you have not discovered Cisco Unified Communications Manager resources, run the Discovery_CiscoCM Knowledge Script on all proxy agent computers where you installed the module. For more information, see Section 2.8, Discovering Unified Communications Manager Resources.
HINT:To ensure the discovery of NetIQ SNMP Trap Receiver, stop and delete existing Discovery jobs before creating new jobs. For more information, see Section 4.50.5, Working with NetIQ SNMP Trap Receiver.
Configure the proxy agent computer as an FTP server. For more information, see Section 2.9, Configuring the Proxy Agent Computer as an FTP Server.
Configure the proxy agent computer as a billing server. For more information, see Section 2.10, Configuring the Proxy Agent Computer as a Billing Server.
(Conditional) If you have not created the CiscoCM supplemental database, run the SetupSupplementalDB Knowledge Script.
To get the updates provided in this release, upgrade any running Knowledge Script jobs. For more information, see Section 2.15, Upgrading Knowledge Script Jobs.
After the installation has completed, the CiscoCM_Install.log file, located in the \NetIQ\Temp\NetIQ_Debug\<ServerName> folder, lists any problems that occurred.