2.3 Installing the Module

Run the module installer only once on any computer. The module installer automatically identifies and updates all relevant AppManager components on a computer.

Access the AM70-CallDataAnalysis-7.x.x.0.msi module installer from the AM70_CallDataAnalysis_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 AM70-CallDataAnalysis_7.x.x.0.msi from a command prompt or by double-clicking it.

  • Log in to the server as a user with administrative privileges and run CallDataAnalysis.x.x.0.msi 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). 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.

2.3.1 Manually Installing the Module

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 Section 2.4, 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. Double-click the module installer.msi file.

  2. Accept the license agreement.

  3. 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.

  4. 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.

  5. If you use Control Center 7.x, run the module installer for each QDB attached to Control Center.

  6. If you use Control Center 8.x or later, run the module installer only for the primary QDB, and Control Center will automatically replicate this module to secondary QDBs.

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

  8. If the Data Mart is not located on the Data Warehouse computer, run CDA_StandaloneDatamartSetup.exe on the H.323 RADIUS Data Mart computer. You can find this file in \Program Files\NetIQ\AppManager\bin\CDAFiles. Do not take this step if the Data Mart and Data Warehouse are on the same computer or if you will not use an H.323 RADIUS Data Source.

  9. If you have not discovered Call Data Analysis resources, run the Discovery_CallDataAnalysis Knowledge Script on the Data Warehouse computer. For more information, see Section 2.7, Discovering Call Data Analysis Resources.

    NOTE:If you are upgrading from version 7.4, you will need to perform additional steps to ensure that the Data Warehouse is properly configured for this version of the module, 7.5. For more information, see Section 2.3.2, Upgrading from Version 7.4 of the Module.

  10. Run the Discovery_ReportAgent Knowledge Script to display all of the Report Knowledge Scripts on the CallData tab.

  11. If you are using Cisco Unified Communications Manager 4.x as a Data Source, ensure AppManager can connect to it. For more information, see Section 2.11, Connecting to a Unified Communications Manager 4.x Data Source.

  12. If you are using Cisco H.323 gateways as Data Sources, configure Microsoft Internet Authorization Service (IAS) on each Data Mart computer. For more information, see Section 2.8.1, Internet Authentication Service (IAS).

  13. For all Data Sources, ensure proper permissions have been set to allow AppManager to access the data you want to collect. For more information, see Section 2.8, Configuring Required Services.

  14. Run AddDataSource_CiscoCallMgr, AddDataSource_H323RADIUS, or AddDataSource_CiscoCM to enable data collection.

  15. To get the updates provided in this release, upgrade any running Knowledge Script jobs. For more information, see Section 2.6, Configuring Security Manager Settings.

After the installation has completed, the CallDataAnalysis_Install.log file, located in the \NetIQ\Temp\NetIQ_Debug\<ServerName> folder, lists any problems that occurred.

2.3.2 Upgrading from Version 7.4 of the Module

If you are upgrading from the previous release, version 7.4, you will need to perform additional steps to ensure that the Data Warehouse is properly configured for this version of the module, 7.5.

To upgrade from version 7.4 to version 7.5:

  1. Start the upgrade by double-clicking the AM70-CallDataAnalysis-7.x.x.0.msi module installer file. For more information, see Section 2.3, Installing the Module.

  2. Propagate Knowledge Script changes. For more information, see Section 2.9.2, Propagating Knowledge Script Changes.

  3. Run the Discovery_CallDataAnalysis Knowledge Script again on all Call Data Analysis agents, leaving the Database name parameter set to the default of NQCDA_Warehouse. For more information, see Section 2.7, Discovering Call Data Analysis Resources.

  4. You are now ready to run the AppManager for Call Data Analysis Knowledge Scripts and reports for this release.