5.9.2 Configuration File page

Configuration file contents

Displays information about the configuration file selected in the tree display area. For the items displayed in Configuration file contents, see 5.9.1 Valid Configuration Information page.

Status

Displays Collection status, Collection date/time, Application status, and Application date/time for the configuration file selected in the tree display area.

• Collection status

  Displays one of the following collection statuses for the configuration file:

  - Not collected

  - Collected

  - Collection failed

• Collection date/time

  Displays the time^#1 on the manager that information was collected in the JP1/IM - View locale.

  Collection date/time is updated when any of the following occurs: the profiles are collected in a batch operation (Batch Collect Profiles), the configuration file is collected, the configuration file is applied, or the profiles are applied in a batch operation (Batch Reflect Profiles).

• Application status

  Displays one of the following application statuses for the configuration file:

  - Blank (nothing displayed)

  This indicates that the settings file does not exist on the server or settings have been applied. For example, this status arises immediately after the settings file is imported or if the process is stopped.

  - Applied

  This indicates that the settings file has been applied and the target process is running.

  - Reflection failed^#2

  This indicates that the settings file could not be applied due to an error.

  - Saved on the server^#2

  This indicates that the created or edited settings file saved on the server has not been used by the target process.

• Application date/time

  Displays the time on the agent that information was applied correctly in the IM-View locale.

  Application date/time is updated when the profiles are applied in a batch operation (Batch Reflect Profiles) or the configuration file is applied.

Saving/application

Applied contents

• Apply

  Applies the settings to the system managed by IM Configuration Management.

• Save

  Saves the settings to the server on which IM Configuration Management is running.

Application method

Reload is chosen as the application method.

Startup Options

