You can install more than one connector for failover purposes. If the primary connector becomes
Error Logging Level This refers to the logging of the connector service. Select the drop-down list to set the level for logging the connector service. The error logs are created in \Program Files\NetIQ\temp\NetIQ_debug\<name of machine>\AMNC.log.
Enable/Disable Logging Select this option to choose Error Logging type or no logging.
Max Log Size (MB) Select this option to set a limit to the log file size. When the log reaches the specified limit, it is copied to a backup file (replacing the previous one) so that the disk space used is twice the Max Log Size. If Max Log Size is set to zero, there is no limit on the file size.
Field Description
Field Description
Interactive User (Use only for Debug Testing)
This mode is for use by NetIQ Technical Support only.
NOTE: The connector service should be stopped before running in debug mode.
This User (Enter a Valid User Account to run the Server under)
The connector application runs as a Windows service that runs a COM server (the AMNCServer process). Enter an account (user name and password) for the AMNCServer process.
NOTE: Repeat the process if there are more than two connectors.
One connector will be designated as the primary one where you can configure the following parameters:
AM Event ID field (if used)
AM Event Source field (if used)
Restart Period
Netcool Save Details
A secondary connector does not allow you to change these values.
4
4Working with AppManager Events
This chapter describes how to use IBM Tivoli Netcool and AppManager to manage AppManager events generated in your organization.
4.1 Working with Events
After you install the connector, you can view event status from either the AppManager console or the Netcool Event List.
For more information on managing events from the AppManager console, see the Administrator Guide for AppManager.
The connector formats an AppManager event into a Netcool alert, providing administrators with detailed troubleshooting information.
To view and acknowledge the alert details:
1 Double‐click a Netcool alert in the Alert Status dialog box.
2 On the Alert Details tab, right‐click the alert in the Netcool Event List and select Acknowledge.
The connector forwards the event status to the AppManager console. For more information on using the Netcool Event List, see the Netcool/OMNIbus User Guide.
4.2 Working with Event Collapsing
When you enable event collapsing in AppManager, AppManager forwards duplicate events as a single event to Netcool. Netcool displays each subsequent occurrence as a single occurrence of the same event. The subsequent events have the same identification number as the original event and are displayed with time‐stamps of their occurrences.
Whenever the parent event in AppManager generates a child event, the event displays as New in the Netcool console.
AppManager events, by default, are displayed in an ascending order (parent event, followed by child events that display the most recent event first). Depending on your configuration, Netcool alerts display corresponding child events in descending order, beginning with older child events followed by newer child events.
You can also set other options in AppManager, which then affect how events are displayed in Netcool. For example, you can set AppManager to automatically close events if an event condition does not exist.
For more information on event collapsing and automatically closing events, see the Administrator Guide for AppManager.
4.3 Troubleshooting
If new or updated AppManager events are not showing up as alerts in the Netcool console, then data is not flowing from AppManager to Netcool. Take the following steps to rectify the problem:
Ensure AMNCServer.exe is running. This program enables the flow of data from AppManager to Netcool.
If AMNCServer.exe is not running, restart the NetIQ AM/IBM Tivoli Netcool Connector Service (amncservice.exe), which will restart AMNCServer.exe and resume the flow of data.
If AMNCServer.exe is running, check AMNC.log to verify the time of the last log entry. If no entries have been written to the log in a while, then the AMNCServer.exe process may be hung or locked up. Stop AMNCServer.exe and restart AMNCService.exe. AMNCServer.exe will start as well and begin processing AppManager events that are to be sent to Netcool.
If the AppManager console does not reflect updated event statuses from actions occurring in Netcool, then data is not flowing from Netcool to AppManager. Take the following steps to rectify the problem.
Ensure the SNMP Trap Service, snmptrap.exe, is running. This Windows service enables AppManager to receive traps. Start the service if it is not running.
Ensure SNMPTrapReceiverFromNC.exe is running.
If SNMPTrapReceiverFromNC.exe is not running, restart the NetIQ Trap Receiver service, AMNCTrapRecv.exe, which will, in turn, start SNMPTrapReceverFromNC.exe.
If SNMPTrapReceiverFromNC.exe is running, check SnmpTrapHandler.log for log entries. If initialization was successful and SNMPTrapReceiverFromNC.exe is running, but no updates have been written to the log in a while, then trap updates are not being received from Netcool.
Ensure snmptrap.exe is running.
If snmptrap.exe and SNMPTrapReceiverFromNC.exe are running and log entries are being recorded, restart Netcool.