Quest QMX Base Framework for
Quest Management Xtensions - Operations Manager (2007 & 2005 Editions)
Quest Management Xtensions - Configuration Manager (2007 & SMS Editions)
Quest Management Xtensions for Device Management (2007 & SMS Editions)
Quest Management Connectors - Operations Manager (2007 & 2005 Editions)
Quest Management Pack for AS400 - Operations Manager 2007 Edition
Quest Management Pack for z/OS - Operations Manager 2007 Edition
Version 4.0.0.505
Release Notes
August 05, 2009
Welcome to Quest QMX Base Framework
Upgrading the Base Framework Version
The Quest QMX Base Framework supplies services to the Quest Management extensions which in turn integrate into the Microsoft System Center product suite; namely Operations Manager, Configuration Manager, Virtual Machine Manager, Data Protection Manager and (outside of System Center) Microsoft Enterprise Single Sign-on (ENTSSO). In addition to supporting the Microsoft System Center product suite, QMX Base Framework and the library of QMX extensions support the Quest Big Brother and Foglight products.
The foundation of the QMX Base Framework is the Microsoft WMI technology and Microsoft scripting technology.
| 07/14/2009
|
Modified MOM\CommonRoutinesSNMP.js and MOM\CommonRoutinesSNMPVirtualAgent.js to populate CustomField4 with the word TRAP (using ThrowAlert2 call) |
| 07/22/2009 | Modified MOM\CommonRoutinesSNMPPerformanceMetrics.js to perform SNMP unoptimized v2 table walk |
| 07/22/2009 | Modified eXcSoftware.nonWindows.xml (changed version to 7.0.0.3) to add new performance metric template which uses the Operations Manager Client |
| 07/22/2009 | Modified MOM\GlobalVariables.js, added global variable g_boolUseOpsMgrSDKForPerfData (default is false) |
| 07/22/2009 | Modified MOM\OpsMgrGlobalVariables.xml, added global variable g_boolUseOpsMgrSDKForPerfData (default is false) |
| 07/22/2009 | Modified MOM\eXcGUI\OpsMgrGlobalVariables.html, added global variable g_boolUseOpsMgrSDKForPerfData |
| 07/22/2009 | Modified MOM\CommonRoutinesInsertPerformanceRecord.js, function InsertPerformanceRecordJS2SCOM to use global variable g_boolUseOpsMgrSDKForPerfData instead of hardcoded local variable |
| 07/22/2009 | Modified MOM\CommonRoutinesInsertPerformanceRecord.js, function ProcessWriteOpsMgrPerfMetricsToDWDB to pass global variable g_boolUseOpsMgrSDKForPerfData to eXcSoftwareOM2007eXctenderInterface.CheckPerformanceRuleWithinManagementPack |
| 07/22/2009 | Modified MOM\eXcOpsMgrSingleton.js, function ScriptVersion to pass global variable g_boolUseOpsMgrSDKForPerfData to eXcSoftwareOM2007eXctenderInterface.CheckPerformanceRuleWithinManagementPack |
| 07/22/2009 | Modified MOM\eXcOpsMgrSingleton.js, function CompiledVersion to pass global variable g_boolUseOpsMgrSDKForPerfData to eXcOpsMgrSingleton.exe |
| 07/22/2009 | Modified nonWindows\MOM\eXcOpsMgrSingleton\eXcOpsMgrSingleton.cs to accept new argument for g_boolUseOpsMgrSDKForPerfData and also to pass to call to eXcSoftwareOM2007eXctenderInterface.CheckPerformanceRuleWithinManagementPack |
| 07/22/2009 | Modified eXc_nonWindows_WMI_Provider.mof to change method SendPerformanceMetric to be static. Also,removed parameters strVirtualAgent and strVirtualAgentCategory and added DATETIME DATETIMEGenerated |
| 07/22/2009 | Modified eXc_nonWindows_OperatingSystem.cpp, method CeXc_nonWindows_OperatingSystem::SendPerformanceMetric to process new pararmeter list and commented out 2[strVirtualAgent, strVirtualAgentCategory], added one [DATETIMEGenerated]) |
| 07/22/2009 | Modified TheConstants.h, to add pDATETIMEGenerated |
| 07/22/2009 | Modified eXcSoftwareOM2007eXctender.cs, method CheckPerformanceRuleWithinManagementPack to accept new parameter boolUseOpsMgrSDKForPerfData_in. This will indicate whether to use the old eXcSoftware.nonWindows.nonWindowsObject.PerformanceRule.Template template or the new eXcSoftware.nonWindows.nonWindowsObject.PerformanceRule.TemplateV2 template in the eXcSoftware.nonWindows.xml Management Pack |
| 07/28/2009 | Modified __BuildProjectsList.txt so proper dependency projects get build in the proper order |
| 07/28/2009 | Renamed g_boolDebugOpsMgrSingletonSDKCalls to g_boolDebugOpsMgrSingletonCalls in MOM\GlobalVariables.js, eXcOpsMgrSingleton.js, _GlobalVariables.xml/html |
| 07/28/2009 | Moved g_boolDebugOpsMgrSingletonCalls from _GlobalVariables.xml/html to OpsMgrGlobalVariables.xml/html |
| 07/28/2009 | Modified eXcSoftwareOM2007eXctender.cs, method InsertPerformanceRecord to clarify the DebugOut to say "via Operations Manager SDK" to differentiate call to Operations Manager Client |
| 07/28/2009 | Modified eXcOpsMgrSingleton.cs to call DebugOut ("Inserting performance metric counter by means of Operations Manager Client") for WMI inserts |
| 07/28/2009 | Modified MOM\__GlobalVariables.xml to ship QMX with the OpsMgrSingleton off since the installer gets into an error state since OpsMgrSingleton now has a dependancy on the WMI Provider |
| 07/30/2009 | Modified eXcOpsMgrSingleton.cs, method Main to add Mutex so only one exe is ever running |
| 07/30/2009 | Modified eXcOpsMgrSingleton.csproj, to add <GenerateResourceNeverLockTypeAssemblies>true</GenerateResourceNeverLockTypeAssemblies> |
| 07/30/2009 | Modified MOM\CommonRoutinesSNMP.js to change "contact eXc" to "contact Quest" |
| 07/30/2009 | Modified MOM\CommonRoutinesSNMPVirtualAgent.js, functions SNMPTrapVirtualAgent2 and ProcessUsingDB to harden the logic around the AdditionalMessageFilterDBs.txt feature |
| 07/31/2009 | Modified eXc_nonWindows_WMI_Provider.mof, class eXc_nonWindows_Performance_Event to add strValue since opsmgr System.Performance.DataGenericMapper expects the value as a string. Also had to change eXc_nonWindows_Operatingsystem.cpp, TheConstants.h, CommonRoutinesInsertPerformancRecord.js, eXcOpsMgrSingleton.js and eXcSoftware.nonWindows.xml |
| 08/04/2009 | Modified EditHostsV4, Form1.cs, added member variable m_stringCurrentOpsMgrSDKSingletonBoolValue, created method GetOpsMgrSDKSingletonBoolValue and modified methods SetupOpsMgrGlobalVariablesXMLFileWatcher and m_FileSystemWatcher_Changed_OpsMgrGlobalVariablesXMLFile so that we only call SetGlobalWMIProperty on "UseOpsMgrSingleton" when the value has changed. |
The following is a list of issues addressed in this release of QMX Base Framework.
|
Feature |
Resolved Issue |
Defect ID |
| QMX Base Framework now inserts Operations Manager 2007 performance metrics using the Operations Manager agent rather than using the Operations Manager SDK. | The Microsoft Operations Manager SDK interface has limitations on the amount of data it can process. While this was the recommended approach from Microsoft as the Operations Manager initially released, Microsoft has since recommended to Quest that using the Operations Manager agent is a more efficient way for QMX to insert the performance metric data. QMX will continue to support both modes using the agent approach as the default. | |
|
QMX Base Framework Operations Manager Singleton
|
Under certain conditions, multiple QMX Operations Manager Singleton processes could be started simutaneously, causing exceptions to be thrown. These exceptions were on the eXcOpsMgrSingleton.exe and were being logged to the NT application log. |
The following is a list of enhancements implemented in this release of the QMX Base Framework.
|
Feature |
|
QMX Base Framework now inserts Operations Manager 2007 performance metrics using
the Operations Manager agent rather than using the Operations Manager SDK.
|
The following is a list of issues known to exist at the time of this release of the QMX Base Framework.
|
Feature |
Known Issue |
Defect ID |
| N/A |
N/A |
This version of QMX is backwards compatible with previous versions. Please note however that if you are upgrading to QMX Base Framework 4.0.0.505 from a release that is earlier than 4.0.0.505, you need to re-import the QMX base (Operations Manager) Management Pack (which is now at version 7.0.0.3). Note that you do not need to unload the MP first, you can just re-import over the existing MP.
Before installing the QMX Base Framework, ensure your system meets the following minimum hardware and software requirements:
| Platform | x86 or x64 |
| Memory | Recommended 8GB+ |
| Hard Disk Space | Recommended 100GB+ |
| Operating System | Windows 2003 Server, Windows 2008 Server, Windows XP, Windows Vista |
| Additional Software | N/A |
Currently, the QMX Base Framework only supports English systems.
The following explains how to upgrade your Quest QMX Base Framework from an older version that is already installed. For step-by-step instructions on how to install the Base Framework for the first time, please refer to the Installation Guide.
Note: You use the same Base Framework for all of the System Center products that Quest supports.
To upgrade your Quest QMX Base FrameworkBefore you upgrade the Base Framework, save all .xml files so that you can restore any customized
variable settings once you have completed the upgrade:
Assuming that the Quest QMX Base Framework is installed on C:,
copy all the .xml files from
C:\Program Files\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\MOM to
C:\Program Files\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\MOM\Backups.
Note: There will be an .xml file for each Global Variable tab that you see in the QMX Configuration tool.
For example, there will be an .xml file for the _GlobalVariable.xml tab, the MOMGlobalVariables.xml tab,
and the OpsMgrGlobalVariables.xml tab.
Start the Configuration Tool.
Stop any running Extensions.
On the MOM GlobalVariables tab, unselect the g_boolAutomaticallyStartVirtualAgents and g_boolUseOpsMgrSingleton global variables, if they are selected, and click Save.
Close the Configuration Tool.
From the Start menu, navigate to the Control Panel |Add or Remove Programs and remove the current version of Quest QMX Base Framework
Note: Older versions of Quest QMX Base Framework are called "eXc Software eXctender Event Provider for non-Windows..."; newer versions are called "Quest QMX base framework for Windows...".
Download and install the latest Quest QMX Base Framework from: Trial Downloads:
Click Save to download the .zip file to a location of your choice.
Extract all the files from the .zip.
Double-click the .exe file to start the Setup wizard.
Note: You must install the latest Base Framework to the same directory as the previous version so that existing Extensions will work properly.
Restore any customized variable settings you had before the upgrade:
Verify the values for the Global Variables by opening the _GlobalVariable.xml file and the
OpsMgrGlobalVariables.xml file that you copied before you started (see step #1).
Compare the values for each variable in the .xml file to the corresponding variables in both
the GlobalVariable tab and the OpsMgrGlobalVariable tab in the QMX Configuration Tool.
For Values that were overwritten by the upgrade, copy the values from the .xml file and
paste the content into the Value box of the Configuration Tool
Restart the Windows Management Instrumentation service:
Right-click the My Computer icon on your desktop and select Manage.
Navigate to Services and Applications | Services.
Right-click Windows Management Instrumentation and select Restart.
Close the Computer Management window.
Start the Configuration Tool.
If you unselected the g_boolAutomaticallyStartVirtualAgents and g_boolUseOpsMgrSingleton
global variables on the MOM GlobalVariables tab in step #4, re-select them and click Save.
Wait approximately 3-5 minutes for the non-Windows Proxy Discovery to complete inside the Operations Manager Console.
Re-start the Extension(s).
Get the latest product information, find helpful resources, test the product betas, and join a discussion with the Quest QMX Base Framework team and other community members. Join the Management Extensions Web site at Management Extensions.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA |
|
| Web |
Refer to our Web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.
Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.
From SupportLink, you can do the following:
View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.
This guide is available in English only.
© 2009 Quest Software, Inc.
ALL RIGHTS RESERVED.
This document contains proprietary information protected by copyright. The software described in this document is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Quest Software, Inc.
If you have any questions regarding your potential use of this material, contact:
|
Quest Software World Headquarters
LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656
Email: legal@quest.com |
Refer to our Web site for regional and international office information.
Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, InTrust, IT Dad, JClass, Jint, JProbe, LECCOTech, LiteSpeed, LiveReorg, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQLab, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
N/A
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.