Description

Enterprise Vault (EV) Compliance Accelerator (CA)/Surveillance from version 15 and higher includes Power BI Reporting. Using Power BI Reporting requires configuring an endpoint and then running the Report templates using the endpoint information. Below is a quick reference guide to Power BI Reporting for Surveillance.

The log excerpts, information and/or screenshot(s) below were taken from a non-production test lab environment and are used for example purposes only.

1. Open the Surveillance Help and navigate to Working with reports.

2. Under Enhanced Reporting, follow the Configuring a reporting endpoint section to create a Reporting endpoint if not already created. Verify the IP addresses of the computers from where Power BI will be run are added. Note the Endpoint Base URL, the Primary Key and Secondary Key. To view the keys, click on the vertical ellipses at the end of the row and select Show/Hide Keys.

Example from a lab:

Endpoint Base URL: https://CA.evrpslab.com/Reporting
Primary Key: 2d3ba115b9cf4829853eaf4e8ead40f9
Secondary Key: 899f9568b9914fc1b376a6032c248c0e

Note that the keys expire 90 days after creation. The expiration date can be seen by clicking on the Toggle Selection List dropdown button, then selecting the Primary Key expiry date and Secondary Key expiry date options. To renew the keys, click on the vertical ellipses at the end of the row | Edit | click Regenerate next to each key.

3. Install the 64-bit version of Power BI Desktop on the computer where the Reports need to be run.

4. Review the Configuring a Power BI Template for reporting or Managing Power BI Templates for reporting APIs section in the Surveillance Help for information on how to download the Power BI Report templates to the computer where the Reports need to be run:

4.1. In the Surveillance UI go to Configuration | Reporting Endpoint | PowerBI_Templates.

4.2. Go to the download location and extract the PowerBITemplates.zip file that contains Power BI templates to a folder on the computer where the Reports need to be run.

5. To run the Power BI Reports, open the required Power BI template and configure as indicated for each report in the Managing Power BI templates for reporting APIs section of the Surveillance User Guide. Hovering over the I in each parameter field will provide more information on what is needed. Some Reports require a request to be submitted, then the ReportID from the request is used to view the actual Report.

The TEMPLATE- Evidence Of Review By Department - View Report Data is used in the following examples.

5.1. First open the TEMPLATE - Evidence Of Review - Submit report request template in Power BI.

5.2. Enter the information as prompted and click Load.

5.3. In the OData Feed pane, select Basic and enter the following information then click Connect (note there may be multiple prompts where the below information needs to be entered):

User name: ReportingApiUser
Password: enter either the Primary Key or Secondary Key
Select which level to apply these settings to: select the bottom level /odata/EvidenceOfReviewAsync

5.4. Note the Report ID as listed in the Evidence of Review report generation request has been submitted with below details. page. The Report ID will be in the format 1234ABCD-12AB-34CD-56EF-123456ABCDEF. Right-click on the Report ID | Copy | Copy Value.

Example Report ID from a lab: 3f2eaefd-10a2-4b3c-8801-67ea81e8be2d

5.5. Then open the TEMPLATE - Evidence Of Review By Department - View Report Data template in Power BI.

5.6. Enter the information as prompted and click Load. The Report ID will be the Report ID generated above.

5.7. In the Access Web Content pane, select Basic and enter the following information then click Connect (note there may be multiple prompts where the below information needs to be entered):

User name: ReportingApiUser
Password: enter either the Primary Key or Secondary Key
Select which level to apply these settings to: select the bottom level /odata/EvidenceOfReview

5.8. The Report should now be displayed.

Possible Issues

- If one or both of the following messages are seen, follow these steps:

Evidence Of Review
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

Report Status Message
OData: Request failed: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

1. Enter the Endpoint Base URL in a browser.

2. Right-click on the Not Secure button in the Address Bar | click on the icon to the right of Certificate Details | go to the Details tab | Export | save the certificate as a Base64-encoded ASCII, single certificate (*.perm;*.crt) file | Close the browser.

3. Then open the certificate location in File Explorer | right-click the certificate | Install Certificate | Local Machine | Place all certificates in the following store | Browse | Trusted Root Certification Authorities | OK | Next | Finish.

- If issues are seen regarding authentication, clear the Power BI cached credentials as follows: File | Options and settings | Data source settings | down-arrow next to Clear Permissions | Clear All Permissions.

- Basic Authentication step repeatedly prompts for the credentials. This is typically caused by not having the IP address of the computer where Power BI is installed in the IP Address allowed list in the endpoint.

- Mashup Error 1

Microsoft.Mashup.Engine1.Library.Resources.HttpResource:Request failed:
OData Version: 3 and 4, Error: The remote server returned an error: (500) Internal Server Error. (Login failed for user 'DOMAIN\COMPUTERNAME$')
OData Version: 4, Error: The remote server returned an error: (500) Not Found. (Login failed for user 'DOMAIN\COMPUTERNAME$')
OData Version: 3, Error: The remote server returned an error: (500) Not Found. (Login failed for user 'DOMAIN\COMPUTERNAME$')

This occurs when the Application Pool Identity is set to something local such as Network Service or ApplicationPoolIdentity instead of a domain account. Check the EnhancedReportingDataApi Application Pool in IIS on the CA/Surveillance server.

- Mashup Error 2

Microsoft.Mashup.Engine1.Library.Resources.HttpResource:Request failed:
OData Version: 3 and 4, Error: The remote server returned an error: (404) Not Found. (Not Found)
OData Version: 4, Error: The remote server returned an error: (404) Not Found. (Not Found)
OData Version: 3, Error: The remote server returned an error: (404) Not Found. (Not Found)

This is likely caused by the Surveillance certificate not being installed on the computer where Power BI is installed (see above).