NetIQ AppManager for Self Monitoring (AM Health) Readme

The AppManager for Self Monitoring module, also known as AM Health, provides Knowledge Scripts for monitoring the health and availability of AppManager components.

This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. We hope you continue to help us ensure our products meet all your needs. You can post feedback in the AppManager forum on Qmunity, our community Web site that also includes product notifications, blogs, and product user groups.

The documentation for this product is available on the NetIQ Web site in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click Add Comment at the bottom of any page in the HTML version of the documentation posted at the AppManager Modules page. To download this module, log into the AppManager Module Upgrades & Trials page.

What's New?

This release of AM Health includes the following new Knowledge Script:

AMHealth_AgentDown. Use this Knowledge Script to monitor the health of AppManager agents, raise events when agents are down or unavailable, and generate actions as appropriate. (ENG325729)

This release also resolves the following issues:

AMHealth_HeartbeatWin and AMHealth_QDBComponentsHealth Knowledge Scripts fail with an event message stating the jobs failed to execute the NetIQCtrl command. This release resolves an issue in which the AMHealth_HeartbeatWin and the AMHealth_QDBComponentsHealth scripts generated an event message stating that the NetIQCtrl utility command returned an error. With this release, the error with the NetIQCtrl utility command no longer occurs. (ENG326726, ENG328755, ENG330512, ENG328802, ENG330225)
AMHealth_HeartbeatWin Knowledge Script generates a Microsoft VBScript type mismatch event message in locales other than the United States. This release resoves an issue in which running the AMHealth_HeartbeatWin script in locales other than English (United States) resulted in the following error: Microsoft VBScript runtime error [Line: 1089] Type mismatch: 'strCorrectDate'. In this situation, the script incorrectly calculated the date in the non-American locale. With this release, an update to the script ensures that the date is properly calculated for all locales. (ENG330598, ENG327144)
AMHealth_HeartbeatWin Knowledge Script incorrectly generates an event stating that there are no jobs for QDB sites. This release resolves an issue in which the script generated a number of incorrect event messages for different QDBs that stated No jobs for QDB site [QDBName]. With this release, the script no longer generates the incorrect events. (ENG326330)
AMHealth_HeartbeatWin incorrectly reports that jobs are exceeding the maximum run time in some locales. With this release, an update to the script ensures that the run times are properly calculated in all locales, preventing the maximum run time events. (ENG330160)
AMHealth_QDBComponentsHealth Knowledge Script causes an Unexpected end of file event message. This release resolves an issue in which running the AMHealth_QDBComponentsHealth script raised the following event message: Utilized Log space for the tempdb database is high. With this release, an update to the AMHealth_QDBComponentsHealth script prevents this event message from occurring. (ENG329647)
AMHealth_QDBComponentsHealth Knowledge Script cannot connect to the SQL Server. This release resolves an issue that occurred when the QDB and management server components were installed on a SQL Server that was configured with the server and port number, the Discovery_AMHealth Knowledge Script failed to discover the QDB and management server components, and the AMHealth_QDBComponentsHealth Knowledge Script failed to monitor the QDB and management server components. With this release, these two scripts work as expected in this situation. (ENG325720)
AMHealth_QDBComponentsHealth Knowledge Script generates an inaccurate event time. This release resolves an issue in which the AMHealth_QDBComponentsHealth script generated an event time that does not match the event time in the management server and the QDB. With this release, the event time is consistent in Control Center, the management server, and the QDB. (ENG329241, ENG329758)

To get the updates provided in this release, you must install the module to the repository (QDB) and then propagate changes to any running jobs for the Knowledge Scripts that were updated in this release. This module requires AppManager 8.x, and it does not automatically update renamed or copied Knowledge Scripts. For more information, see the "Upgrading Knowledge Script Jobs" section in the new management guide.

This release of AM Health replaces all Previous Releases.

Return to Top

System Requirements

For the most recently updated list of supported application versions, see the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.

AM Health requires AppManager version 8.0 or later installed on the AppManager repository (QDB) computer and on all console computers.

For more information, see the new AppManager for Self Monitoring Management Guide, included in the download package.

Return to Top

Contents of the Download Package

AM Health includes Knowledge Scripts to discover and monitor your AppManager resources. The download package includes this Readme, a management guide, Help for Knowledge Scripts, and several files that are used during installation:

AM70-AMHealth-8.0.131.0.msi, the module installer.
AM70-AMHealth-8.0.131.0.ini, a configuration file used with the AppManager setup program.
AM70-AMHealth-8.0.131.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.

When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.

Return to Top

Installing This Module

Run the module installer on all console computers to install the Help and console extensions. Run the module installer only once on each of these computers.

You must also install the Knowledge Scripts. You can install these components into local or remote QDBs. When installing to the primary QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.

Important Run the module installer only for the primary QDB, and Control Center will automatically replicate this module to secondary QDBs.

Install Knowledge Scripts 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.

For more information about installing this module, see the AppManager for Self Monitoring Management Guide, included in the download package.

Return to Top

Known Issues

NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.

