8.2 JP1 events obtained by converting NNMi incidents

When NNMi incidents are converted into JP1 events, the attributes of the NNMi incidents are mapped into JP1 event attributes. Two types of attributes are mapped:

Attributes that are mapped by default
Additional attributes that are mapped according to settings in the NNMi incident forwarding filter definition file

The following table lists and describes the attributes of JP1 events that are obtained by converting NNMi incidents.

Table 8‒1: Attributes of JP1 events obtained by converting NNMi incidents
Attribute type		Item	Attribute name	Description	Size	Mapping
Basic attribute		Event ID	None	Value indicating the event or the program of the application that issued the JP1 event. In NNMi: `0x00006100`	--	D
Basic attribute		Message	None	Character string describing the details of the event. By default, the message in the NNMi incident is set. The NNMi incident forwarding filter definition file can be used to set mapping.	--	D
Extended attribute	Common information	Event level	`SEVERITY`	JP1 event severity obtained by converting the severity of the NNMi incident. The NNMi incident forwarding filter definition file can be used to set mapping.	5-11 bytes	D
		Product name	`PRODUCT_NAME`	Name of the program that issued the JP event. In NNMi: `/HITACHI/JP1/IM/NNMI_INCIDENT`	29 bytes	D
		Object type	`OBJECT_TYPE`	Name indicating the type of object that resulted in issuance of the event. In NNMi: `NNMI_INCIDENT`	13 bytes	D
		Object name	`OBJECT_NAME`	Name of the object that resulted in issuance of the event (such as a job or a jobnet). In NNMi: Name set by NNMi (`NNMI_NAME`)	1-64 characters	D
		Root object type	`ROOT_OBJECT_TYPE`	Type of object. In NNMi: `NNMI_INCIDENT`	13 bytes	D
		Root object name	`ROOT_OBJECT_NAME`	Name used to issue an execution instruction during a user operation. In NNMi: Name set by NNMi (`NNMI_NAME`)	1-64 characters	D
		Occurrence	`OCCURRENCE`	Event that occurred on the object indicated by its object name. In NNMi: `RECEIVE`	7 bytes	D
	Program- specific information	Result of Mapping	`NNMI_EM_RESULT`	Execution result of mapping processing on added extended attributes. For details, see 4.1.3(3)(b) Checking the result of extended attribute mapping.	1-19 bytes	D^#1
		Incident UUID	`NNMI_UUID`	UUID of the NNMi incident	1-36 characters	D^#1
		Source Name	`NNMI_SRC_NAME`	Source name of the NNMi incident	1-255 characters	A
		Source Type	`NNMI_SRC_TYPE`	Source type of the NNMi incident	1-50 characters	A
		Source Node	`NNMI_SRC_NODE_NAME`	Source node of the NNMi incident	1-255 characters	D
		Name	`NNMI_NAME`	Name of the NNMi incident	1-64 characters	D
		Severity of NNMi incident	`NNMI_SEVERITY`	Severity of the NNMi incident	1-255 characters	D
		Priority	`NNMI_PRIORITY`	Priority of the NNMi incident	1-255 characters	A
		Lifecycle State	`NNMI_LIFECYCLE_STATE`	Lifecycle state of the NNMi incident	1-255 characters	A
		Assigned To	`NNMI_ASSIGNED_TO`	NNMi incident assignment target	1-255 characters	A
		Category	`NNMI_CATEGORY`	Category of the NNMi incident	1-255 characters	A
		Family	`NNMI_FAMILY`	Family of the NNMi incident	1-255 characters	A
		Origin	`NNMI_ORIGIN`	Origin of the NNMi incident	1-255 characters	A
		Correlation Nature	`NNMI_NATURE`	Correlation nature of the NNMi incident	1-255 characters	A
		Duplicate Count	`NNMI_DUPLICATE_COUNT`	Duplicate count of the NNMi incident	1-10 bytes	A
		Message	`NNMI_FORMATTED_MESSAGE`	Message in the NNMi incident	1-1,024 characters	D
		Notes	`NNMI_NOTES`	Notes in the NNMi incident	1-256 characters	A^#5
		RCA Active	`NNMI_RCA_ACTIVE`	RCA active of the NNMi incident	4-5 characters	A
		Origin Occurrence Time	`NNMI_ORIGIN_OCCUR_TIME`	Occurrence time at the origin of the NNMi incident^#2	1-17 bytes	D
		Origin Occurrence Time (ms)	`NNMI_ORIGIN_OCCUR_TIME_MS`	Occurrence time at the origin of the NNMi incident (milliseconds)^#3	1-19 bytes	A
		First Occurrence Time	`NNMI_FIRST_OCCUR_TIME`	Occurrence time of the first NNMi incident^#2	1-17 bytes	A
		First Occurrence Time (ms)	`NNMI_FIRST_OCCUR_TIME_MS`	Occurrence time of the first NNMi incident (milliseconds)^#3	1-19 bytes	A
		Last Occurrence Time	`NNMI_LAST_OCCUR_TIME`	Occurrence time of the last NNMi incident^#2	1-17 bytes	A
		Last Occurrence Time (ms)	`NNMI_LAST_OCCUR_TIME_MS`	Occurrence time of the last NNMi incident (milliseconds)^#3	1-19 bytes	A
		Created	`NNMI_CREATED`	Date and time the NNMi incident was created^#2	1-17 bytes	A
		Created (ms)	`NNMI_CREATED_MS`	Date and time the NNMi incident was created (milliseconds)^#3	1-19 bytes	A
		Last Update Time	`NNMI_MODIFIED`	Last date and time the NNMi incident acquisition time was updated^#2	1-17 bytes	A
		Last Update Time (ms)	`NNMI_MODIFIED_MS`	Last date and time the NNMi incident acquisition time was updated (milliseconds)^#3	1-19 bytes	A
		Severity Unique Key	`NNMI_SEVERITY_UK`	Unique key of the NNMi incident severity	5-8 bytes	D^#1
		Priority Unique Key	`NNMI_PRIORITY_UK`	Unique key of the NNMi incident priority	1-80 characters	A^#1
		Lifecycle State Unique Key	`NNMI_LIFECYCLE_STATE_UK`	Unique key of the NNMi incident lifecycle state	1-80 characters	A^#1
		Category Unique Key	`NNMI_CATEGORY_UK`	Unique key of the NNMi incident category	1-80 characters	A^#1
		Family Unique Key	`NNMI_FAMILY_UK`	Unique key of the NNMi incident family	1-80 characters	A^#1
		Origin Unique Key	`NNMI_ORIGIN_UK`	Unique key of the NNMi incident origin	5-18 bytes	A^#1
		Correlation Nature Unique Key	`NNMI_NATURE_UK`	Unique key of the NNMi incident correlation nature	4-18 bytes	A^#1
		Number of Custom Attributes	`NNMI_CIA_NUM`	Number of custom attributes of the NNMi incident	1-10 bytes	A
		Custom Attribute Name	`NNMI_CIA_NAME_$n`	Name of a custom attribute of the NNMi incident. `$n` indicates the index of the custom attribute.^#4	1-80 characters	A
		Custom Attribute Type	`NNMI_CIA_TYPE_$n`	Type of the custom attribute of the NNMi incident. `$n` indicates the index of the custom attribute.^#4	6-15 bytes	A
		Custom Attribute Value	`NNMI_CIA_VALUE_$n`	Value of the custom attribute of the NNMi incident. `$n` indicates the index of the custom attribute.^#4	1-2,000 characters	A
		NNMi connection protocol	`NNMI_PROTOCOL`	Protocol used to connect to NNMi	4-5 bytes	D^#⁶
		NNMi server name	`NNMI_SERVER`	Host name of the connection-target NNMi	1-255 bytes	D^#1
		NNMi port number	`NNMI_PORT`	Port number of the connection-target NNMi	1-5 bytes	D^#1

