A system administrator was asked by the development team to inform them of any warning
message which contains a string “Connection” on a WebSphere Application Server with High
Performance Extensible Logging (HPEL) enabled.
What should the administrator do to continuously monitor logs for the required message?
A.
Configure log detail levels to include filter on “Connection” string.
B.
Use the Log Viewer in the administrative console with filter on “Connection” string.
C.
Use the logviewer.sh or logviewer.bat command with appropriate options.
D.
Use the Log Viewer in the administrative console with filter on “Connection” string and enable
the ‘Refresh automatically’ feature.
C
0
0
The correct is C.
0
0
The right one C
0
0
c
0
0
It’s gotta be C!
0
0
way not A ?, it’s continuously monitor
0
0
way not D ?, it’s continuously monitor
0
0
logviewer.sh -monitor -includeLoggers Connection
-monitor [integer]
Specifies that you want the logViewer to continuously monitor the repository and output new log record entries as they are created. You can provide an optional integer argument after this parameter to specify how often you want the LogViewer tool to query the repository for new records. By default the logViewer queries the repository for new records every 5 seconds. When used with other filtering options, only those new records that match the filter criteria are displayed.
-includeLoggers logger_name
When this option is used, only log events from the specified loggers are included in the LogViewer output. Separate multiple entries with a comma. The * symbol can be used as a wild card to include all loggers below a parent logger. When used in combination with the -excludedLoggers option, the more specific match determines if the log event is included or excluded.
0
0
C is the correct one.
0
0
C
0
0
D is correct
0
0