Hitachi

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


IM management node link definition file (imdd_nodeLink_def.conf)

Organization of this page

Format

{
  "meta":{
    "version":"1"
  },
  "links":[
    {
      "from":"tree-SID-of-the-preceding-node or SID-of-the-preceding-node ",
      "to":"tree-SID-of-the-subsequent-node or SID-of-the-subsequent-node",
      "type":"information-type"
      "value":{
        "unit":[
          {
              "precedingJob":"complete-name-of-preceding-linked-unit",
              "succeedingJob":"complete-name-of-subsequent-linked-unit", 
              "succeedingJobTimeType":"format-of-scheduled-date-and-time-for-linkage"
              ]
      }
    }, ...
  ]
}

Files

imdd_nodeLink_def.conf

imdd_nodeLink_def.conf.model (model file for the IM management node link definition file)

Storage directory

In Windows
For a physical host:

Manager-path\conf\imdd\

For a logical host:

shared-folder\jp1imm\conf\imdd\

In UNIX
For a physical host:

/etc/opt/jp1imm/conf/imdd/

For a logical host:

shared-directory/jp1imm/conf/imdd/

Description

This file defines relationships between IM management nodes. You can use this definition file to define new relationships between IM management nodes. If you define the same relationship as that in the IM management node link file (imdd_nodeLink.json) (which is the one with the same from, to, and type), the relationship defined in this file takes effect in the system.

If JP1/AJS or JP1/PFM is linked, a relationship between monitoring targets is registered automatically by the related node display function. If you want to add other relationships separately and show them in the integrated operation viewer, you can specify them in this definition file. For details about the related node display function, see 3.6 Related node display function in the JP1/Integrated Management 2 - Manager Overview and System Design Guide.

When defined relationships do not support the related node display function, the relationships in question do not show up in the integrated operation viewer. However, if you use the REST API, you can get the settings as data. However, if you use the REST API, you can get the settings as data. For details about the REST API, see the manual provided separately.

When the definitions are applied

The settings in the IM management node link definition file are applied to the Intelligent Integrated Management Base when the jddupdatetree command is completed successfully.

Information that is specified

The IM management node link definition file must be saved in UTF-8 without BOM (byte order mark).

version

Specifies the version of the IM management node link definition file. Set this to 1.

from

This node is the preceding node. Specifies the tree SID or the SID. The SID can be up to 1 megabyte in size and must not include any control characters. Acceptable characters are alphanumeric characters and the following symbols: underscore (_), forward slash (/), percent sign (%), hyphen (-), period (.), colon (:), and tilde (~). This option is mandatory.

The Job flow tab displays relationships between IM management nodes only when rootJobnetExecutionOrder is specified for type and an SID is specified. If you specify a tree SID, you cannot view relationships between IM management nodes in the window. However, by using the link information acquisition API, you can acquire link information specified with the tree SID. For details, see the document provided separately.

The Related node tab, on the other hand, displays relationships between IM management nodes regardless of the value specified for type or whether an SID or tree SID is specified.

Example to specify a root jobnet:

_JP1AJS-M_HOST1/_HOST_HOST1/_JP1SCHE_schedulerserv/_JP1JOBG_jobgroup/_JP1ROOTJOBNET_jobnet1
to

This node is the subsequent node. Specifies the tree SID or the SID. The SID can be up to 1 megabyte in size and must not include any control characters. Acceptable characters are alphanumeric characters and the following symbols: underscore (_), forward slash (/), percent sign (%), hyphen (-), period (.), colon (:), and tilde (~). This option is mandatory.

The Job flow tab displays relationships between IM management nodes only when rootJobnetExecutionOrder is specified for type and an SID is specified. If you specify a tree SID, you cannot view relationships between IM management nodes in the window. However, by using the link information acquisition API, you can acquire link information specified with the tree SID. For details, see the document provided separately.

The Related node tab, on the other hand, displays relationships between IM management nodes regardless of the value specified for type or whether an SID or tree SID is specified.

Example to specify a root jobnet:

_JP1AJS-M_HOST1/_HOST_HOST1/_JP1SCHE_schedulerserv/_JP1JOBG_jobgroup/_JP1ROOTJOBNET_jobnet2
type

Specifies the type indicated by the link information set by from and to. Control characters are not acceptable. This option is mandatory.

The following type is supported as standard:

  • rootJobnetExecutionOrder (relationship of execution order of a root jobnet)

  • managerAgent (relationship between a manager and agent of a JP1 product)

  • rootJobnetAgent (relationship between a root jobnet and an AJS agent)

  • sameNode (relationship between nodes having the same name)

If you specify rootJobnetExecutionOrder for type, specify the SID of the IM management node for from and to.

value

Specifies additional link information. This option is optional.

unit

Specify it if the information type is an execution order of a root jobnet. Specify the information of a linked unit. This option is optional.

precedingJob

Specifies the complete name of a preceding linked unit. Specify a string of one megabyte or less other than control characters. This option is mandatory.

Example :

/jobnet1/JP1 event sending job
succeedingJob

Specifies the complete name of a subsequent linked unit. Specify a string of one megabyte or less other than control characters. This option is mandatory.

Example :

/jobnet2/JP1 event reception monitoring job
succeedingJobTimeType

Specify it if the information type is an execution order of a root jobnet. Specify a scheduled date and time for linkage. This option is optional. If it is omitted, endtime is assumed for operation.

  • startTime

    Specify it if the link is configured so that execution of the subsequent unit is started after the preceding unit ends. For example, use it for the link through cancellation of holding operation or a wait condition.

  • endTime

    Specify it if the link is configured so that the wait condition of the subsequent unit is met after the preceding unit ends. For example, use it for the link through event jobs (such as a file monitoring job or incoming email monitoring job).

Example definition

{
    "meta":{
        "version":"1"
    },
        "links": [
    {
     "from":_JP1AJS-M_HOST1/_HOST_HOST1/_JP1SCHE_schedulerserv
/_JP1JOBG_jobgroup/_JP1ROOTJOBNET_jobnet1",
     "to":_JP1AJS-M_HOST1/_HOST_HOST1/_JP1SCHE_schedulerserv
/_JP1JOBG_jobgroup/_JP1ROOTJOBNET_jobnet2",
     "type":"rootJobnetExecutionOrder",
     "value":{
          "unit":[
           {
              "precedingJob":"/jobnet1/job1",
              "succeedingJob":"/jobnet2/Job2",
              "succeedingJobTimeType":"startTime"
           }, ...
         ]
      }
 
        }, ...
    ],
}