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
Micro Focus has introduced a brand-new protocol to its outstanding line up of protocols. TruWeb is created with a developer mindset. It is a protocol that focuses on the HTTP (transport) level, providing a lightweight, scalable and cross-platform solution for web protocol testing.
This protocol is available in version 12.60 of LoadRunner and Performance Center as well as StormRunner Load. You can start to take advantage of the capabilities that TruWeb has to offer. You can write a TruWeb script using Virtual User Generator (VuGen), Atom.io, JetBrains WebStorm (IntelliJ), or other IDEs and tools.
TruWeb allows performance engineers, testers and developers create scripts on any platform. It supports Windows, MacOS and Linux. You can record scripts via HAR files or the TruWeb Proxy Recorder. On top of this, TruWeb can also be ran as a standalone solution. You can run TruWeb in single mode, which runs a single iteration for a single Vuser, or in load mode, which runs the script use the scenario settings defined in the scripts scenario.yml file.
TruWeb is currently in Tech Preview. It is in its first phase of its release. The below links will allow you to read more of the current capabilities as well as download and give it a test drive.
TruWeb is currently in Tech Preview. Meaning you do not need a license to run it. However, this may change in future versions.