BSM 9.x – When creating a Downtime in BSM, it’s not possible to select various CIs, for example "SiteScope Monitor" or "SiteScope Group"
When creating a Downtime in BSM, it’s not possible to select various CIs, for example "SiteScope Monitor" or "SiteScope Group".
By default BSM doesn’t allow to enable downtime for all CITs.
When creating a downtime and getting to the CI Selection screen, simply click on Help,
and BSM will tell what CITs are allowed:
All views that the user has permission to see may be selected. You can select CIs only of the following CI types:
• running software
• business application
• ci collection
• infrastructure service
• business service
"System Monitors" or "Sitescope Group" is not part of this list, thus you cannot select it.
This post has the instructions which explains how to select (for example) SiteScope Group CI for downtime scheduling.
It can easily adapted to enable any other CI for downtime scheduling.
- Please follow instructions below to select SiteScope group CI to schedule downtime
- Restart BSM
- Go to Downtime UI (Admin -> Platform -> Downtime Management)
- Verify that SiteScope group is not grey out (like a snapshot below)
- Go to Admin -> Platform -> Setup and Maintenance > Infrastructure Settings
- Find options “Object Root” and “Link Root” and change them to “root” (like on snapshot below)
- Re-login BSM
- Go to Admin -> RTSM Administration -> Modeling Studio (before editing, please backup TQL)
- Load “BSMDowntime_topology” and add “SiteScope Group” CI type to graph.
Then connect “BSMDowntime” with just added CIT with link “downtime of”
(this link become available after your changes in infra settings (see point 6)
- Double-click on “BSMDowntime” CIT and go to “Cardinality” tab.
You can see logical expression of node, your new added link between “SiteScope Group” and “BSMDowntime” will be mentioned with “AND” operand. You should switch it to “OR” (like on screenshot below)
- After these changes do not forget to save TQL