L.5 Changes from version 08-00 to version 08-01

• Support was added for the following features related to correlation event issue:

  • The range of JP1 events subject to correlation event issue processing can be restricted.

  • By grouping JP1 events matching an event condition on the basis of an attribute value, correlation events can be issued on a group basis.

  • Users can change the number of sets of JP1 events that can be kept for one correlation event generation condition.

• Additional files needed to be backed up.

  • System profile (.system)

  • Definition file for issuing correlation events

• Limits were updated according to version 08-01.

• JP1/IM - Central Console and JP1/IM - Central Scope were integrated and renamed JP1/IM - Manager.

• jco_log.bat, jco_log.sh, jcs_log.bat, jcs_log.sh

• The version 7 data collection tools (jco_log.bat, jco_log.sh, jcs_log.bat, and jcs_log.sh) were discontinued. They were replaced by a data collection tool for JP1/IM - View (jcoview_log.bat) and data collection tools for JP1/IM - Manager (jim_log.bat and jim_log.sh).

• Correlation events can be issued.

• JP1/IM could be linked with JP1/IM - Rule Operation.

• The Event Issue Service (evgen) could be monitored by the health check function.

• In windows other than the Severe Events page of the Event Console window, users could select multiple JP1 events and change their response status in one operation.

• Information about the JP1 events displayed in the Event Console window could be saved as a CSV snapshot.

• The maximum length of a command executed remotely from JP1/IM - View or executed in an automated action was changed to 4,096 bytes.

• The maximum number of lines that can be displayed in the Log area of the Execute Command window was increased from 100 to 10,000. The execution results could also be sorted by column header (Time, Host, and Message).

• JP1 events output in a UTF-8 locale environment were also supported.

• A Related Events window was added for viewing related events (repeated events and correlation source events).

• The permitted monitoring range of a monitoring tree could be changed for individual JP1 users. Also, the operations users are permitted to perform on monitoring nodes within a permitted monitoring range could be individually controlled (using JP1 resource groups).

• An Add option was added to the feature for automatically generating monitoring trees.

• Items in the Monitoring Tree window and Search window could be sorted according to their status.

• The same attribute name could be used in more than one individual condition in the Status-Change Condition Settings window.

• The following operations in the Monitoring Tree (Editing) window were supported:

  • Acquire and apply changes to information from a previous version of JP1/IM - Central Scope.

  • Read and edit CSV files saved in a previous version of JP1/IM - View, and save the edited information to a previous version of JP1/IM - Central Scope.

• The programs that can be launched from the Tool Launcher window were changed.

• JP1 events were added.

• The list of log files was updated in accordance with version 08-00.

• The list of files was updated in accordance with version 08-00.

• Connectivity with previous versions was updated in accordance with version 08-00.

• The jcocmdconv command was added, allowing the user to import command execution logs from version 7 to the version 8 environment (JP1/Base enhancement).

• Messages have been added, deleted, and changed.

• JP1 events have been added.

To Page Top