Discovery_AMHealth Knowledge Script might not discover roles. You must upgrade the local agent component on QDB and CCDB computers to successfully run jobs from the new AppManager Health module. Otherwise, the Discovery_AMHealth Knowledge Script might not discover and display the repository roles in the Control Center and Operator Consoles. The installation process does not remind you to upgrade the repository agents. (ENG300814)
AMHealth_HeartBeatWin Knowledge Script generates an Unable to process jobs list error message for XP computers. The AMHealth_HeartBeatWin Knowledge Script running on a Windows XP computer might fail to communicate with the agent and return the following message: AppManager V3.1: Unable to process job list - failed to retrieve joblist information. This failure occurs because Remote Procedure Call (RPC) on Windows XP requires that all RPC callers must be able to authenticate using NT LAN Manager (NTLM). The AMHealth_HeartBeatWin Knowledge Script uses RPC calls but does not authenticate using NTLM.

To work around this issue, set the following registry entries to zero and reboot the Windows XP computer:
- HKLM\Software\Policies\Microsoft\Windows NT\RPC\EnableAuthEpResolution
- HKLM\Software\Policies\Microsoft\Windows NT\RPC\RestrictRemoteClients
This issue does not affect communication between the management server and the agent because the management server does not make RPC calls to the agent computer. (ENG287443)

Return to Top

Previous Releases

This release of AM Health includes enhancements added in previous releases.

AppManager for Self Monitoring (AM Health) 8.0.113.0, October 2012

Discovery_AMHealth Knowledge Script fails if Microsoft .NET Framework version 2.0 is not installed on agents. This release resolves an issue in which the Discovery_AMHealth Knowledge Script failed with the following message: AppManager discovery failed (roles). The discovery did not fail on management servers, but only on agents that did not have .NET 2.0 installed. With this release, the discovery process succeeds even on agent computers that do not have .NET 2.0 installed. (ENG311953)
Discovery_AMHealth Knowledge Script fails with an invalid procedure call or argument error message. This release resolves an issue in which the Discovery_AMHealth script failed to discover a management server when the number of characters in the AllowMS registry key on the management server was greater than 256. With this release, the Discovery_AMHealth script can discover a management server with an AllowMS key that has more than 256 characters. (ENG320039, ENG316028)
AMHealth_CCComponentsHealth Knowledge Script does not retreive a SQL user. This release resolves an issue in which AMHealth_CCComponentsHealth Knowledge Script was unable to retrieve a SQL user set up with SQL authentication. With this release, this script works with both Windows and SQL authentication, provided that you set up the user credentials with AppManager Security Manager. (ENG314194)
AMHealth_QDBComponentsHealth and AMHealth_CCComponentsHealth Knowledge Scripts incorrectly calculate file growth. This release resolves an issue in which these scripts generated incorrect events about insufficient disk space when sufficient space existed. With this release, the AMHealth_QDBComponentsHealth and AMHealth_CCComponentsHealth scripts correctly calculate disk space and file growth. (ENG310646, ENG323257)

AppManager 8.0.1.0, January 2012

The AM Health module was previously included as part of the AppManager release, and not as a standalone module.

This initial release of the AM Health module provides Knowledge Scripts for monitoring the health and availability of AppManager components, including QDBs, the CCDB, management servers, agent computers, the command queue service, the Deployment Service, and the Deployment Web Service. The setup program installs this module during QDB installation. The module includes two new Discovery Knowledge Scripts, four Knowledge Scripts, and two Knowledge Script Groups (KSGs).

The following AM Health Knowledge Scripts are available in this release:

Discovery_AMHealth: Discovers AppManager server resources (QDB, management server, and agent) and Control Center server resources (CCDB, command queue service, and Deployment Service) installed on Microsoft Windows servers.
Discovery_AMHealthUNIX: Discovers AppManager agent resources installed on UNIX or Linux servers.
CCComponentsHealth: Monitors the health and availability of SQL Server resources associated with Control Center components.
HeartbeatWin: Monitors the AppManager agent heartbeat signal and job execution in a Microsoft Windows environment.
HeartbeatUNIX: Monitors the AppManager agent heartbeat signal in a UNIX or Linux environment.
QDBComponentsHealth: Monitors the health and availability of SQL Server resources associated with the QDB and the management server.
HealthCheckAMAgentComponents Recommended Knowledge Script Group: Includes the HeartbeatWin and HeartbeatUNIX Knowledge Scripts.
HealthCheckAMCoreComponents Recommended Knowledge Script Group: Includes the CCComponentsHealth and QDBComponentsHealth Knowledge Scripts.

Return to Top

Contact Information

Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.

For detailed contact information, see the Support Contact Information page.

For general corporate and product information, see the NetIQ Corporate Web site.

For interactive conversations with your peers and NetIQ Corporation experts, become an active member of Qmunity, our community Web site that offers product forums, product notifications, blogs, and product user groups.

Return to Top

Legal Notice

THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.

For purposes of clarity, any module, adapter or other similar material ("Module") is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.

This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.

This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.

U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.

For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.

Return to Top