Environment
- 16 May 2024
- 1 Minute to read
- Print
- PDF
Environment
- Updated on 16 May 2024
- 1 Minute to read
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Environments within a Configuration Management Database (CMDB) include various environments: development, staging, and production. This serves as controlled space for different phases of the software lifecycle.
Let's explore the following Use Case for configuring Environment!
Use Case User persona:Application Designer | Solution |
| ACME develops and deploys a variety of applications for different industries. The company operates in three main environments: Staging, Development, and Production. To ensure the stability and reliability of their services, ACME wants to implement criticality levels within their Configuration Management Database (CMDB) for each environment. | John can configure Environment under CMDB configuration and categorize their CIs into different environment levels based on their impact on business operations and services. He can define four levels: Staging, Development, and Production. Based on this, IT team can manage its software development and deployment processes more effectively, maintaining a balance between stability and innovation. |
Configure Environment
To configure Environment, perform the following steps:
- Select CMDB > Environment.
Figure: Environment - Configure the Environment for CMDB.
Figure: Configuration field - Specify the Tenant from the drop-down list and Status (Development, Staging, Production) under the field values. The configuration appears as shown below.
Figure: Configure Environment - Click Save to save the configuration for the Environment.
Figure: Environment
Figure: Configuration field
Figure: Configure Environment Was this article helpful?