Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Command, Definition File and API Reference


Summary of amendments

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

Changes

Location

The following commands were added:

  • jddupdatesuggestion

  • jddsetopinfo

  • jddupdatessomap

1.Commands, 1. jddupdatesuggestion, 1. jddsetopinfo, 1. jddupdatessomap

A note was added to inform users that the command in question cannot be executed simultaneously with the jddupdatesuggestion command.

1. jddcreatetree, 1. jddupdatetree

It is now possible to use an option to specify how to apply changed or deleted system configuration information.

1. jddupdatetree

The authentication infrastructure provided by the OpenID provider can now be used. The functional description was modified to reflect this change.

1. jddsetaccessuser

The following file can now be collected:

  • Response action execution history file for JP1/IM - Manager (Intelligent Integrated Management Base)

1. jim_log.bat (Windows only), 1. jim_log.sh (UNIX only)

A linkage type can now be specified for linkage with root jobnets.

2. IM management node link definition file (imdd_nodeLink_def.conf)

Information regarding JP1/NNMi, JP1/OA and JP1/SSO was added.

2. IM management node link definition file (imdd_nodeLink_def.conf), 4.4.4(4), 4.5.14, 5.5.1, 7.1.1, 7.1.4(4), 7.1.4(5), 7.2.2(3)

The following definition files were added:

  • Suggestion definition file

  • Single sign-on mapping definition file

2. Suggestion definition file, 2. Single sign-on mapping definition file (imdd_sso_mapping.properties)

The following options can now be specified:

  • Authentication setting for OpenID provider

  • Default setting to be applied when the jddupdatetree command is executed without the option to specify how to apply the changes made to the system.

Notes were added.

2. Intelligent Integrated Management Base definition file (imdd.properties)

Following the incorporation of the suggestion function, additional information was provided under Description and When the definitions are applied.

2. Configuration file for converting information (event_info_replace.conf)

A new attribute was added to an HTML tag, which can be used in an event guide message when the Integrated Operation Viewer window of the Intelligent Integrated Management Base is displayed.

2. Event guide information file (jco_guide.txt)

The following attributes were added to the default definition file (default.conf):

  • E.SUGGESTION_ID

  • E.TREE_SID

2. Definition file for extended event attributes

The following JP1 events related to the suggestion function were added:

  • 00003FE0

  • 00003FE1

  • 00003FE2

3.2.1, 3.2.2

Information regarding what happens when the jddupdatetree command is executed in configuration change mode was added in the table listing affected functions.

4.4.3(3)

The following methods were added:

  • jp1EmService.getEvent

  • jp1SimtService.getLink

  • jp1EmService.changeEventStatus

  • jp1SimtService.getTreeSid

4.5, 4.5.13, 4.5.14, 4.5.15, 4.5.16

The following APIs were added:

  • Suggestion mapping information acquisition API

  • Previous execution history acquisition API

  • Response action suggestion API

  • Response action execution API

  • Single sign-on mapping definition application API

5.1, 5.8.4, 5.13.1, 5.13.2, 5.13.3, 5.14.1

OpenID authentication was added as one of the REST API authentication methods.

5.2.8(3)

An image file can now be specified for member simtData of the IM management node tree object. The specified image file will be displayed as a node icon on the Related node tab.

7.2.2(1)

The following OSs are now supported:

  • Linux 8

  • Oracle Linux 8

--

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