AppManager 9.1 includes new features, improves usability, and resolves several previous issues.
Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
The documentation for this product is available on the NetIQ website in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the AppManager Documentation page. To download this product, see the AppManager Suite Product Upgrades website.
The following outline the key features and functions provided by this version:
AppManager 9.1 adds support for the following Microsoft operating systems and databases:
Windows Server 2012 R2
For the AppManager repository (QDB) and Control Center repository (CCDB), SQL Server 2014 Standard and Enterprise editions
For environments with all components on one computer, SQL Server 2012 Express (32-bit and 64-bit)
For environments with all components on one computer, SQL Server 2008 Express (32-bit and 64-bit)
AppManager 9.1 includes the following enhancements:
Architectural changes with version 9.1 allow for increasing the capacity of the AppManager repository (QDB) and management server by approximately three times using your existing configuration.
In test environments, increasing the workload on the management server rarely caused the persistent IO cache to fill to capacity. In scenarios that were designed to cause the cache to fill, the cache cleared quickly without causing performance issues.
AppManager 9.1 reduces the amount of disk space that the QDB requires by implementing a streamlined method of collecting and storing data.
Previously, AppManager stored data in two tables in the QDB, resulting in some duplication of stored data. In addition, if a Knowledge Script generated data details in addition to data points, AppManager collected the data details by default.
With version 9.1, AppManager stores all of the data that it collects for a given day in one table per day, and removes old tables periodically. A setting in the Control Center console allows you to control how often AppManager removes old tables. In addition, AppManager no longer collects data details by default. A setting in the Operator Console allows you change the default behavior.
For more information about the changes to data collection and storage, see Data Collection and Storage.
AppManager 9.1 includes a command line utility, MigrateQ.exe, that automates migrating existing agents to a new QDB and allows you to migrate multiple agents simultaneously, if needed. You can migrate version 7.0.2 and later agents to new QDBs. For more information about using the utility, see Migrating an Agent to a New QDB in the Upgrade and Migration Guide for AppManager.
AppManager 9.1 includes several changes to expected behavior. The following sections provide more information:
To allow small environments to host QDBs and the Control Center repository (CCDB) on SQL Server Express editions, AppManager 9.1 includes a new service called the NetIQ AppManager Task Scheduler Service. The service schedules SQL Server jobs for the repositories. In earlier versions of AppManager, the SQL Server Agent scheduled the jobs.
For version 9.1 repositories to function correctly, you must install the service and then use the Task Scheduler Configuration Utility to add the repositories to the service. You also use the utility to change the schedule for SQL Server jobs. For more information about installing and configuring the service, see Installing a Management Site in the Installation Guide for AppManager.
To reduce the amount of space that collected data uses in the QDB, AppManager 9.1 implements a streamlined method of collecting and storing data. The following table summarizes the differences between AppManager 8.x and 9.1. For more information about collecting and storing data, see Managing Data and Managing a QDB in the Administrator Guide for AppManager.
|
AppManager 8.x |
AppManager 9.1 |
|---|---|
|
Stored collected data for use in short-term charts and graphs in the Data table for eight days (by default) |
Stores data that it collects on a given day in Data_yyyymmdd tables for immediate display in real-time charts and graphs for 30 days (by default), and each day removes tables that are more than 30 days old A new option in the Control Center console, Remove old data after, allows you to change the default retention period. For more information, see Global Preferences Options in the Control Center User Guide for AppManager. |
|
Stored data for long-term reporting in the ArchiveData table indefinitely (by default) |
Does not store data separately for long-term reporting Instead, AppManager stores all of the data that it collects on a given day in Data_yyyymmdd tables for immediate display in real-time charts and graphs for 30 days (by default), and each day removes tables that are more than 30 days old. A new option in the Control Center console, Remove old data after, allows you to change the default retention period. For more information, see Global Preferences Options in the Control Center User Guide for AppManager. NOTE:If you upgrade from a previous version of AppManager, data that was archived before the upgrade will no longer be available. If you have long-term reporting needs, NetIQ Corporation recommends using NetIQ Analysis Center. Alternatively, you can increase the amount of time AppManager retains the Data_yyyymmdd tables, but NetIQ Corporation recommends keeping only as much data as you need for charts and graphs. |
|
Provided options for periodically archiving and aggregating data in the QDB to prevent the ArchiveData table from becoming too large |
Streamlined method for collecting and storing data makes the archiving and aggregating options obsolete |
|
By default, collected data details with data points if the Knowledge Script generated those details and stored them in the Data table |
By default, does not collect data details with data points The Collect data details with data point repository preference in the Operator Console allows you to select whether to collect data details by default. The Data_yyyymmdd tables store any data details you collect. If you are upgrading to AppManager 9.1, the upgrade does not change the current setting for the Collect data details with data point repository preference. |
AppManager now considers operating systems to be logical servers and represents them as root application objects in the consoles. Related objects, such as CPU, no longer appear as direct child objects of servers, but instead appear as child objects of the operating system root (for example, WindowsOS:Server_Name).
Previously, when Knowledge Script jobs in the NT and UNIX categories raised events, the events appeared in either the NT or UNIX view in the Operator Console (depending on the operating system of the computer where the job ran). Now, those events only appear in the Master view and any views or management groups that are based on the Master view.
As part of the effort to reduce the size of the QDB and improve performance, the database schema no longer supports storing information in a format that allows presenting it in snapshot and dynamic views in the Operator Console. Starting with this version, you can no longer create snapshot or dynamic views. If you configured snapshot or dynamic views in earlier versions of AppManager, those views will be standard views after you upgrade to this version.
As an alternative, use the Control Center console to create rule-based management groups. For more information, see About Rule-based Management Groups in the Control Center User Guide for AppManager.
To prevent performance issues, the option to switch to another QDB without logging out of the Operator Console is no longer available. To switch to another QDB, you must log out of the console and then log in again with the desired QDB and server names.
Before you upgrade to version 9.1, all components must be version 8.2, with the exception of the Windows agent. You can upgrade version 7.0.1 and later Windows agents to version 9.1.
AppManager version 9.1 requires that the CCDB and the primary QDB be the same version. You can either create a new version 9.1 primary QDB or upgrade your existing version 8.2 primary QDB to version 9.1. You cannot upgrade QDBs earlier than version 8.2 to version 9.1.
Before you upgrade the CCDB to version 9.1, ensure that it does not contain any QDBs that are earlier than version 8.2. If it does, either remove the QDBs or upgrade them to version 8.2.
For more information about the requirements for upgrading components, see Upgrading Management Servers and Agents in a Single QDB Environment and Upgrading Components in a Multiple-QDB, Control Center Environment in the Upgrade and Migration Guide for AppManager.
For detailed information about hardware and software requirements, see System Requirements in the Installation Guide for AppManager.
If you currently use the AppManager Operations Portal and plan to continue using it with AppManager 9.1, you must install the latest Patch Bundle for AppManager Operations Portal. To obtain the latest Patch Bundle, contact Technical Support.
For information about installing AppManager, see the Installation Guide for AppManager, available on the AppManager Documentation page.
For information about upgrading AppManager, see the Upgrade and Migration Guide for AppManager, available on the AppManager Documentation page.
NetIQ Corporation strives to ensure that 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.
Section 4.1, Task Scheduler Configuration Utility Allows Duplicate QDBs in Some Cases
Section 4.2, Agent Migration Utility Does Not Migrate Custom Property Descriptions
Section 4.4, SQL Server AlwaysOn Availability Groups Require Manual Discovery After Upgrade
Section 4.5, Manual Discovery Required for Task Scheduler Service
Section 4.6, Re-added Scripts and Groups Do Not Synchronize to Non-primary QDBs
Issue: If the default instance of Microsoft SQL Server Express hosts a QDB, it is possible to add the QDB to the Task Scheduler service twice: once by specifying the SQL Server name and once by specifying the SQL Server name with the instance name.
Workaround: Use the Task Scheduler Configuration Utility to remove the duplicate QDB from the service. For more information, see Adding Repositories to the Task Scheduler Service in the Installation Guide for AppManager.
If you use the MigrateQ.exe utility to migrate an agent that has custom properties where you also provided descriptions of the custom properties, the utility does not migrate the descriptions along with the custom properties.
If you select either of the secure communications options (encrypted communications only or authentication and encrypted communications) when you install the QDB and agents, agent computers require more time (approximately 20 minutes) to establish initial connections with management servers. During this time, agent computers might appear offline in the Control Center console.
After you upgrade to version 9.1, to view SQL Server AlwaysOn Availability Groups that you discovered before the upgrade, you must run the Discovery_SQLServer Knowledge Script to re-discover the resources. For more information about discovering SQL Server resources, see the AppManager for Microsoft SQL Server Management Guide, available on the AppManager Modules Documentation page.
Issue: If you install the NetIQ AppManager Task Scheduler service on an agent computer without any other AppManager components installed, the Discovery_AMHealth Knowledge Script does not run automatically to discovery the service for health monitoring in Control Center.
Workaround: After you install the agent and the service, manually run the Discovery_AMHealth Knowledge Script.
Issue: If you remove a Knowledge Script or Knowledge Script Group from the Control Center console and then immediately add the same script or group back to the console, AppManager does not synchronize the re-added script or group to non-primay QDBs.
Workaround: If you plan to delete a Knowledge Script or Knowledge Script Group and then add it again, wait at least one minute after you delete the script or group and then re-add it.
Because of the new, streamlined method of collecting and storing data in AppManager 9.1, some of the repository preferences that you could previously set in the Operator Console are no longer valid. The Operator Console User Guide for AppManager refers to these invalid preferences. In Chapter 3, “Configuring the Operator Console,” the “Set Preferences for Data Management” subsection refers to the following preferences that are no longer valid:
Default period to keep points in data table
Move archived points to aggregate table
Time interval to purge old points in repository
Automatically update last, minimum, maximum and average value for graph data
For more information about the new method for collecting and storing data, see Data Collection and Storage.
Also as part of the effort to reduce the size of the QDB and improve performance, the database schema no longer supports storing information in a format that allows presenting it in snapshot and dynamic views in the Operator Console. Information in the Operator Console User Guide about using snapshot and dynamic views is no longer valid.
The Operator Console no longer allows you to switch to another QDB without logging out of the console. Information in the Operator Console User Guide about the File > Connect Repository menu item is no longer valid.
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 website.
For general corporate and product information, see the NetIQ Corporate website.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
NetIQ AppManager is covered by United States Patent No(s): 05829001, 05986653, 05999178, 06078324, 06397359, 06408335.
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.
© 2015 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.