Setting up the Main node configurations
Summarize
Summary of Setting up the Main node configurations
The Main node configurations in Operational Resilience, introduced in Release 20.1.x, allow administrators to define the roll-up chain for dependencies among various CSDM objects. This setup enables data integration from the CMDB into Operational Resilience, facilitating a comprehensive view of dependencies in the Workspace.
Show less
Key Features
- Customizable Relationships: Administrators can set up and customize relationships between business services, application services, service offerings, and business processes.
- Main Node Configurations: Includes various configurations such as Opres with CSDM header, Service (CMDB), and Dependency configurations, each serving different user needs.
- Dependency Framework: Defines how different entities relate to one another, enabling multiple levels of dependency management.
- BCM Integration: When the Business Continuity Management application is installed, BCM-related dependencies can be incorporated into Operational Resilience.
Key Outcomes
After setting up the Main node configurations, users can expect:
- Integration of CMDB data for effective reporting within Operational Resilience.
- Customizable views and configurations tailored to specific business needs, enhancing understanding of service dependencies.
- Enhanced ability to manage and visualize service and process relationships through 360º views.
Starting with Release 20.1.x, Main node configurations are set up in Operational Resilience to define the roll-up chain for dependencies. Operational Resilience administrators configure the entity types and pillars, generate the entities, and then establish relationships between different CSDM objects. After this setup is complete, data is fetched from the CMDB into Operational Resilience, and the rolled-up dependencies are displayed in the Workspace view.
Main node configurations in Operational Resilience support different business views in the CSDM model. The relationships defined in the Main node configuration align with the relationships specified in the CSDM model. The data structure is used to retrieve data from the CMDB and integrate it into Operational Resilience.
Main node configurations
Main node configurations include relationships such as mappings between a business service and an application service, an application service to another application service, a service offering to a business process, and so on.
The base version of Operational Resilience includes the following Main node configurations, with the source being the OpRes CMDB.
Opres with CSDM header configuration for business services: The Opres with CSDM header configuration defines the relationships for a business service and is primarily used by new customers.
This configuration sets up the direct and indirect relationships between the following objects:
- Application services
- Business processes
- Business services
- Service offerings
The following diagram illustrates the structure of the Opres with CSDM header configuration, available as a base version in Operational Resilience. A business service can have relationships configured with one or more application services, service offerings, and business processes. When entities are generated and scheduled jobs are executed, dependencies are fetched and rolled up to the parent business service. The configuration supports multiple levels of dependencies, as shown in the example.
For more information on the Opres with CSDM header configuration, see Opres with CSDM header Main node configuration.
Service (CMDB) configuration for services: The Service (CMDB) configuration defines the relationships for a service and is primarily used by existing customers. It supports only one level of dependency, such as a parent service having a child service, a process, or a dependency. A child service can have a process and a dependency (such as Dep2 or Dep4 as shown in the example) and a process can have a dependency (such as Dep3 as shown in the sample hierarchy).
For more information on the Service (CMDB) configuration, see Service (CMDB) Main node configuration.
- Dependency configurations:
The Dependency configurations define the relationships for dependencies that are related to business services, business processes, and service offerings.
Business process to dependencies: The Business process to dependencies configuration defines the relationships from a business process to its dependencies. The following diagram shows the dependency relationship framework for a business process, available as a base version in Operational Resilience. A business process can have relationships with application services, other business processes, technical services, contracts, third parties, and more. When entities are generated and scheduled jobs are executed, dependencies are fetched and rolled up to the parent business process.
For more information on the Business process to dependencies configuration, see Business process to dependencies Main node configuration.
Business service to dependencies: The Business service to dependencies configuration defines the relationships from a business service to its dependencies. The following diagram illustrates the dependency relationship framework for a business service, available as a base version in Operational Resilience. A business service can have relationships with locations, contracts, third-parties, third-party engagements and more. When the entities are generated and scheduled jobs are executed, dependencies are fetched and rolled up to the parent business service.
For more information on the Business service to dependencies configuration, see Business service to dependencies Main node configuration.
Service offering to dependencies: The Service offering to dependencies configuration defines the relationships from a service offering to its dependencies. The following diagram shows the dependency relationship framework for the service offerings, available as a base version in Operational Resilience. A service offering can have relationships with application services, other business processes, technical services, contracts, third parties, and more. When entities are generated and scheduled jobs are executed, dependencies are fetched and rolled up to the parent service offering.
For more information on the Service offering to dependencies configuration, see Service offering to dependencies Main node configuration.
BCM dependency configurations: When the Business Continuity Management application is installed in an instance, BCM related dependencies are fetched into the Operational Resilience application. The Main node configurations related to BCM, such as BCM-CMDB, Downstream related plan, Plan primary assets, Plan related assets, and Upstream related plans, are shown in the example.
For more information on the BCM dependency configurations, see BCM dependencies related Main node configurations.
For information on gathering data aligned with the latest CSDM model, see Gathering data aligned with the latest CSDM setup.
After setting up the Main node configurations, you must ensure that the entities are generated in Operational Resilience. Only when the entities are generated in Operational Resilience and the relationships are created in the Main node configurations, CMDB data can be brought into Operational Resilience for reporting.