Current BSM dashboards show limited capability of displaying NNMi iSPI Metric reports in any of the out of box NNMi Components.
With a bit of creative thinking we can overcome this limitation.
As MyBSM allows us to create a URL-based component, the main objective is to set up a reoccurring report schedule in iSPI Metrics and have the html report saved to a remote file system whilst maintaining a static file name. The report can then be published by IIS in which the MyBSM URL component can then reference. Let’s demonstrate how this can be done in the following high level steps.
From the BI Configuration on the iSPI Metrics server, set up the remote File System where your iSPI Metric report will be saved. Note that SERVER_FS is a remote Windows server with Internet Information Services (IIS) activated and listening to port 80, and NPS_reports is a folder we’ve shared.
From the iSPI Metrics console which is cross launched from the NNMi console, go to BI Server -> Administration. Then navigate to: Configuration -> Dispatchers and Services. Click on the Define File System icon.
Define the File System Location by specifying a sub directory. In this example we want our report to be saved to the SampleReports sub-directory which resides under our shared folder called NPS_reports.
Create the report schedule for the desired report in iSPI Metrics. We have chosen the out of box “Report View Of Executive” report to be saved to the Sample Reports location we defined in the previous step.
Select the option to “Replace existing files” with the static file name we have chosen:
Note that iSPI Metrics adds a suffix of “-en-au.mht” to the Report name above when it’s actually saved to the file system.
This is what the report looks like when saved to SERVER_FS:
On SERVER_FS, we have defined our Virtual Directory where our html reports reside:
In BSM, we navigate to the MyBSM page and create a New Component. We supply the URL of the report we wish to publish.
Finally, verify the html report is viewable via MyBSM.