2.4.2 Setting the definition files
To convert NNMi incidents into JP1 events and then use JP1/IM to manage and monitor them, you must set the definition files listed in the following table.
Note the following points about the environment variables settings.
-
When LC_ALL is not specified, the settings of LC_MESSAGES, LANG, and LC_CTYPE# must be the same.
-
When LC_ALL and LC_MESSAGES are not specified, the settings of LANG and LC_CTYPE# must be the same.
- #
-
The settings of LC_CTYPE are optional.
Table 2‒5: Definition files to be set Definition file name
Description
NNMi incident forwarding filter definition file
This file defines conditions for converting NNMi incidents acquired from NNMi into JP1 events.
Mapping definition file
This file defines mapping for displaying category and family labels (which are attributes of NNMi incidents) on the Event Details window of JP1/IM - View.
JP1/IM - Manager definition files
The following two definition files are used by JP1/IM - Manager:
- Definition file for extended event attributes
-
This definition file is used to display the extended attributes specific to JP1/IM - EG for NNMi in the Event Details window of JP1/IM - View.
- Definition file for opening monitor windows
-
This definition file is used to open NNMi windows from the Event Console window of JP1/IM - View.
Create the NNMi incident forwarding filter definition file and the mapping definition file by copying the sample files provided by JP1/IM - EG for NNMi.
The JP1/IM - Manager definition files are included in JP1/IM - Manager. Normally, there is no need to edit the included definition files. Edit these definition files only when it is necessary to add attributes to be displayed in the Event Details window of JP1/IM - View or change the Web browser to open NNMi windows.
For details about the settings in each definition file, see 4. Converting NNMi Incidents into JP1 Events.