L.2 Changes in version 12-50

(1) Changes in the manuals 3021-3-D51-20(E), 3021-3-D52-20(E), 3021-3-D53-20(E), 3021-3-D54-20(E), 3021-3-D56-20(E), and 3021-3-D58)(E)

• The following functions were added to the Intelligent Integrated Management Base to reduce the operational burden on JP1/IM:

  • Function for suggesting response actions appropriate to the system status

  • Function for applying system configuration information using a configuration change mode

  • Function for single sign-on linkage with external products other than JP1 products

  • Direct access URL function

• Linkage with JP1/AJS was improved.

• The information when the product is linked with JP1/OA, JP1/NNMi, and JP1/SSO can now be displayed.

• The timeout periods when JP1/IM - Manager is started and stopped can now be changed.

• The maximum number of management nodes that can be managed with the Intelligent Integrated Management Base was increased to 150,000.

• A description regarding the regular expressions that can be used in the Intelligent Integrated Management Base was added.

• The following files and directories were added to the Intelligent Integrated Management Base:

  • Suggestion definition files

  • Model files for the suggestion definition files

  • Suggestion template files

  • Model files for the suggestion template files

  • Response action execution history file

  • Single sign-on mapping definition file

  • Model file for the single sign-on mapping definition file

• A procedure for creating an operation history output destination when configuring a new cluster environment was added.

• A procedure for migrating the IM management node link definition file when updating JP1/IM and JP1/AJS to version 12-50 or later was added.

• The default timeout periods at start and stop were changed.

• The following backup files were added:

  • Single sign-on mapping definition file

  • User-created plug-ins

  • Custom UI file storage folder

  • Suggestion template files

  • Suggestion definition files

• A procedure for backup and recovery in new and rebuilding mode was added.

• A procedure for executing the jddupdatetree command in new and rebuilding mode when the Intelligent Integrated Management Base is used was added.

• The timeout period for the JP1/IM2 - Manager service (for Windows) and the jco_start command (for UNIX) was changed.

• Notes when information is obtained from JP1/AJS3 - Manager hosts of version 12-50 or later were added.

• The following log files were added to the list of log files and folders for the Intelligent Integrated Management Base:

  • jddupdatesuggestion command trace log

  • jddsetopinfo command trace log

  • jddupdatessomap command trace log

  • Log for the response action execution history file

  • User-created plug-ins

• The following files were added to the lists of data to be collected for troubleshooting:

  • Access permissions information for JP1/IM - Manager (Intelligent Integrated Management Base) (response action execution history folder)

  • Plug-in files

  • Response action execution history file

• The Intelligent Integrated Management Base can now be logged into using authentication via an OpenID provider.

• The Suggestion tab is now displayed in the Details area in the Integrated Operation Viewer window.

• The suggestion icon is now displayed in the Integrated Operation View when suggestion definition information is available.

• The Linked unit dialog box can now display associations for waiting and the jobnet connector.

• Related notes displayed on the Integrated Operation Viewer window can now be displayed using icons corresponding to the node type.

• The metric name was added as a metric that could be obtained from a linked product.

• The following commands were added:

  • jddupdatesuggestion

  • jddsetopinfo

  • jddupdatessomap

• The following definition files were added:

  • Suggestion definition files

  • Single sign-on mapping definition file

• The mode for applying changes to or deletion of system configuration information can now be specified with option of the jddupdatetree command.

• The authentication infrastructure of an OpenID provider can now be used with the jddsetaccessuser command.

• The JP1/IM - Manager (Intelligent Integrated Management Base) response action execution history file can now be acquired using the jim_log.bat and jim_log.sh commands.

• The type of linkage when linking to a root jobnet can now be specified with the IM management node link definition file (imdd_nodeLink_def.conf).

• Options regarding the OpenID provider authentication settings and system configuration application mode were added to the Intelligent Integrated Management Base definition file (imdd.properties).

• The attributes of HTML tags that can be used as an event guide message were added to the event guide information file (jco_guide.txt).

• The following attributes were added to the definition file for extended event attributes:

  • E.SUGGESTION_ID

  • E.TREE_SID

• The following JP1 events were added:

  • 00003FE0

  • 00003FE1

  • 00003FE2

• The following methods were added:

  • jp1EmService.getEvent

  • jp1SimtService.getLink

  • jp1EmService.changeEventStatus

  • jp1SimtService.getTreeSid

• 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

• OpenID authentication can now be used in the REST API.

• The name of the image file to be displayed as a node icon in the Related node tab can now be specified in the simtData member of the IM management node tree object.

• The following messages were added:

  KAJY00021-E, KAJY00022-E, KAJY00023-W, KAJY02055-I, KAJY22018-E, KAJY22019-E, KAJY22020-E, KAJY22021-E, KAJY22022-E, KAJY22023-I, KAJY22024-I, KAJY22025-E, KAJY22026-W, KAJY22027-W, KAJY22028-W, KAJY22029-W, KAJY22030-E, KAJY22031-E, KAJY22033-E, KAJY22034-W, KAJY22035-W, KAJY22036-W, KAJY22037-W, KAJY22038-W, KAJY22039-W, KAJY22040-I, KAJY22041-W, KAJY22042-W, KAJY22043-E, KAJY22044-W, KAJY22045-W, KAJY22046-E, KAJY22047-E, KAJY24113-E, KAJY24114-E, KAJY24219-E, KAJY24115-E, KAJY24116-E, KAJY32005-W, KAJY32006-E, KAJY52019-W, KAJY52020-E, KAJY52021-E, KAJY52022-E, KAJY52023-E, KAJY52024-W, KAJY52025-W, KAJY52026-E, KAJY52027-E, KAJY52028-E, KAJY52029-E, KAJY52030-E, KAJY52031-W, KAJY52032-W

• The actions were added to the following messages:

  KAJY02000-E, KAJY02003-E, KAJY02023-E, KAJY24201-E, KAJY32211-E

• A description of and corrective action for the KAJY32211-E message was added.

• The following applicable OSs are now supported:

  • Linux 8

  • Oracle Linux 8

To Page Top