Hitachi

JP1 Version 11 JP1/Integrated Management - Manager Overview and System Design Guide


Summary of amendments

The following table lists changes in this manual (3021-3-A07-30(E)) and product changes related to this manual.

Changes

Location

For linkage with JP1/Service Support, a new incident registration mode was added to allow any event attributes or character strings to be inherited.

2.5, 8.1.1

A common exclusion-condition in extended mode can now exclude a JP1 event that satisfies the condition from automated-action execution.

3.2, 3.2.6, 3.2.7, 5.1, 5.4.4

A description was added for the common exclusion history file that logs the exclusion processes of common exclusion-conditions.

3.2.7(5)

A description was added for the common exclusion-conditions definition history file that logs the definition history of common exclusion-conditions.

3.2.7(6)

A note was added for the common exclusion-conditions.

3.2.7(7)

The maximum number of repeated event conditions was increased to 2,500. The total size of the definitions of repeated event conditions was increased to 15 MB.

3.4.3, 3.4.4, 3.5.4, Appendix D.1(1), Appendix D.1(2)

Saving event listings (CSV snapshot) now includes action-excluded events.

3.15.1(3)

Saving event information from the integrated monitoring database (output of an event report) now includes the following event attributes:

  • Common exclude conditions group ID (E.JP1_IMCOMEXCLUDE_ID)

  • Common exclude conditions group name (E.JP1_IMCOMEXCLUDE_NAME)

  • Common exclude conditions group target-for-exclusion (E.JP1_IMCOMEXCLUDE_TARGET)

3.15.2(3)

Defined automated actions can now be enabled or disabled by using the Action Parameter Definitions window or the jcachange command.

5.1, 5.2, 5.3, 5.3.1, 5.3.3, 5.4.4

A note was added for cases where the automated action function requests a large number of agents at once to execute a command.

5.1

For automated action definitions, the status of execution conditions can now be retained unless their definitions are changed.

5.3.3

A consideration on maintenance was added for excluding error events that are caused by maintenance work from action execution.

11.1.3(1)(c), 12.10.1(2), 12.10.2(2)(b)

The maximum number of hosts that can be managed by one instance of JP1/IM - Manager was increased to 2,500.

12.1.3, Appendix D.1(1), Appendix D.3(1)

The following files were added to the list of files and folders:

  • Configuration file for incident inheritance information

  • Model file for the configuration file for incident inheritance information

  • Common exclusion history file

  • Common exclusion-conditions definition history file

Appendix A.1(2), Appendix A.2(2)

The maximum number of hosts on which commands can be executed from one instance of JP1/IM - Manager was increased 2,500.

Appendix D.1(1)

The maximum number of defined common exclusion-conditions groups (in extended mode) was increased to 2,500. The maximum filter length of the common exclusion-conditions groups (in extended mode) was increased to 15 MB.

Appendix D.1(1)

The maximum number of hosts that can be set in a business group or monitoring group was increased to 2,500.

Appendix D.3(1)

In addition to the above changes, minor editorial corrections were made.