NetIQ Module Builder allows subject matter experts to create customized AppManager modules that are specific to the set of applications the company wants to monitor and manage. This Readme covers information related to Module Builder Editor.
This release improves usability and resolves 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 Modules page. To download this product, see the AppManager Module Upgrades & Trials website.
This release provides the following enhancements:
Support for Microsoft Windows Server 2012 R2 and Windows Server 2012. This release now supports Windows Server 2012 R2 and Windows Server 2012. For more information, see the System Requirements.
Option to change the default Module Builder string. With this release, you can modify the default KS Category name in Module Builder Editor while generating a module.
This release of Module Builder Editor replaces all Previous Releases.
For the most recently updated list of supported application versions, see the AppManager Supported Products page.
Module Builder Editor has the following system requirements:
|
Software/Hardware |
Version |
|---|---|
|
NetIQ AppManager installed on the AppManager repository (QDB) computers, on the Windows agent computers you want to monitor, and on all console computers |
7.0 or later Support for Windows Server 2008 on AppManager 7.x requires AppManager Windows Agent hotfix 71704 or later. For more information, see the AppManager Suite Hotfixes page. |
|
Microsoft Windows operating system on the agent computers |
One of the following:
|
|
Microsoft .NET Framework on agent computers
|
2.0.50727, at minimum |
|
Adobe Reader |
4.0 or later The Module Builder Editor user generates a PDF file at the end of the module-generation process. Acrobat Reader is required to read this PDF file. |
NOTE:Microsoft .NET Framework 3.5 (includes .NET 2.0 and 3.0) features are not enabled by default on Windows Server 2012 and 2012 R2. Before installing Module Builder Editor on Windows Server 2012 or 2012 R2, ensure that Microsoft .NET Framework 3.5 is enabled. For more information on how to enable Microsoft .NET Framework 3.5, see the Microsoft article.
For more information on hardware requirements and supported operating systems and browsers, see the Module Builder Management Guide, included in the download package.
The download package for the Module Builder Editor includes the application setup program, ModuleBuilderEditor-1.1.60.0.msi, this Readme, a user guide for AppManager users and subject matter experts, and context-sensitive Help for the Module Builder Editor user interface.
To install Module Builder Editor, do as follows:
Navigate to the download folder and double-click the ModuleBuilderEditor-1.1.60.0-Setup.exe file.
In the \Program Files\NetIQ\Module Builder\Editor folder, double-click the ModuleBuilderEditor-1.1.xxx.0.msi file.
By default, the Module Builder Editor files are installed in the following location: \Program Files\NetIQ\Module Builder\Editor. If any installation problems occur, a installation log file will be available in the \Windows\Temp folder.
Launch Module Builder Editor by clicking Start > Programs > NetIQ > Module Builder > Module Builder Editor. Module Builder Editor requires that the logged-in user be a member of the local Administrators group.
NOTE: If you are using Windows Vista or Windows Server 2008, you must run Module Builder Editor as Administrator. Right-click the Module Builder Editor shortcut in the NetIQ/Module Builder programs menu folder and select Run as administrator. If you are already logged in as the administrator, you will not have the Run as administrator option.
For more information about installing this module, see the NetIQ Module Builder Management Guide, included in the download package.
You can use the Add or Remove Programs or Programs and Features option from the Control Panel to uninstall this application.
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.
The Module Builder Editor creates an uninstallation log only on systems running Windows Installer 4.x. On systems running a version of Windows Installer less than 4.x, the Module Builder Editor does not create an uninstallation log. (DOC275155)
If you run application discovery a second time, the list of automatically discovered Windows components changes. If you run the discovery process a second time, and then select No on the Clear Auto-Discovered Properties dialog box, the previously auto-discovered items remain selected, but they will not be labeled as auto-discovered. On the Discovery Results dialog box, the Module Builder Editor only lists new components that it discovered automatically, based on the current criteria, so the previously auto-discovered items will not show up in the new auto-discovered lists. (ENG270339)
The maximum length for an application name in the Module Builder Editor is 93 characters. When identifying the application you want to monitor in the Module Builder Editor, you cannot use an application name longer that 93 characters in length. (ENG272575)
Module Builder cannot monitor components with names longer than 128 characters. If you attempt to select a component for monitoring, such as a log file, and that component has a file name (not including the path) of more than 128 characters, the log file will be truncated in the TreeView of AppManager. As a result, Module Builder cannot properly monitor the component you selected in the Module Builder Editor. (DOC264488)
An error message displays while you are adding a process or log file to monitor. If a process or log file cannot be accessed, or if access is denied, the Module Builder Editor displays an error message for each object that cannot be accessed. You might see this message multiple times if there are several directories in the application folder that the Module Builder Editor cannot access. (DOC271867)
When selecting a process with more than one instance, the Module Builder Editor chooses the first instance it encounters. When you select a process, if that process has multiple instances running, the Module Builder Editor does not give you the ability to select which instance to use in the charts. The Module Builder Editor simply chooses the first instance it finds. The Module Builder Editor also chooses the first instance of a process when it automatically selects a process using the application setup discovery. (DOC271865)
The Module Builder Editor cannot collect data on a process with a file name that is longer than 64 characters. (DOC272158)
Cannot specify None for the Event Type when defining an event to monitor. When defining event log events on the Event to Monitor window, selecting an Event Type value of None does not produce matches, even if you have event log entries that contain an Event Type of None. (DOC275940)
For a wildcard log file, Module Builder Editor only stores the last viewed log file in the Log File Preview. If you use the wildcard option to select multiple log files for monitoring, you will only see the most recent log file in the Log File Preview text area on the Identify Log File Details to Monitor page. If you are viewing wildcard log files in AppManager Expert mode, the log file that displays in the preview is not the selected file, but the last log file viewed by the subject matter expert. (DOC273483)
Some installed applications may not display in Select Application from List dialog. Due to the way some applications handle their installation and uninstallation processes, those applications may not display in this list. If the application you want to manage is not in the list, you must define the name and path manually. (ENG262479)
The Module Builder Editor does not show the Windows Session Manager process as running. When adding the Windows Session Manager (smss.exe) process to the Processes plug-in, Module Builder Editor reports the process as not running. To monitor the Windows Session Manager process, use the Performance Counters plug-in, the Process category, and the corresponding PerformanceMetrics Knowledge Script. (ENG288128)
Error messages display when the name of a monitored service is more than 80 characters. The Module Builder Editor displays a message stating that a service no longer exists if the service name is greater than 80 characters. This situation only applies to the service name, not the service display name. You can dismiss the error messages and still manually add the service to monitor. (DOC272155)
When you are specifying the actions to take on a service, you cannot set the severity level for the success or failure of these actions in the Module Builder Editor. The corresponding success or failure severities can only be updated in the AppManager Knowledge Script after the script has been checked into your AppManager Repository. You can view the corresponding severity information for the actions in the application monitoring contract PDF document. (DOC270751)
The Module Builder Editor does not recognize performance counters that were enabled after the Module Builder Editor was started. If you added or enabled new performance counters while the Module Builder Editor was running, the Module Builder Editor will not recognize these counters until you close and then open the Module Builder Editor again. (DOC270747)
For Windows Vista and Windows Server 2008 computers, the Module Builder Editor requires that the Event Log Source Name be specified using the full source name or by using a regular expression. The source name that appears in the Windows Event Viewer may only contain a shortened version of the full source name. When adding an event using the Existing Events tab in the Module Builder Editor, the source name appears in the full format. However, when editing an event or adding an event using the Ad-hoc Events tab, you must specify the Source value in this full format or use a Regular Expression when using this event property. To find the Source value from a Windows Vista or Windows Server 2008 Event Viewer, select the Event, click the Details tab, and in the Friendly View, click System > Provider > [Name]. (DOC273767)
Excessive icons in .mob file may cause Editor to fail. Module Builder Editor may fail when attempting to load a saved .mob file that contains a high number of icons for processes or applications. Module Builder Editor cannot display the icons if the number of icons exceeds the Microsoft Windows limit for GDI (Graphics Device Interface) Objects. You can prevent Module Builder Editor from saving and loading these icons by adding a "LoadAndSaveIcons" key to the MoBEditor.exe.config file. For more information, see the "Configuring Settings for the Module Builder Editor" topic in the "Installing Module Builder" chapter of the Module Builder User Guide, included in the download package. (ENG287195)
This release of Module Builder Editor includes enhancements added in previous releases.
This release resolved the following issue:
The Module Builder Editor does not recognize performance counters used by some 64-bit systems. In previous releases, the Module Builder Editor could not read some native 64-bit performance counters if they were not also implemented with parallel 32-bit versions. With this release, the Module Builder Editor can read all 32-bit and 64-bit performance counters, including native 64-bit-only performance counters. (ENG301998)
This release included the following enhancements:
Support for Windows 7 and Windows Server 2008 R2. With this release, NetIQ Module Builder Editor can be installed on agent computers running Microsoft Windows Server 2008 R2 or Microsoft Windows 7. (ENG283482)
In addition, this release resolved the following issue:
Some graphics are not displayed when reopening a .mob file. This release resolves an issue in which the following error message is displayed when a .mob file is reopened: The system cannot find the file specified. The error occurs when the number of icons for log files associated with .mob file exceeds the Microsoft Windows limit for GDI (Graphics Device Interface) Objects. With this release, the Module Builder Editor does not load icons for non-executable (.exe) files from the .mob file. In addition, icons for log files are not collected or stored, so future .mob files will not contain unnecessary icons. (ENG287195)
This release resolved the following issue:
Deselection feature of the Module Builder Editor does not work when multiple event descriptions selected. Before you install this release, it is not possible to select multiple event descriptions and then deselect associated items. For example, if you select multiple event descriptions, you cannot deselect the associated Description Contains check box for the selected event descriptions. After you install this release, a code change allows you to select multiple event descriptions and also deselect associated items as needed. (ENG279745)
This release included the following features:
An easy-to-use editor interface that allows subject matter experts to quickly define application metrics and management information that an AppManager expert can use to create AppManager monitoring packages. In the Module Builder Editor, a subject matter expert answers a series of questions and defines parameters that an AppManager expert can use to generate a set of customized Knowledge Scripts for AppManager.
The ability for the AppManager expert to provide simple application health monitoring from the perspective of the subject matter expert. The subject matter expert used the Module Builder Editor to specify the Windows processes, services, performance counters, event log events, and log files for the monitored application that the subject matter expert wants to monitor. No prior knowledge of AppManager or monitoring is required for the subject matter expert.
The subject matter’s knowledge and information, once passed to the AppManager expert, results in a set of customized Knowledge Scripts. After defining the application with the Module Builder Editor, the subject matter expert shares the Module Builder Editor file with the AppManager expert. The AppManager expert reviews the subject matter's settings, revises the settings as needed, and generates a set of AppManager Knowledge Scripts, including a Discovery Knowledge Script, that represents the subject matter's application. The AppManager expert runs the customized scripts on a set of computers to track performance, health, and other data relevant to keeping the application functional.
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.
For information about NetIQ legal notices, disclaimers, warranties, export and other use restrictions, U.S.Government restricted rights, patent policy, and FIPS compliance, see https:/www.netiq.com/company/legal/.
Copyright © 2015 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/. All third-party trademarks are the property of their respective owners.