AppManager Connector for IBM Tivoli Netcool/OMNIbus formats AppManager events into Netcool alerts so you can monitor the alerts by using Netcool. An AppManager event is a notification about a condition or activity you are monitoring that occurs on a managed client.
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 of AppManager Connector for IBM Tivoli Netcool/OMNIbus provides the following enhancements:
Support for Microsoft SQL Server 2016 (64-bit): This release now supports Microsoft SQL Server 2016 (64-bit) on the Connector database computer.
Support for Windows Server 2016 (64-bit): This release now supports Windows Server 2016 (64-bit) operating systems on the Connector computer.
This release of AppManager Connector for IBM Tivoli Netcool/OMNIbus replaces all Previous Releases.
For the most recently updated list of supported application versions, see the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.
AppManager Connector for IBM Tivoli Netcool/OMNIbus has the following system requirements:
|
Software/Hardware |
Version |
|---|---|
|
NetIQ AppManager |
8.0.3, 8.2, 9.1, 9.2, 9.5, or later |
|
Microsoft Windows operating system on the Connector computers |
One of the following:
|
|
Microsoft SQL Server on the Connector database computer |
One of the following:
|
|
IBM Tivoli Netcool/OMNIbus |
8.1, 7.4, 7.3.1, 7.3.0, 7.2.1, 7.2.0, or 7.1 |
|
IBM Tivoli Netcool MTTRAPD Probe |
7.0.1857, 11.0.0, 12.0.0, or later |
|
IBM Tivoli Netcool SNMP Gateway Server |
1.6.0.0, 1.5.1.0, or 0.0.1395 |
|
MDAC on the Connector computer |
2.6 or later |
Although the connector is supported only on Windows servers, it can communicate with Netcool/OMNIbus installed on one of the following UNIX workstations:
Sun SPARCstation or UltraSPARC with Solaris 11 (64-bit)
Sun SPARCstation or UltraSPARC with Solaris 10 (32-bit and 64-bit)
Sun SPARCstation or UltraSPARC with Solaris 9 (32-bit and 64-bit)
Sun SPARCstation or UltraSPARC with Solaris 8 (32-bit and 64-bit)
HP-9000 Series with HP-UX 11.i (v2 and v3)
Red Hat Enterprise Linux 6 and 7 (64-bit)
Red Hat Linux 5.2, 5.0 (32-bit and 64-bit)
For more information on hardware requirements and supported operating systems and browsers, see the AppManager Connector for IBM Tivoli Netcool/OMNIbus Management Guide, included in the download package.
Run the setup program only once on any computer. The AM2NetcoolInstall.log file lists changes and problems encountered during the installation. By default, this file is located in the NetIQ temp folder.
IMPORTANT:If you are upgrading from a previous release, reinstall all Netcool components, including the connector database on the computer where the Netcool Connector is already installed. When you run AM_Netcool_Setup.exe on the computer where you want to install the connector, you must select Create Connector Database in the Select Features dialog box.
For more information about installing this module, see the AppManager Connector for IBM Tivoli Netcool/OMNIbus Management Guide, included in the download package.
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.
Multiple Netcool connectors should not point to the same connector database. Setting up multiple Netcool connectors to use the same connector database is not supported unless you are using a second Netcool connector as a backup for the first connector. Using the same connector database for different Netcool connectors that gather data from different AppManager repositories could result in the loss of information on events with the same event ID that came from different AppManager repositories. To monitor events from different AppManager repositories, set up each AppManager repository with a different connector and connector database. (ENG319601)
Updates made to AppManager events that are not available in the connector database might not get synchronized. Any event that is older than the number of days specified in the Check unchanged events older than X [days] option on the Advanced Settings (2) tab of the connector Configuration Utility is removed from the connector database, even if the event has been properly mapped into Netcool and is listed in the AppManager repository. Consequently, updates made to such events might not get synchronized. (ENG314937)
This release of AppManager Connector for IBM Tivoli Netcool/OMNIbus includes enhancements added in previous releases.
This release of AppManager Connector for IBM Tivoli Netcool/OMNIbus provides the following enhancements:
Support for IBM Tivoli Netcool/OMNIbus 8.1 and 7.4. This release supports IBM Tivoli Netcool/OMNIbus version 8.1 and 7.4. For more information, see the System Requirements.
Support for Windows Server 2012 R2 and 2012. This release supports Windows Server 2012 R2 and Windows Server 2012. For more information, see the System Requirements.
Support for SQL Server 2014 and SQL Server 2012 R2. This release supports SQL Server 2014 and SQL Server 2012 R2. For more information, see the System Requirements.
Improvement in the performance of the connector. With this release, the connector takes significantly less amount of time to forward the events from AppManager to Netcool.
This release of AppManager Connector for IBM Tivoli Netcool/OMNIbus resolves the following issue:
Connector fails to upgrade on a hard drive other than the C: drive. This release resolves an issue in which AppManager Connector for IBM Tivoli Netcool/OMNIbus failed to upgrade if the connector was installed on a hard drive other than the C: drive. With this release, the connector can be upgraded on any hard drive in which the previous version of the connector is installed. (ENG325206)
This release provided the following enhancement:
Support for a user-specified name for the connector database. This release allows you to specify the name of the connector database instead of using the default database name of AMNC as in previous releases. The ability to give each of your connector databases a unique name allows you to host multiple connector databases on a single SQL Server, instead of hosting each AMNC database on a separate SQL Server as in previous releases. (ENG317060)
This release provided the following enhancements:
Support for recent versions of IBM Tivoli Netcool/OMNIbus. This release now supports IBM Tivoli Netcool/OMNIbus version 7.3.1, 7.3.0, 7.2.1, and 7.2.0.
Support for Windows Server 2008 R2. This release now supports Windows Server 2008 R2 operating systems on the Connector computer.
Support for SQL Server 2008 R2 and SQL Server 2008. This release now supports SQL Server 2008 R2 (32-bit and 64-bit) and SQL Server 2008 (32-bit and 64-bit) on the Connector database computer.
Support for communicating with Sun SPARCstation or UltraSPARC with Solaris 10 and Red Hat Linux 5.0 and 5.2. Although the connector is supported only on Windows servers, it can now communicate with Netcool/OMNIbus installed on one of the following UNIX workstations:
Sun SPARCstation or UltraSPARC with Solaris 10 (32-bit and 64-bit)
Red Hat Linux 5.2 and 5.0 (32-bit and 64-bit)
Support for IBM Tivoli Netcool MTTRAPD Probe version 12.0.0 and 11.0.0.
Support for IBM Tivoli Netcool SNMP Gateway Server version 1.6.0.0 and 1.5.1.0.
This release resolved the following issues:
In the Netcool Event List, the Netcool Connector does not correctly display the server name from which the events were generated. This release resolves an issue in which the Netcool Connector displayed the name of the proxy server instead of the server from which the events were actually generated. With this release, the Netcool Connector correctly displays the name of the server from which the events were generated. (ENG248041)
The installation of the Netcool Connector might fail on a system that has short file name creation disabled. This release resolves an issue in which the Netcool Connector installation might have failed on a system that has short file name creation disabled. With this release, the Netcool Connector is successfully installed on a system irrespective of whether the short file name creation is enabled or disabled on the system. (ENG276571)
The Netcool Connector Configuration Utility sometimes fail to save the value for the disable synchronization setting. This release resolves an issue in which the Netcool Connector Configuration Utility sometimes failed to save the value specified for the Disable Synchronization of AppManager with Netcool setting that is available on the Advanced Settings (1) tab. With this release, the Netcool Connector Configuration Utility properly saves the value of the disable synchronization setting. (ENG266081)
This release resolved the following issue:
Unable to change the community string for traps being sent. This release resolved an issue in which the connector did not allow you to edit the community string for the outgoing traps. With this release, you can change the community string for outgoing traps, but you must enter at least one character for the string, or the utility defaults to public as the community string. (ENG301255)
This release resolved the following issues:
Connector does not forward Chinese characters. Before you install this release, AppManager Connector for IBM Tivoli Netcool/OMNIbus does not forward messages that include Chinese characters. After you install this release, a change in the connector's code allows it to recognize and forward messages including Chinese characters to the Netcool console. (ENG266666)
Packet loss prohibits forwarding of events to Netcool. Before you install this release, large SNMP traps experience packet loss when multiple, fragmented packets contain UDP datagrams and if no ARP cache is present. The packet loss prevents the connector from forwarding these traps to the Netcool console. After you install this release, the connector checks the size of the SNMP trap and creates an ARP cache if the trap is large enough to be fragmented and if the trap destination is on the same subnet as the trap source. (ENG269988)
This release resolved the following issue:
Some event details are not available in collapsed events. Before you install this release, event details such as AMCategoryName are not available in the child events of collapsed events. The details are available in the parent event. This problem applies only to events raised by Knowledge Script Group jobs. After you install this release, event detail fields in child events are correctly populated. (ENG265097)
This release resolved the following issues:
The Netcool connector no longer forwards every event from the repository when you start with a new AppManager Netcool database. Before you install this release, when you start with a new AppManager Netcool database after a new release or hotfix, the connector forwards to AppManager every event from the past that is in the repository. After you install this release, you can use the configuration utility to enter the event ID of the last event that was forwarded out of the repository, and the connector will start from the next event ID and not forward any events before that event. You set this option on the Advanced Settings (1) tab of the configuration utility. (ENG254784)
Updates were made to the SNMP varbind values since the previous release and previous hotfixes. The connector name, its version, and the AppManager parent event ID are now part of the connector's SNMP traps. You must use the new mttrapd.rules file installed in the AMNC\redist folder on the connector, or you should modify your custom rules.
The name of the connector and its version number are now the first two varbinds in SNMP traps sent by this connector, and the AppManager parent event ID for the event is varbind 28. With the inclusion of the connector's version as the second varbind value, you can now differentiate traps coming from particular versions of the connector and understand whether the trap contains the parent event ID and other information that has been added or modified over prior releases.
In prior versions of the connector, the flag indicating whether detailed information will be stored in the alert occupied the first varbind and the name of the AppManager repository database the connector is forwarding events from occupied the second varbind. After you install this release, the name of the connector now occupies the first varbind, and the version of the connector occupies the second varbind, and all previous varbinds are now two positions higher. (ENG254663, ENG254975)
NOTE:The NetIQ AppManager Connector for IBM Tivoli Netcool/OMNIbus Management Guide was updated to include the current list of varbinds (See 'Working with Connector Elements and Fields').
This release resolved the following issues:
New option to close or acknowledge parent events. This release adds an option in the NetIQ AppManager for IBM Tivoli Netcool Configuration Utility that allows you to select whether the connector should close or acknowledge parent events in AppManager. (ENG251312)
New option to enable FQDN of alert sources in Netcool alerts. The Configuration Utility gives you the option of having the connector use a fully qualified domain name (FQDN) for event computer names in Netcool alerts. Previously, you needed to manually create a registry key to use FQDN for computer names. (ENG253382)
Connector stops forwarding events. Before you install this release, the connector could crash when trying to forward a large number of events in a small amount of time. After you install this release, the connector will continue forwarding events in these situations while minimizing as much delay as possible. (ENG250146, ENG249945)
Long event messages cause the connector to stop functioning. Before you install this release, large event messages cause an error in the connector, preventing it from forwarding the event on to Netcool. After you install this release, the connector can handle large amounts of data in the detailed event message. (ENG252106)
This release resolved the following issues:
Resolves issue with collapsed events. With this release, the connector sends a single SNMP trap from the AppManager repository to Netcool with the exact count of collapsed events. In previous releases, the connector sent each collapsed event as a separate SNMP trap to Netcool. (ENG245700)
Resolves issue with recognizing AMNCServer.exe. With this release, on restart, the NetIQ AppManager/IBM Tivoli Netcool Connector service monitors the running instance of the AMNCServer.exe. In previous releases, on restart, the NetIQ AppManager/IBM Tivoli Netcool Connector service failed to recognize the running instance of AMNCServer.exe. (ENG245702)
Resolves issue with restarting services. With this release, the connector restarts the NetIQ AppManager/IBM Tivoli Netcool Connector service and the NetIQ AppManager/IBM Tivoli Netcool Trap Receiver service if the services stop. The Restart the Service option from the Subsequent Failures list in the Recovery tab of the Services properties dialog box is enabled. In previous releases, the connector failed to start these services if they stopped. (ENG245704)
Resolves issue with dependency on SNMP Trap Service. With this release, the NetIQ AppManager/IBM Tivoli Netcool Trap Receiver service is dependent on the SNMP Trap Service to enable synchronization between AppManager and Netcool. In previous releases, NetIQ AppManager/IBM Tivoli Netcool Trap Receiver service was not dependent on the SNMP Trap Service. (ENG245705)
Resolves issue with uninstallation. With this release, uninstallation of the connector removes all DCOM components for AMNCServer.exe from the Registry. In previous releases, uninstalling the connector did not remove all DCOM information from the Registry, which caused problems during the installation of a newer version of the connector. (ENG246046)
Resolves issue with FQDNs in alerts. With this release, alerts in the Netcool console can provide the hostname of the agent computer as it appears in the AppManager Operator Console TreeView pane, rather than the fully qualified domain name (FQDN). In previous releases, alerts used only the FQDN. TreeView objects that are defined by IP addresses will always display their FQDN or NetBIOS name in Netcool. To provide the hostname as it appears in the AppManager Operator Console, open the Registry Editor, navigate to HKEY_LOCAL_MACHINE\Software\NetIQ\AMNC\Config, create a new DWORD value labeled UseFQDNForMachineName, and set the Value data field to 0.
Resolves issue with unresolved domain names. With this release, unresolved domain names no longer cause incorrect information to be populated in the SNMP trap varbind list. In previous releases, if the connector was unable to resolve the domain name for a given server, it would populate alert fields in the varbind list with incorrect data. (ENG246407)
Resolves issue with NULL fields in alerts. With this release, alerts containing NULL event count fields are not forwarded to the Netcool console. In previous releases, alerts whose event count equaled 0 (zero) were forwarded to Netcool. (ENG246746)
Resolves issue with crash of AMNCServer.exe. With this release, simultaneous polling of shared resources no longer causes AMNCServer.exe to stop unexpectedly. In previous releases, AMNCServer.exe stopped abruptly when different polling threads queried the connector database at the same time. (ENG246834)
This release resolved the following issues:
Connector failed to forward AppManager events to IBM Tivoli Netcool/OMNIbus. This issue occurred when the connector garbled the name of the agent computer after receiving the event from AppManager. (ENG241645)
Connector failed to forward any new AppManager event to IBM Tivoli Netcool/OMNIbus. The connector failed to forward a new event when the description of a short event message was null. The connector failed to synchronize AppManager events and IBM Tivoli Netcool/OMNIbus alerts. (ENG241786)
This release updated the following files:
AMNCServer.exe
SnmpTrapReceiverFromNC.exe
SnmpTrapSenderToNC.dll
This hotfix also added a Windows service, AMNCTrapRecv.exe. This service allows you to monitor the status of the SNMP Trap Receiver.
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 (C) 2019 NetIQ Corporation. All rights reserved.
For information about NetIQ trademarks, see https://www.netiq.com/company/legal/. All third-party trademarks are the property of their respective owners.