Legend:

--: There is no need to take this size into consideration.

D: Attribute mapped by default

A: Additional attribute that is mapped when it is defined in the NNMi incident forwarding filter definition file

#1

This is an internal attribute of NNMi incidents. If the version of JP1/IM - Manager is 11-10 or earlier, the default is that they are not displayed in the Event Details window of JP1/IM - View even when NNMi incidents are converted into JP1 events. If you need to display these attributes, see 4.4.1(3) Displaying internal attributes in the Event Details window. Furthermore, when adding definitions to a definition file for extended event attributes, you must add definitions to the definition files for extended event attributes for all languages. If you have not added the definitions to the definition files for extended event attributes for some languages, the definitions will not be enabled.

#2

Displayed as the elapsed time in seconds since 1970-01-01 at 00:00:00 (world standard time). When the attribute is displayed in the Event Details window of JP1/IM - View, the value is displayed in the time format based on the time specified in the local time zone of the viewer host.

#3

Displayed as the elapsed time in milliseconds since 1970-01-01 at 00:00:00 (world standard time).

#4

$n is replaced with a number in the range from 1 to the number of custom attributes (NNMI_CIA_NUM). Attributes whose $n is from 1 to 20 are displayed in the Event Details window of JP1/IM - View by default. If you want to display attributes whose $n is greater than 20, see 4.4.1(4) Displaying custom attributes in the Event Details window.

Example: In the case of the fourth custom attribute value, define as NNMI_CIA_VALUE_4.

#5

Even when a value is entered into the Notes attribute of an NNMi incident that has been converted into a JP1 event, the attribute value is not mapped into the JP1 event attribute. Only NNMi incident attributes in which values have been entered before JP1/IM - EG for NNMi obtains NNMi incidents from NNMi can be mapped to JP1 event attributes.

#6

The following values will be used based on the -ssl option set for the jegn_setup command of JP1/IM - EG for NNMi:

- If false is specified for the -ssl option: http

- If true is specified for the -ssl option: https

To Page Top