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
APM 9.40 installed in Linux
When generating the EUM report “BPM Performance over time” or “Metrics overtime” the timestamp of the header of all columns doesn’t dshowa proper timestamp,
but a string like “@_@15”
This does not happen on a APM 9.40 on Windows installation.
In APM’s eum.log the following error is logged when the report is generated:
(EumBaseTablePresentationBuilder.java:127) ERROR – Failed to generate table presentation model for PerformanceMatrixTable
java.util.MissingResourceException: Can’t find resource for bundle java.util.PropertyResourceBundle, key format.HOUR_minute
Some tests done:
on a working system I generated a report at 01/15, showing data points at 15:02, 16:00, 17:00, after saving the report via the browser in one of the files
(in my case it’s “HPE Application Performance Management (running on sov02bac13.eu.hpecorp.net)_files”\PIDefaultEntryPoint_data\newReport_data\DrawSkeletonAction_data\ajaxNavigate.htm
using F12 -> tab Inspector in Mozilla, or F12 in IE does the same trick)
I can see for a table cell with time “15:02”
<td realcellindex=”3″ title=”15:02″ .. name=”@_@1516024920″ ..
for the field with time “16:00” I can see
<td realcellindex=”4″ title=”16:00″ .. name=”@_@1516028400″
so in my case we do have the correctly displayed time, “15:02”, I guess via the element “title” but also this strange string “@_@1516024920”, which turns out to be the EPOCH date/time.
1516024920 = 15/01/2018 15:02:00
on a failing system, the HTML code when disaplying the report shows the bad values as column title:
title=”@_@151623633″ .. name=”@_@151652633″ ..
which (I think) explains what we see, a column title “@_@15”,
while in my system’s case I have
title=”15:02″ .. name=”@_@1516024920″ ..
and thus I see “15:02” as column title.
On Windows environments the code doesn’t refer to the property “format.HOUR_minute” but on Linux it does due to some conditions.
Also the property “format.HOUR_minute” is missing in some of the localizaion files.
There was a localization parameter missing.
The code has been fixed to take the correct parameter.
A hotfix is available via QCCR1I130187
Immediate Openings for Automation Test Lead in Hexaware Technologies Ltd. Chennai
- 6+ years of IT experience and minimum 5+ years of experience on QTP and QC tools.
- Strong hands on experience in leading test automation projects.
- Experience in leading test automation initiatives.
- Proficient in Functional / Regression Test Automation concept design, framework definition and scripting
- Must have led team in at least two/ three project( s) with complete SDLC
- Extensive vbscript programming experience on QTP
- Ability to develop complex function libraries in QTP
- Select and develop appropriate test automation techniques, applying the latest strategy in test automation
- Should have worked in an onshore- offshore project delivery model
- Practical project management experience, specifically relating to environment, infrastructure and test management.
- Experience in dealing with SQL databases and writing queries
- Hands on experience working with agile methodology and financial / banking systems are added advantage.
- Good communication and cross- group collaboration skills.
Send your resume to firstname.lastname@example.org
To specify a measurement of a monitor which will be taken into account for SLA calculations, these steps can be followed:
1. Go to the SLA definition.
2. Go to Define KPIs section.
3. Select the SiteScope Monitor CI associated to the metrics that should be measured and edit the KPI on the left panel.
4. Introduce the name of the measurement in the Measurement type field.
If SiteScope measurement is called status, the word status should be introduced.
5. Start the SLA if it is a new SLA or recalculate it if it is a new one.
Partition Manager runs every hour, 24 times a day. PM likes to sleep a lot, it wakes up every hour to do its job and goes back to sleep again (snooze mode).
It depends on what changes were made, if configuration changes were done, then a restart is a good idea so it can reload them. Each time Partition Manager starts, it needs to reload PM_CONFIG. If a restart is not done, the maximum waiting time is one hour.
The Extensibility guide describes how to validate the mapping rules using an XML schema.
The Extensibility guide explains the creation of a complete topo sync package using an example.
NOTE : This guide does not describe uCMDB basics and relies on quite some uCMDB know-how. (E.g. what are ci-types, what are the key attributes, etc.). The OMi Extensibility guide is the right place to describe these uCMDB basics.
Creating custom Content Pack requires uCMDB know-how, therefore it’s hard or even impossible to create a SyncPackage, if one doesn’t know what to map where.
It’s possible to map configuration item types to RTSM views using the RTSM Modeling Studio, so that views are available for selection and use in the Health Top View pane.
Comprehensive details about how to create new CI types, and how to work with the concepts of the RTSM, are described in the HP Business Service Management Modeling Guide.
This guide (Modeling.pdf) is part of the standard BSM documentation.