Category name definition file for IM management nodes (imdd_category_name.conf)

Format

{
  "meta":{
    "version":"1"
  },
  "categoryData":[
    {"categoryId":"category-ID","categoryName":"category-name"},
    ...
  ]
}

To Page Top

Files

imdd_category_name.conf

imdd_category_name.conf.model (model file for the category name definition file for IM management nodes)

To Page Top

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/

To Page Top

Description

This file defines the category names and orders of IM management nodes in management groups to display a sunburst or tree chart of data that is collected by the Intelligent Integrated Management Base. The IM management node categories are displayed in the order they are defined.

To Page Top

When the definitions are applied

The settings in the category name definition file for IM management nodes are applied to the Intelligent Integrated Management Base when the jddcreatetree or jddupdatetree command is completed successfully.

For details about the jddcreatetree and jddupdatetree commands, see jddcreatetree and jddupdatetree in Chapter 1. Commands.

To Page Top

Information that is specified

The category name definition file for IM management nodes must be saved in UTF-8 without BOM(byte order mark).

"version":"1"

Specifies the version of the category name definition file for IM management nodes. Set this to 1.

"categoryId":"category-ID"

The specified default value. Do not edit the value.

"categoryName":"category-name"

Specifies a category name of the management group that will appear in a sunburst or tree chart. The value of categoryName can be up to 255 characters in length and must not include any control characters or machine-dependent characters.

To Page Top

Example definition

Example of the definition for changing the order of the underlined categories

Before the change

{
  "meta":{
    "version":"1"
  },
  "categoryData":[
    {"categoryId":"job","categoryName":"Job"},
    {"categoryId":"serviceResponse","categoryName":"Service Response"},
    {"categoryId":"enterprise","categoryName":"Enterprise"},
    {"categoryId":"transactionProcessing","categoryName":"Transaction Processing"},
    {"categoryId":"applicationServer","categoryName":"Application Server"},
    {"categoryId":"database","categoryName":"Database"},
    {"categoryId":"platform","categoryName":"Platform"},
    {"categoryId":"virtualMachine","categoryName":"Virtual Machine"},
    {"categoryId":"managementApplications","categoryName":"Management Applications"},
    {"categoryId":"otherApplications","categoryName":"Other Applications"}
  ]
}

After the change

{
  "meta":{
    "version":"1"
  },
  "categoryData":[
    {"categoryId":"job","categoryName":"Job"},
    {"categoryId":"serviceResponse","categoryName":"Service Response"},
    {"categoryId":"enterprise","categoryName":"Enterprise"},
    {"categoryId":"platform","categoryName":"Platform"},
    {"categoryId":"database","categoryName":"Database"},
    {"categoryId":"virtualMachine","categoryName":"Virtual Machine"},
    {"categoryId":"managementApplications","categoryName":"Management Applications"},
    {"categoryId":"transactionProcessing","categoryName":"Transaction Processing"},
    {"categoryId":"applicationServer","categoryName":"Application Server"},
    {"categoryId":"otherApplications","categoryName":"Other Applications"}
  ]
}

To Page Top