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

Release Notes

July 07, 2009


Contents

Welcome to Quest QMX Base Framework

New in this Release

Resolved Issues

Enhancements

Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

For More Information

 


Welcome to Quest QMX Base Framework

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.

 


New in This Release

 

06/09/2009 Modified eXcSoftwareInstallationPrerequisiteChecker.js to process VMM (request by Norm)
06/10/2009 Modified CommonRoutinesInsertPerformanceRecord.js, function InsertPerformanceRecordJS2UsingSingleton

to add the "Swedish" comment for non-English systems. Ultimately, we want this to be

handled dynamically

06/16/2009 Modified eXcSoftwareOM2007eXctender.cs, re-added public method GetnonWindowsComputerOpsMgrObjectID since it is being used by the VMWare VA
06/17/2009 Modified __BuildProjects.js to always set the /rebuild argument for eXcVADebugger project since it has a proxy stub dll
06/22/2009 Created new script file MOM\CommonRoutinesConnectorProcessingExceptions.js
06/22/2009 Modified MOM\CommonRoutinesConnector.js, added new function InteractWithHuman()
06/25/2009 Modified eXcSoftwareOM2007eXctender.cs, method DebugOut to write to filesystem log file added public property (on COM object) DebugLog to be able to set the filesystem log file
06/25/2009 Modified MOM\GlobalVariables.js to add g_boolDebugOpsMgrSingletonSDKCalls (default false)
06/25/2009 Modified MOM\_GlobalVariables.xml to add g_boolDebugOpsMgrSingletonSDKCalls (default false)
06/25/2009 Modified MOM\eXcGUI\_GlobalVariables.html to add g_boolDebugOpsMgrSingletonSDKCalls description text
06/25/2009 Modified MOM\eXcOpsMgrSingleton.js to set DebugLog on eXcSoftwareOM2007eXctender if

g_boolDebugOpsMgrSingletonSDKCalls = true

06/26/2009 Modified eXcGUI\JavaScriptLogic.js, function Validate to not allow IP address/FQDNs to be specified in the __Hosts.xml
06/26/2009 Modified eXcGUI\JavaScriptLogic.js, function Validate to properly set focus on element where unique validation

occurs (i.e. if there are > 1 unique validations on a row)

06/26/2009 Modified MOM\CommonRoutinesSNMPWatchdog.js so it is not a time 0 script
06/30/2009 Modified ScriptManagerImpleBase.cpp, method CScriptManagerImplBase::DetermineVirtualAgentType to set VA type to DOTNET when file extension has .CMD. Trying to get CLILargeScreen going for %RDY
06/30/2009 Modified CommonRoutinesVirtualAgentFactory.js, function BuildArgumentList to put quotes around

program for DOTNET VA type

06/30/2009 Modified eXcSoftwareOM2007eXctender.cs, method CheckPerformanceRuleWithinManagementPack fixed bug

where m_ManagementPackBase was null and it needed to be populated since it is a reference

in the dynamic management pack.

07/01/2009 Modified CommonRoutinesInsertPerformanceRecord.js, function InsertPerformanceRecordJS2SCOM to

segment opsmgr dynamic rule generation logic into its own function ProcessWriteOpsMgrPerfMetricsToDWDB.

Also added global variable g_boolUseScriptAndWMICacheForDynamicOpsMgrRules so that we can easily

disable caching if needed.

07/01/2009 Modified MOM\eXcOpsMgrSingleton.js to trace API calls to write to DebugLog on error
07/01/2009 Created compiled version of eXcOpsMgrSingleton project at

C:\Projects\eXc\WMI_Providers\nonWindows\MOM\eXcOpsMgrSingleton. In the scripted version

(see C:\Projects\eXc\WMI_Providers\nonWindows\VirtualAgentLibrary\MOM\eXcOpsMgrSingleton.js), the

MS XMLDOM ActiveX object cannot handle large, sustained loads. Under this load, it randomly gets

"Permission Denied" exceptions. Even stranger, the exception occurs within a jscript try-catch

but the exception is not handled by the catch. Therefore, I moved all the logic into a compiled

C# program (unfortunate but until I can resolve this XMLDOM issue...).

07/01/2009 Modified MOM\eXcOpsMgrSingleton.js to call compiled version
07/06/2009 Added C:\Projects\eXc\WMI_Providers\nonWindows\MOM\eXcOpsMgrSingleton\eXcOpsMgrSingletonDotNet20.sln

to __BuildProjectsList.txt

07/06/2009 Added eXcOpsMgrSingleton.exe to Setup[64|32]_[Debug|Release]_VS200[5|8]
07/06/2009 Added MOM\CommonRoutinesConnectorProcessingExceptions.js to Setup[64|32]_[Debug|Release]_VS200[5|8]

Resolved Issues

The following is a list of issues addressed in this release of QMX Base Framework.

 

Feature

Resolved Issue

Defect ID

QMX Base Framework generating dynamic Operations Manager rules for performance data being written to the Operations Manager datawarehouse A bug was introduced in QMX Base Framework 4.0.0.499 that prevented the generation of the dynamic Operations Manager rules which were used to move the non-Windows performance metrics into the Operations Manager Datawarehouse database.  The bug has been corrected.  
QMX Base Framework Operations Manager Singleton excessive memory consumption and timeouts

 

The script version of the Operations Manager Singleton was consuming an excessive amount of memory.  In addition, under heavy loads, the script would produce timeouts in the client code (i.e. the QMX extension scripts) and/or lock-up.  This appears to be an issue with the Microsoft XMLDOM ActiveX control.  We were able to reproduce this error in the lab.  It was unclear how to resolve this error so the Operations Manager Singleton was rewritten (into compiled C# code).  Running as compiled code has resolved all this issues described.  

New Enhancements

The following is a list of enhancements implemented in this release of the QMX Base Framework.

 

Feature

The prerequisite checker program now checks on VMM prerequisites.

 

QMX connectors can now call into Connector "exception" rules which accommodate for Management Packs that do not follow the Operations Manager standard.

Added a global variable flag (g_boolDebugOpsMgrSingletonSDKCalls) so that detailed error information can be collected for Operations Manager SDK API calls.

SNMP Watchdog logic will poll rather than run as a "time 0" script to allow a lower overall memory consumption by QMX.


Known Issues

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

 

 


Upgrade and Compatibility

 

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.502 from a release that is earlier than 4.0.0.499, you need to re-import the QMX base (Operations Manager) Management Pack.  Note that you do not need to unload the MP first, you can just re-import over the existing MP.

 


System Requirements

 

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

 


Global Operations

 

Currently, the QMX Base Framework only supports English systems.

 


For More Information

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.

 

Contacting Quest Software:

Email info@quest.com
Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web

http://www.quest.com

Refer to our Web site for regional and international office information.

Contacting Quest Support:

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

 

www.quest.com

Email: legal@quest.com

Refer to our Web site for regional and international office information.

 

Trademarks

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.

 

 

Third Party Contributions

N/A

 

Disclaimer

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.