CMDB relationships
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2024 10:53 AM
Just getting started with creating CMDB for a new customer. What is the best practice recommendation when setting up relationships (Depends on, Sends Data To, etc.) between Business Applications? Should the relationship be created at the Business Applications to Business Application layer or should they be created at the Application Service to Application Service layer? The Application Services (Dev, QA, Prod) will all have identical relationships. I'm guessing they should be at the Application Services layer because Change, Incident records use Application Service as the CI but just want to confirm. If that is the case, is there any easy way to duplicate information from one Application Service to another? Also, we haven't purchased Discovery yet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2024 11:12 AM - edited 11-11-2024 11:15 AM
It is recommended to follow the Common Services Data Model (CSDM 4.0) for creating relationships. The Business Application (BA) CI is primarily used for Service and Application Portfolio Management. The BA is not an operational CI, meaning it should not be used in tickets, but it represents the entire collection of products and infrastructure deployed. The relationship types defined for Business Application to any child CI is shown on that page.
For example:
A Business Application related to Application Service uses the "Consumes::Consumed by" relationship type
A Business Application related to SDLC Component uses "Contains::Contained by"
