2.2.1 Define configuration item classes and managed items
This section describes the use cases for defining classes of configuration items and managed items to optimize managed items.
Suppose you are operating an in-house service that creates and provides, for each department, a test environment for software under development in your company.
If the “CMDB” function is used to manage the provided test environment as configuration items, it is possible to use the configuration item classes that exist by default to manage each of the elements (such as computers and software) that make up the test environment. However, this can result in redundant administrative procedures, such as the presence of unnecessary fields in each class or the need to create and associate multiple configuration items of different classes.
This section describes the procedure for creating a class that represents the “test environment” to be provided as a single configuration item, and summarizes only the necessary information.
Assume that the following fields are required as a result of the operational management study.
The fields [Name], [Deployment State], [Incident State], and [Attachments] are created automatically.
- Description
- Customer (recipient department), Owner (member of the recipient department)
- FQDN
- IP Address
- Version of the software to be tested
- Edition of the software to be tested (Basic, Premium)
- Date when provision of the test environment started
- Date when provision of the test environment ended
- Size (Large, Medium, Small) indicating the performance of the computers in the test environment
FQDN and IP Address, which are mentioned above, are fields that are already defined. Definitions of the other fields will be newly created.
(Table) Input details for catalog items (create a class)
| Field | Value |
|---|---|
| Name | TestEnvironment |
| Permission Group | Specify "itsm-configitem". |
| Categories | Specify "Default". |
| Validity | Select "valid". |
| Comment | Provided test environment. |
(Table) Input details for dynamic fields (text)
| Field | Value |
|---|---|
| Name | Specify "TestEnvironmentVersion". |
| Validity | Specify "valid". |
| Label | Specify "Version". |
[Create a multi-line text field]
(Table) Input details for dynamic fields (textarea)
| Field | Value |
|---|---|
| Name | Specify "TestEnvironmentDescription". |
| Validity | Select "valid". |
| Label | Specify "Description". |
| Number of rows | Specify "8". |
[Create a field for possible values]
(Table) Input details for dynamic fields (dropdown)
| Field | Value |
|---|---|
| Name | Specify "TestEnvironmentEdition". |
| Validity | Select "valid". |
| Label | Specify "Edition". |
| Possible values | Click the [Add value] button and add the following:
|
| Default value | Specify "Basic". |
- Name: TestEnvironmentSize
- Label: Size
- Possible values
- Key: Large, Value: Large
- Key: Medium, Value: Medium
- Key: Small, Value: Small
- Default value: Medium
(Table) Input details for dynamic fields (customer)
| Field | Value |
|---|---|
| Name | Specify "TestEnvironmentCustomer". |
| Validity | Select "valid". |
| Label | Specify "User department". |
[Create a customer user field]
(Table) Input details for dynamic fields (customer user)
| Field | Value |
|---|---|
| Name | Specify "TestEnvironmentCustomerUser". |
| Validity | Select "valid". |
| Label | Specify "User". |
(Table) Input details for dynamic fields (date)
| Field | Value |
|---|---|
| Name | Specify "TestEnvironmentProvisionStartDate". |
| Validity | Select "valid". |
| Label | Specify "Provision start date". |
- Name: TestEnvironmentProvisionEndDate
- Label: Provision End Date
---
Pages:
- Name: Summary
Layout:
Columns: 3
ColumnWidth: 1fr 1fr 1fr
Content:
- Section: Contact
RowStart: 1
ColumnStart: 1
- Section: Environment
RowStart: 1
ColumnStart: 2
- Section: Period
RowStart: 1
ColumnStart: 3
- Section: Description
RowStart: 2
RowSpan: 2
ColumnStart: 2
ColumnSpan: 2
Sections:
Description:
Type: Description
Header: Description
Contact:
Content:
- Header: Recipient department
- DF: TestEnvironmentCustomer
- DF: TestEnvironmentCustomerUser
Environment:
Content:
- Header: Environment information
- DF: ITSMNetworkInfo-FQDN
- DF: ITSMNetworkInfo-IPAddress
- DF: TestEnvironmentVersion
- DF: TestEnvironmentEdition
- DF: TestEnvironmentSize
Period:
Content:
- Header: Provision period
- DF: TestEnvironmentProvisionStartDate
- DF: TestEnvironmentProvisionEndDate
Some of the labels of classes that exist by default are provided with translations of values, so English field names such as “Description” will be translated and displayed when the display language is set to Japanese. To change the display language, use the icon for changing the language for Ops I. For details, see “Functions > Basic window structure” in “JP1 Cloud Service/Operations Integration User’s Guide”.
For labels that have no translation provided, they have been created in Japanese since the primary display language is Japanese.
[Specify fields to trigger updating the class version]
Specify configuration item fields that will increment the configuration item version when the field is updated. Here, you will configure settings so that the configuration item version will be incremented when a change occurs to the following fields of the created class.
- FQDN
- IP Address
- Version
- Edition
- Size
(Table) Input details for catalog items (modifying a class)
| Field | Value |
|---|---|
| Version Trigger | Select the following.
|