Enterprise Vault™ Compliance Accelerator Administrator's Guide
- Introducing Compliance Accelerator
- Introducing Veritas Surveillance
- Creating and viewing reports
- About the Compliance Accelerator reports
- Accessing data through the Microsoft SQL Server Reporting Services (SSRS)
- Enhanced reporting
- Accessing reports through the OData web service
- Configuring a Power BI template for reporting
- Appendix A. Troubleshooting
- Veritas Surveillance user interface user interface is not displayed properly in non-English environment
- Issues with the random sampling of items
- Display issues when you open a Compliance Accelerator website in Internet Explorer 10 or later
- Vault stores not displayed in the Veritas Surveillance web client
- TNEF-encoded attachments to Internet Mail (.eml) messages may not be readable after you export the messages from a review set
- Synchronization errors after you rename the SQL Server computer
- Performance counter errors when the Accelerator Manager service starts
- SQL Service Broker warning when restoring a customer database to a different server
- Error messages when the Intelligent Review (IR) API authentication and authorization fails
- Known issues after enabling FIPS
Enhanced reporting
Compliance Accelerator has introduced reporting endpoint APIs to improve reporting and analytics capabilities.
The currently available reporting endpoint APIs are:
Departments
Users
UserRoles
Roles
ItemMetrics
EvidenceOfReviewByDept
EvidenceOfReviewByUser
To utilize these reporting endpoints, the administrator must configure them in Compliance Accelerator. Upon successful configuration, Compliance Accelerator generates a base URL and API keys to ensure secure access to the reporting endpoints.
To securely access data, the primary or secondary API keys serve as passwords, unique to each reporting endpoint configuration. The specified IP addresses during the configuration of these enhanced reporting endpoints are authorized and permitted for API calls.