Definition file for manually registering incidents (incident.conf)
- Organization of this page
Format
VERSION=version-information SS_MODE={1|2|3} #comment-line [SS_URL=http://JP1/Service Support host:port-number]
File
incident.conf (definition file for manually registering incidents)
incident.conf.model (model file for the definition file for manually registering incidents)
Storage directory
- In Windows
-
- For a physical host:
-
Console-path\conf\console\incident\
- For a logical host:
-
shared-folder\jp1cons\conf\console\incident\
- In UNIX
-
- For a physical host:
-
/etc/opt/jp1cons/conf/console/incident/
- For a logical host:
-
shared-directory/jp1cons/conf/console/incident/
Description
This definition file is used to register a JP1 event in JP1/IM - View as an incident in another product.
When the definitions are applied
The settings in the definition file for manually registering incidents take effect when the jco_spmd_reload command is executed, or when a user logs in to JP1/IM - Manager (Central Console) after restarting JP1/IM - Manager.
Information that is specified
- VERSION=version-information
-
Specify the version of the definition file for manually registering incidents. Specify 2, or 3 for version-information. If you omit this parameter, or did not specify the value correctly, the SS_URL and SS_MODE parameters are ignored. Note that if you specify this parameter more than once, the parameter on the last line is valid.
Table 2‒48: List of parameters that can be specified for the version information and definition file for manually registering incidents Version information
Parameter name
2
SS_URL#
3
SS_URL
SS_MODE
- SS_MODE={1|2|3}
-
Specify the registration mode of an incident. If you want to specify this parameter, specify 3 for the VERSION parameter. If not, this parameter is ignored. You can specify 1, 2, or 3. The following table describes available incident registration modes and when each mode should be used.
Table 2‒49: Incident registration modes and when to use each of them Incident registration mode
Description
When to use
Supported version of JP1/IM - Manager, JP1/IM - View, and JP1/Service Support
SS_MODE=1
Source attributes and their target fields are fixed.
The specification of JP1/IM - Manager 10-00 or earlier must be used for linkage with JP1/Service Support.
09-50 or later
SS_MODE=2
-
Source attributes and their target fields are fixed.
-
The event ID (B.IDBASE) is inherited in addition to the attributes that are inherited when SS_MODE=1.
-
The event ID is required to be registered.
-
Linkage with JP1/IM - Manager, JP1/Service Support, and JP1/Navigation Platform is required.
10-10 or later
SS_MODE=3
-
The mapping between source attributes and target fields is configurable.
-
Multiple attributes can be mapped to one target field.
-
Any character string you want can be inherited.
-
Any attribute or character string you want is required to be registered.
-
This mode also allows linkage with JP1/IM - Manager, JP1/Service Support, and JP1/Navigation Platform.
11-50 or later
If you omit this parameter, or do not specify the value correctly, 1 is assumed. Note that if you specify this parameter more than once, the parameter on the last line is valid.
If you specify the registration mode of an incident, information to be registered as an incident is changed. For details about registration modes of incidents and information to be registered as incidents, see 8.1.1 Attributes of a JP1 event registered as an incident in JP1/Service Support during linkage in the JP1/Integrated Management - Manager Overview and System Design Guide.
-
- #comment-line
-
A line beginning with a hash mark (#) is treated as a comment.
- [SS_URL=http://JP1/Service Support-host:port-number]
-
Specifies the URL of a Web page for JP1/Service Support on which you can register an incident by using one-byte numeric values and symbols. The default is SS_URL=, and no value is set.
The maximum length of a URL that calls JP1/Service Support is 2,046 characters. If 2 is set for the registration mode of an incident, event IDs are inherited. Therefore, the length of a message that can be inherited when 2 is set is less than the length of a message when 1 is set. If a message is truncated before the end, the user must copy the rest of the message displayed in the Event Details window, and paste it into JP1/Service Support.
When you code the port numbers of JP1/Service Support in this parameter, you must set them to ensure passage through the firewall between the JP1/IM - View machine and the JP1/Service Support machine.
To link with JP1/Service Support after upgrading JP1/IM - Manager, add this line, and then do the following:
-
Change version-information to 2 or 3.
-
Add SS_MODE on a new line to specify the registration mode when you want to register an event ID (SS_MODE=2) or you want a desired attribute or character string of a JP1 event to be inherited as an incident (SS_MODE=3).
-
Change the line beginning with IDM_URL as the comment statement (add #).
Restart JP1/IM - Manager or execute the jco_spmd_reload command to apply the definitions. If you already logged in to JP1/IM - View, restart JP1/IM - View.
-