IT Operations Management (ITOM)

7 Ways to Get the Most out of the New Service Health Reporter 9.30

7 Ways to Get the Most out of the New Service Health Reporter 9.30


Guest post by Vineetha Vasudevan, R&D – Software Engineer, HP SHR

The release of HP Service Health Reporter 9.30 has ushered in a whole set of features that extend platform support and scalability, making it truly a ‘One stop shop for IT Service Reporting’.


This version also includes new migration SKUs to assist customers in moving from OVPI reporting to HP SHR. For customers who are already on SHR 9.20, there is an in-place upgrade process facilitated to upgrade to SHR 9.30.


What you can do in SHR 9.30

Let’s look at some of the interesting possibilities with the latest SHR reporting solution:

  1. Remote Collector —In SHR 9.30, you can deploy the SHR Collector component on separate systems to collect data from various sources across the network. The data sources may be located within or outside a firewall. The remote collection also improves the scalability of SHR collection. Deploying collectors remotely is optional; the SHR server (with the local collector) retains its capability to collect data independently from the data sources.
  2. High Availability Environment —SHR can be configured in a High Availability environment using the Veritas Cluster Server (VCS) 5.1 or 6.0. The configuration involves a two-node cluster using a shared disk with SHR 9.30 installed on both nodes.
  3. Security Enhancements — SHR now supports secured (HTTPS) communication for its Administration console and Reporting console (SAP Business Objects InfoView) in SHR 9.30. SHR can be configured to use client certificate-based authentication (for example, logging on using smart cards), wherein SHR verifies the identity of the user by validating the smart-card-based certificate and authorizes the user using SAP Business Objects.
  4. Multi-tenant reports — Quite often there is a need for administrators to provision reports with data sets tailored for the logged-in users. This is now possible using the access-level restrictions feature in Business Objects, coupled with SHR Groups. For more details, read up on the recent blog, “Multi-Tenant reports using SHR Groups”.
  5. SHR Big Data Content — The SHR Content Packs for Hadoop and Vertica are now released on HP Live Network. Read the blog series on SHR Content on Big Data for more details and insights into these content use cases.
  6. Integrating custom topology with SHR content on OMi and Service Health: A cool new utility is now available that will help you ease custom topology data integration into OMi and Service Health content packs of SHR.
  7. Customer and Location Provisioning: It is now possible to provision Customer and Location details pertaining to IT infrastructure components so as to leverage them in IT performance reporting in SHR.


Over and above these features, we have also some nice improvements in SHR 9.30, including:

  • Reports — All reporting content has been refreshed to work on SAP Business Objects XI 3.1 SP 5. Usability improvements in place in Exchange Server content pack that include dynamic x-launch based on Exchange Server Roles.
  • Network Content — Network data integration is also now available in RtSM deployment of SHR even for cases where NNM is not integrated with BSM.
  • Integration with HP Operations Agent Virtual Appliance — The HP Operations Agent on the virtual appliance simplifies the monitoring of the VMware infrastructure by providing a mechanism for easy deployment of the agent. The preinstalled agent, once configured,is capable of collecting performance data from different vCenter Servers. The virtualization content in SHR 9.30 (VirtualEnvPerf_ETL_VMWare_PerformanceAgent component) now enables integration with this appliance as well.


One final thing: a reminder that SHR 9.30 stays open for Content Customization and Extensibility, continuing to provide flexible reporting options via its Content Development Environment (CDE), which was introduced in SHR 9.20.


Get more information

For a sneak-peek into extensibility options offered, take a look at the six-part video series provided in the blog on ‘Content development and extensibility in HP Service Health Reporter’.


Over the coming months, we’ll continue to invest in easy, flexible reporting options for the enterprise – stay tuned as we simplify the content-building experience!

Visit to for more information.

  • operations bridge
About the Author


This account is for guest bloggers. The blog post will identify the blogger.

Acclaimed Contributor.

But I see the content pack is made quite complicate compared to the PI ( Where creating the report packs are much easier ) , also the docs are not that clear .. 


I have seen very less OOB content packs available in SHR , lots of CP's are missing like CP's for QA , MPLS iSPI etc..


Tried developing the Content Pack but didn't succeed , may be I some break !!!

Acclaimed Contributor.

“I'm sorry to hear that you did not experience a totally flawless experience with Content Dev in SHR; that is always our goal and we do work hard to ensure a better extensibility experience for our customers.


As regards the span of content coverage, SHR offers 14 content packs spanning multiple domains like Systems/Virtualization, Networks (Interface and Device performance), Enterprise applications (Databases, AppServers, Active Directory, Exchange Server), Application monitoring(BPM, RUM), reporting on KPIs/HIs and Event data from the consolidated OpsBridge (OMi).

For PI migration scenarios involving extensive network content (MPLS, Traffic et al.), NNM iSPI Performance for Metrics offers detailed reporting on Networking domain.


Btw, the Content Development Environment packaged in SHR provides example content (including all source artifacts) …and this I reckon would be a good start ... The details are offered step by step in the "SHR Getting Started Guide for Content Development". An embedded video in the guide also gives a walkthru' of report creation...


We do appreciate the feedback and want you to know as mentioned in the concluding phrases of this blog that we are indeed working on simplifying the content dev experience further, which will be made available in the upcoming dot release…”


Thanks & Regards,


Acclaimed Contributor.

Hi There,


I have followed the procedure defined in the SHR Getting Started Guide for Content Development Guide , there are lots of mistakes in it , I have given the feedback on few of them to the team by replying to the emaill given @ the end ..


My recommendation is , there should be a utility which would ask the credentials of the DB which we want to connect , and then it should display the tables and relative columns so that we can select whichever we want and then it should create the necessary xml files like model , streams etc .. This feature would easies the task to a large extent ( something like feature similar to the Microsoft strategy business intelligence )


I have successfully compiled the Domain and ETL Components through the CDE with no errors but when I deployed I see no data being collected , I left as it is ...