Configuration file for converting information (event_info_replace.conf)
- Organization of this page
Format
character-before-conversion=character-string-after-conversion character-before-conversion=character-string-after-conversion : character-before-conversion=character-string-after-conversion
File
event_info_replace.conf
Storage directory
- In Windows
-
- For a physical host:
-
Console-path\conf\action
- For a logical host:
-
shared-folder\jp1cons\conf\action
- In UNIX
-
- For a physical host:
-
/etc/opt/jp1cons/conf/action
- For a logical host:
-
shared-directory/jp1cons/conf/action
File permissions
The following permissions are needed to use the configuration file for converting information:
- In Windows
-
The Administrators group and SYSTEM users must be able to reference the file.
- In UNIX
-
Users with the root permissions must be able to reference the file.
Description
This file specifies the following conversion rules:
-
Conversion rules for the event takeover information transform function of the auto action and command execution.
-
Conversion rules of string for suggestion activation condition and response action when type is cmd in suggestion function.
-
Conversion rules of string for auto response action and manual response action when type is cmd
The above string can convert certain ASCII characters in event-takeover information to another string according to conversion rules of configuration file for converting information.
For details about suggestion activation criteria with type cmd and response action strings in the suggestion function, see Suggestion definition file (imdd_suggestion.conf) in Chapter 2. Definition Files.
For details on when type cmd in auto response action, see the section Automatic execution of response actions of Chapter 7. Automatic execution and manual execution of response action (JP1/IM - Agent linkage) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.
For details on when type cmd in manual response action, see the section Manual execution of response actions of Chapter 7. Automatic execution and manual execution of response action (JP1/IM - Agent linkage) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.
The configuration file for converting information is not created when JP1/IM - Manager is installed. To use this configuration file, use a text editor to create and edit event_info_replace.conf.
When the definitions are applied
- For an automated action:
-
The contents of the configuration file for converting information take effect when JP1/IM - Manager starts, when the Apply button is clicked on the Action Parameter Definitions window of JP1/IM - View, and when the jcachange command is executed to reload the definition.
- For command execution:
-
The contents of the configuration file for converting information take effect when the Execute Command window opens.
- For the Intelligent Integrated Management Base (suggestion function, auto and manual execution function in Response Action):
-
The contents of the configuration file for converting information take effect when the JP1/IM3-Manager service is started, when the jddupdatesuggestion command is executed to reload the suggestion definition, or when REST API is execute to load the auto response action definition.
If loading the configuration file for converting information fails when the JP1/IM3-Manager service is started, conversion is made with no conversion rule.
If loading the configuration file for converting information fails when the jddupdatesuggestion command is executed to load the suggestion definition, or when REST API is execute to load the auto response action definition, conversion is made with the conversion rules before the suggestion definition is loaded.
Note that if there is no configuration file for converting information, the function works without any conversion rule.
Information that is specified
- character-before-conversion=character-string-after-conversion
-
Define in the configuration file for converting information conversion rules for the event inheritance information conversion function. Each rule consists of a character-before-conversion and a character-string-after-conversion. You can specify from 0 to 34 conversion rules.
Lines consisting of only spaces, tabs, or linefeed codes in the event inheritance information conversion settings file are ignored. Specify one conversion rule per line. Separate the character before conversion from the character string after conversion with an equal sign (=).
A defined line that is not in the format character-before-conversion=character-string-after-conversion is ignored and processing continues. If no character string after conversion is specified, the function assumes that the specified character before conversion is to be deleted from the event inheritance information.
There can be only one conversion rule for the same character before conversion. If more than one conversion rule is specified for the same character before conversion, the first conversion rule specified takes effect and the subsequent conversion rules for that character are ignored.
If the event inheritance information contains a control character (0x01 to 0x08, 0x0A to 0x1F, or 0x7F), the control character is converted to a space (0x20).
If either of the following applies, the conversion rules are ignored and processing continues:
-
A character that cannot be specified as a character before conversion is specified.
-
Two or more characters are specified as a character before conversion.
- character-before-conversion
-
As a character before conversion, you can specify an ASCII character (0x00 to 0x7F) indicated by Y in the applicable character-before-conversion column of the table below.
The table below lists the ASCII characters that can be specified as the character before conversion.
Table 2‒21: Characters that can be specified as a character before conversion and a character string after conversion Character
Hexadecimal value
character-before-conversion
character-string-after-conversion
Control character
0x00 to 0x08
N
N
Tab
0x09
Y
Y
Control character
0x0a to 0x1f
N
N
Space
0x20
Y
Y
!
0x21
Y
Y
"
0x22
Y
Y
#
0x23
Y
Y
$
0x24
Y
Y
%
0x25
Y
Y
&
0x26
Y
Y
'
0x27
Y
Y
(
0x28
Y
Y
)
0x29
Y
Y
*
0x2a
Y
Y
+
0x2b
Y
Y
-
0x2c
Y
Y
.
0x2d
Y
Y
/
0x2e
Y
Y
:
0x2f
Y
Y
;
0x3b
N
Y
<
0x3c
Y
Y
=
0x3d
Y
Y
>
0x3e
Y
Y
?
0x3f
Y
Y
@
0x40
Y
Y
[
0x5b
Y
Y
\
0x5c
Y
Y
]
0x5d
N
Y
^
0x5e
Y
Y
_
0x60
Y
Y
{
0x7b
Y
Y
|
0x7c
Y
Y
}
0x7d
Y
Y
~
0x7e
Y
Y
- character-string-after-conversion
-
As a character string after conversion, you can specify 0 to 2 ASCII characters (0x00 to 0x7F) indicated by Y in the applicable character-string-after-conversion column of the above table.
-
Example definition
The following shows examples of converting ", ', and * to _:
"=_ '=_ *=_
When the value for a message (B.MESSAGE) receives a JP1 event, The Web server goes down. Details: "NetworkΔError", the value for the entire message text (variable: EVMSG) will be The Web server goes down. Details: _NetworkΔError_.