NetIQ AppManager |
Version 8.2 |
Release Notes |
Date Published: June 2013 |
|
|
AppManager version 8.2 includes new features and improves usability. 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 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. For more information about this release and for the latest release notes, see the AppManager Documentation Web site. To download this product, see the AppManager Suite Product Upgrades Web site. What's New?The following outline the key features and functions provided by this version, as well as issues resolved in this release: Software EnhancementsAppManager version 8.2 includes the following software enhancements:
The enhancements this version provides are available only for AppManager repositories (QDBs) that you choose to upgrade. For information about the requirements to maintain older versions of QDBs in an 8.2 environment, see System Requirements. View Details about Specific Entities in the Managed Environment through New Default Management GroupsAppManager version 8.2 includes a new default management group, AM Logical Servers, that includes all physical computers as well as specific entities on those computers as top-level objects. These entities are known as logical servers and include the following object types:
Including both the physical computers and logical servers as top-level objects allows you to view details about the computers as a whole or about only specific entities on those computers. The AM Logical Servers management group is divided into the following management groups:
The new management groups include only physical computers and logical servers that belong to QDBs you upgrade to version 8.2. The management groups do not include objects that belong to QDBs that you choose not to upgrade. For more information about the new management groups, see the Control Center User Guide for AppManager, available on the AppManager Documentation Web site. Create Rule-based Management Groups Made Up of Specific Entities on a Physical ComputerWhen you created rule-based management groups with previous versions of AppManager, Control Center displayed the complete discovered hierarchy of entities for each computer selected as a group member. To manage specific entities on the computer, you had to navigate the complete hierarchy to locate the specific entity you wanted to investigate. In addition, you could not isolate the entities into their own groups. With AppManager version 8.2, you can create rule-based management groups consisting of physical computers, logical servers, or both. The ability to create rule-based management groups made up of logical servers gives you more flexibility in defining your view of the managed environment. For example, you can manage SQL Servers by location or manage a select set of SQL Server databases without having to view all of the discovered objects on the SQL Server. For QDBs you choose not to upgrade to version 8.2, rules you create to select logical servers will not select objects from those QDBs. For more information about creating rule-based management groups, see the Control Center User Guide for AppManager, available on the AppManager Documentation Web site. Assign Custom Properties to Additional Object TypesPreviously, you could only assign custom properties to physical computers. With AppManager version 8.2, you can assign custom properties to both physical computers and logical servers. By assigning custom properties to logical servers, you can create rule-based management groups that allow you to dynamically manage logical servers in addition to physical computers. For more information about using custom properties with logical servers, see the Control Center User Guide for AppManager, available on the AppManager Documentation Web site. View Charts and Data Streams for Specific Objects in Servers ViewsPreviously, you could only view charts and data streams at the physical computer level. With AppManager version 8.2, when you select an object in a Servers view in the Control Center console (regardless of whether the object is a physical computer or a logical server), the Charts tab displays only the charts and data streams for that specific object. For example, if you select a Virtual Center server, you will now see only the charts and data streams related to the virtual server rather than all charts and data streams for the physical host. Operating System SupportAppManager version 8.2 includes support for the following operating system versions:
Software FixesAppManager version 8.2 includes the following software fixes:
AppManager Modules with Embedded Configuration Wizards Cannot Launch the Wizard During Module InstallationIf you install a module that has an embedded Configuration Wizard, the module now successfully launches the wizard at the end of the installation. This fix applies to the following modules (ENG326686):
Chart Component Does Not Install When Accessing Operator Web Console from Remote ComputerIf you access the Operator Web Console from a remote computer and click Charts to install the chart component, AppManager now successfully installs the component. (ENG327936) Previously, AppManager displayed the following error message when you clicked Charts: The module "AMChartHost.ocx" failed to load. Changes to Expected BehaviorAppManager version 8.2 includes the following changes to expected behavior:
QDB Upgrade Cannot Continue if the SQL Server Agent Service is DownWhen you upgrade a QDB to version 8.2 and the SQL Server Agent service is down, the setup program informs you that the service is down and does not allow you to continue until you start the service. Previously, the setup program warned you that the service was down but allowed you to continue if you chose not to start it. Upgrade Cannot Continue with Active QDB or CCDB ProcessesWhen you upgrade a QDB or the CCDB with active processes to version 8.2, the setup program informs you of the active processes and does not allow you to continue until you stop the active processes. Previously, the setup program warned you about the active processes but allowed you to continue the upgrade if you chose not to end them. Data from QDBs that Are Unavailable During and Following CCDB Upgrade Remains Unavailable Until the QDBs Are AvailableIf a non-primary QDB is unavailable when you upgrade the CCDB to version 8.2 and remains unavailable for some time after the upgrade completes, when you open the Control Center console after the upgrade, data from the non-primary QDB is not available until the QDB is available. Previously, the data was available even if the QDB was not. Managing Custom Properties in Service Map Views Does Not Apply to Embedded Views or to Non-machine Objects that Belong to Non-upgraded QDBsAfter you upgrade to version 8.2, you can manage custom properties for both physical computers and logical servers from within Service Map views as long as the objects are not included in embedded Servers, Service Map, or Events views. You cannot manage custom properties for embedded views within a Service Map view. In addition, before version 8.2, if you defined a custom property for a child object of a physical computer (for example, a CPU) in a Service Map view, AppManager created the custom property against the physical computer. If you selected the child object in the Service Map view, Control Center displayed all of the custom properties defined against the physical computer for that child object on the Custom Properties tab. After you upgrade to version 8.2, if you create a custom property for a child object of a physical computer that belongs to a QDB that you choose not to upgrade, if you select that child object in a Service Map view, Control Center will only display the custom properties that apply to the physical computer itself. You will not see custom properties defined for child objects of the physical computer. Some View-based Management Groups No Longer Include Physical Computers Where Application Resources Are InstalledAfter you upgrade a QDB to version 8.2, some view-based management groups (for example, SQL or IIS) no longer include the physical computer on which the SQL and IIS logical servers reside. As a result, deployment rules you previously configured to deploy to those management groups no longer work and you must configure new deployment rules. Server Name Filter No Longer Applies to Some Servers Views for View-based Management GroupsAfter you upgrade a QDB to version 8.2, if you previously applied the Server Name filter to a Servers view in an application view-based management group (for example, SQL or IIS), the filter is no longer valid and the Servers view is empty because the management group no longer includes physical computers. To filter the Servers view after you upgrade, re-create the filter and set the value to the logical server name. System RequirementsWhen you upgrade to version 8.2, you must upgrade all components included in the installation package. For QDBs, you must upgrade at least the primary QDB to version 8.2. Upgrading non-primary QDBs to version 8.2 is optional, but new features will not be available for those QDBs. Non-primary QDBs you attach to a version 8.2 CCDB must meet the following version requirements:
You can download the hotfixes from the AppManager Suite Hotfixes Web site. AppManager Versions Supported for Upgrade
Installing This VersionThis version supports new installations and upgrades from the versions listed in AppManager Versions Supported for Upgrade. For in-place QDB upgrades from AppManager 7 Platform Update to version 8.2, the setup program updates all stored procedures that AppManager modules use to the versions that are included with the 8.2 installation package. If you have a newer version of a module at the time you perform the upgrade, the setup program does not preserve the newer version. To get the newer version, you must reinstall the module after you complete the upgrade to version 8.2. For in-place QDB upgrades from version 8.0.x, the setup program does not update stored procedures that AppManager modules use and does not add stored procedures for modules that are included with the 8.2 installation package but do not currently exist in the QDB. To get any new modules, you must manually install them. If a new module includes updates to stored procedures, you must install the module for each QDB that is attached to Control Center. To determine whether you must install a module for each QDB or only for the primary QDB, see the management guide for the module. To install new components:
To upgrade components:
(Conditional) To upgrade a clustered QDB, run Setup.exe from any node in the cluster or from a remote computer. Enter the SQL Virtual Server name in the SQL Server Name\Instance field and the SQL Virtual Server QDB name in the Repository field. You do not need to failover the cluster for the upgrade. Any changes to cluster nodes that are offline during the upgrade are automatically propagated when the nodes are online. (Conditional) If you will upgrade the CCDB immediately after you upgrade the QDB, wait a few minutes for the service to update the QDB version information in the CCDB. (Conditional) To upgrade a clustered CCDB, run Setup.exe from any node in the cluster or from a remote computer. Enter the SQL Virtual Server name in the SQL Server Name\Instance field and the SQL Virtual Server CCDB name in the Repository field. You do not need to failover the cluster for the upgrade. Any changes to cluster nodes that are offline during the upgrade are automatically propagated when the nodes are online. After you complete the setup programs for the various components, Control Center resynchronizes with the QDBs. Because the synchronization must finish before complete data is available to Control Center, NetIQ Corporation recommends that you wait for the synchronization to finish before using the upgraded environment. The wait time varies according to the size of the environment. For large environments, a good practice is to perform the upgrade at a time when you can allow several hours before using the environment. For small environments, one hour is a sufficient wait time. Known IssuesNetIQ 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.
Control Center Fails to Select Windows and UNIX Computers with the Logical Servers of Matching Component Type Rule
Control Center Might Display an Incorrect Event Status for Physical Computers in Service Map ViewsFor physical computers in Service Map views, Control Center might incorrectly indicate that no events are present if the computer does not belong to the parent management group for the Service Map view. For example (ENG326364):
Control Center Does Not Retain Groupings by Server Name for Servers Views After Upgrade
Control Center Console Might Appear Unresponsive During Refresh in Large Environments
Developer's Console Stops Unexpectedly Upon Knowledge Script Check In for Some Operating Systems with User Access Control (UAC) Enabled
Upgrade Might Fail for QDBs with a Large Number of Users
Contact InformationOur 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 Web site. For general corporate and product information, see the NetIQ Corporate Web site. For interactive conversations with your peers and NetIQ experts, become an active member of Qmunity, our community Web site that offers product forums, product notifications, blogs, and product user groups. Legal NoticeNetIQ AppManager is protected 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. © 2013 NetIQ Corporation and its affiliates. All Rights Reserved. For information about NetIQ trademarks, see http://www.netiq.com/company/legal/. | ||||||||||||||||||||||||||||||||||||||||||||