• Monitoring log file

  For JP1/Base, specify the paths to the log files that are specified in the log-file trap startup definition file (log file names specified for the jevlogstart command^#1 of JP1/Base).

  For remote monitoring, specify the paths to the log files (log file names specified for the jcfallogstart^#1 or jcfallogdef^#1 command).

  The following shows the characters that cannot be used in monitoring log file names.

  For JP1/Base:

  < (0x3c), > (0x3e), and | (0x7c)

  For remote monitoring:

  < (0x3c), > (0x3e), | (0x7c), * (0x2a), and ? (0x3f)

  Note that if a UNIX host is to be monitored, the path names of the log files to be monitored can have alphanumeric characters, hyphens (-), underscores (_), periods (.), and slashes (/). Log files whose path name includes characters other than these might not be monitored normally.

  The following shows the maximum number of monitoring log file names that can be specified:

  - Log file trapping in Windows: 32

  - Log file trapping in UNIX: 100

  - Remote-monitoring log file trapping: 32

  To specify multiple paths for Monitoring log file, use a space as a separator. If a path specified for Monitoring log file includes spaces, enclose the path in double quotation marks ("). The maximum length of the character string^#2 that can be specified is 1,920 bytes.

  If a Windows host is to be monitored remotely, the \\host-name part existing in the actual path name must be excluded from each path specified for Monitoring log file as shown below:

  Actual path of a monitoring log file:

  \\host-name\shared-folder-name\file-name

  Value to be specified for Monitoring log file:

  \shared-folder-name\file-name

  The following shows examples:

  Example 1: \share\logdir\test01.log \share\logdir\test02.log

  Example 2: "\share\log dir\test01.log" "\share\log dir\test02.log"

• Startup locale

  This item is displayed if the agent is a UNIX host.

  A combination of the character encoding and LANG values can be selected from the drop-down list.

  The following shows an example of the Startup locale drop-down list.

  

  For details about the Startup locale drop-down list, see Table 5-32 Settings that can be selected by using the Startup locale drop-down list (When JP1/IM - Manager operates in a Japanese OS), Table 5-33 Settings that can be selected by using the Startup locale drop-down list (When JP1/IM - Manager operates in an English OS), and Table 5-34 Settings that can be selected by using the Startup locale drop-down list (When JP1/IM - Manager operates in a Chinese OS).

• Additional options

  For JP1/Base, this text box specifies options for the log-file trap startup definition file (options for the normal jevlogstart command^#1 or the cluster-specific jevlogstart command^#1 of JP1/Base). The following options can be specified:

  • File monitoring interval (-t option)

  • Event conversion max size (-m option)

  • Read from the start of log files (-h option)

  • Display command name (-n option)

  • Log data source program name (-p option)

  • Retry specification for opening a log file (-r option)

  • Destination server name (-s option)

  • Specification for UNICODE file monitoring (-g option)

  • Specification for UNICODE file byte order (-b option)

  • Source host name (-x option)

  For remote monitoring, this text box specifies additional options (options for the jcfallogstart command^#1 or the jcfallogdef command^#1). The following options can be specified:

  • File monitoring interval (-t option)

  • Event conversion max size (-m option)

  • Log data source program name (-p option)

  • Retry specification for opening a log file (-r option)

  • Monitored host (-o option)

  • Character encoding (-c option)

  The maximum length of the character string that can be specified in the text box is 1,024 bytes.^#2

• Filter

  This item is enabled only when SSH connection is being used.

  A regular expression is specified as a predefined filter. Note that the regular expression specified here cannot include the following characters: single quotation marks ('), double quotation marks ("), left angle brackets (<), and right angle brackets (>).

• Start the process automatically when the log file trap service starts^#3

  Select this if you want to start log file trapping automatically when the agent host is restarted or the log file trap service is restarted.

Saving/application

The following items are displayed in Application method when Apply is selected in Applied contents:

• Restart^#4

  Select this to apply the new settings in the settings file by restarting the host.

• Send a file

  Select this to apply the new settings in the settings file by sending the file.

SJIS/ja_JP.SJIS

Shift JIS

ja_JP.SJIS

HP-UX

Y

SJIS/japanese

japanese

N

EUC/ja_JP.eucJP

EUC

ja_JP.eucJP

N

EUC/japanese.euc

japanese.euc

N

UTF-8/ja_JP.utf8

UTF-8

ja_JP.utf8

N

C

C

C

N

EUC/ja

EUC

ja

Solaris

Y

EUC/japanese

japanese

N

EUC/ja_JP.eucJP

ja_JP.eucJP

N

SJIS/ja_JP.PCK

Shift JIS

ja_JP.PCK

N

UTF-8/ja_JP.UTF-8

UTF-8

ja_JP.UTF-8

N

C

C

C

N

SJIS/Ja_JP

Shift JIS

Ja_JP

AIX

Y

SJIS/Ja_JP.IBM-932

Ja_JP.IBM-932

N

EUC/ja_JP

EUC

ja_JP

N

EUC/ja_JP.IBM-eucJP

ja_JP.IBM-eucJP

N

UTF-8/JA_JP

UTF-8

JA_JP

N

UTF-8/JA_JP.UTF-8

UTF-8

JA_JP.UTF-8

N

C

C

C

N

UTF-8/ja_JP.UTF-8

UTF-8

ja_JP.UTF-8

Linux

Y

UTF-8/ja_JP.utf8

ja_JP.utf8

N

SJIS/ja_JP.sjis

Shift JIS^#

ja_JP.sjis

N

SJIS/ja_JP.SJIS

ja_JP.SJIS

N

C

C

C

N

C

C

C

Other than the above

Y

C

C

C

HP-UX

Y

Solaris

AIX

Linux

Other than the above

GB18030/zh_CN.gb18030

GB18030

zh_CN.gb18030

HP-UX

Y

UTF-8/zh_CN.utf8

UTF-8

zh_CN.utf8

N

C

C

C

N

GB18030/zh_CN.GB18030

GB18030

zh_CN.GB18030

Solaris

Y

GB18030/zh_CN.GB18030@pinyin

zh_CN.GB18030@pinyin

N

GB18030/zh_CN.GB18030@radical

zh_CN.GB18030@radical

N

GB18030/zh_CN.GB18030@stroke

zh_CN.GB18030@stroke

N

UTF-8/zh.UTF-8

UTF-8

zh.UTF-8

N

UTF-8/zh_CN.UTF-8

zh_CN.UTF-8

N

UTF-8/zh_CN.UTF-8@pinyin

zh_CN.UTF-8@pinyin

N

UTF-8/zh_CN.UTF-8@radical

zh_CN.UTF-8@radical

N

UTF-8/zh_CN.UTF-8@stroke

zh_CN.UTF-8@stroke

N

C

C

C

N

GB18030/Zh_CN.GB18030

GB18030

Zh_CN.GB18030

AIX

Y

GB18030/Zh_CN

Zh_CN

N

UTF-8/ZH_CN

UTF-8

ZH_CN

N

UTF-8/ZH_CN.UTF-8

ZH_CN.UTF-8

N

C

C

C

N

GB18030/zh_CN.gb18030

GB18030

zh_CN.gb18030

Linux

Y

UTF-8/zh_CN.utf8

UTF-8

zh_CN.utf8

N

C

C

C

N

C

C

C

Other than the above

Y

1

Event Forwarding

Transfer setting file in JP1/Base

to-upper or to event-server-name

Y

Reload

Destination (host)

2

Event filter for forwarding

Conditions

3

suppress

ID

unit-of-time

threshold-value

confirmation-count

destination

Suppression of event forwarding:

Suppression ID

Unit Time (sec)

Threshold-based (count)

Check Times (to start or end suppression)

Destination (host)

4

Event filter for suppressing forwarding

Conditions

5

Log File Trapping

Log-file trap startup definition file in JP1/Base

--

N

--

Action definition file name (full path) [-f]

6

Additional option -t

Y

Restart

File monitoring interval (sec) [-t]

7

Additional option -m

Event conversion max size (bytes) [-m]

8

Additional option -h

Read from the start of log files [-h]

9

Additional option -n

Display command name [-n]

10

Additional option -p

Log data source program name [-p]

11

Additional option -r

Retry specification for opening a log file [-r]

12

Additional option -s

Destination server name [-s]

13

--

N

--

Log file trap name [-a]

14

Additional option -u

Y

Restart

Use option [-u]

15

Additional option -g

Specification for UNICODE file monitoring (Windows only) [-g]

16

Additional option -b

Specification of UNICODE file byte order (Windows only) [-b]

17

Locale

--

18

Additional option -x

Specification of source host name [-x]

19

Monitoring log file

Log Files > File name (full path)

20

Start the process automatically when the log file trap service starts (SKIP option)

Y

Reload

--

21

JP1/Base log file trap definition file

MARKSTR

Y

Reload

MARKSTRS > MARKSTR

22

ACTDEF

ACTDEFS > ACTDEF

23

FILETYPE

Y

Restart

File type

24

RECTYPE

Record type

25

HEADLINE

Number of header lines

26

HEADSIZE

Header size (bytes)

27

retry-times

Number of retries

28

retry-interval

Retry interval (sec)

29

hold-count

Number of held JP1 events

30

keep-event

Held-events pass specification

31

open-retry-times

Number of retries for opening a log file

32

open-retry-interval

Retry interval for opening a log file

33

read-retry-times

Number of retries for reading a log file

34

upd-output-event

JP1 event for UPD type^#1

35

unset-extattr

JP1 event extended-attribute options

36

Event Log Trapping

Action definition file for event log trapping in JP1/Base

server

N

--

Destination event server name

37

retry-times

Y

Reload

Number of retries

38

retry-interval

Retry interval (sec)

39

trap-interval^#2

Monitoring interval (sec)

40

matching-level

Matching level

41

filter-check-level

Filter check level

42

jp1event-send

JP1 event notifications

43

trap-name

Trap name

44

filter

Filter > Log type

45

eventid

Event ID

46

filter

Filter > Conditions

47

Local Action

Local action execution definition file in JP1/Base

usr

Y

Reload

Common Block > JP1 user name

48

var

Common Block > Environment-variable file name

49

evt

Common Block > Event ID issuing specification

50

cnt-opt

Common Block > Control option string

51

act

Action Block > Action name

52

cnd

Action Block > Event filter

53

det

Action Block > Suppression time

54

var

Action Block > Environment-variable file name

55

cmd

Action Block > Command

56

cmd-opt usrprofile

Action Block > Command Option

57

evt

Action Block > Event ID issuing specification

58

Remote Log File Trapping

Startup option for remote-monitoring log file trapping

Additional option -t

Y

Restart

File monitoring interval (sec) [-t]

59

Additional option -m

Event conversion max size (bytes) [-m]

60

Additional option -p

Log data source program name[-p]

61

Additional option -r

Retry specification for opening a log file [-r]

62

--

N

--

Destination server name [-s]

63

--

Log file trap name [-a]

64

--

Monitored host [-o]

65

--

Regular expression type

66

Monitoring Log File Locale

Y

Restart

--

67

Monitoring log file

File name under Log Files

68

Filter

--

69

Remote-monitoring log file trap action-definition file

retry-times

Y

Restart

Number of retries for connecting to the event service

70

retry-interval

Retry interval for connecting to the event service (sec)

71

open-retry-times

Number of retries for opening a log file

72

open-retry-interval

Retry interval for opening a log file (sec)

73

hold-count

Number of held JP1 events

74

keep-event

Held-events pass specification

75

FILETYPE

File type

76

HEADLINE

Number of header lines

77

MARKSTR

Y

Reload

MARKSTR under MARKSTRS

78

ACTDEF

ACTDEF under ACTDEFS

79

nset-extattr

JP1 event extended-attribute options

80

Remote Event Log Trapping

Startup option for remote-monitoring event-log trapping

--

N

--

Monitored host [-o]

81

--

Destination event server name

82

--

Regular expression type

83

--

Y

Restart

Filter > Log type [-filter]

84

Remote-monitoring event log trap action-definition file

retry-times

Y

Reload

Number of retries

85

retry-interval

Retry interval (sec)

86

open-retry-times

Number of retries when collecting event log data

87

open-retry-interval

Retry interval for collecting event log data (sec)

88

trap-interval

Monitoring interval (sec)

89

matching-level

Matching level

90

filter-check-level

Filter check level

91

filter

Filter > Conditions