Enterprise Vault™ Compliance Accelerator Administrator's Guide
- Overview and latest updates
- Understanding Veritas Surveillance
- Configuring Compliance Accelerator Desktop Client
- Customizing the reviewing action statuses
- Importing configuration data from an XML file
- Specifying the Windows domains with which to synchronize employee details
- Mapping employee properties to Active Directory or Domino directory attributes
- Grouping departments into partitions
- Setting up department attributes
- Setting up custom message types
- Setting Compliance Accelerator system configuration options
- Ad Hoc Searches configuration options
- Diagnostics configuration options
- Document Conversion configuration options
- Export/production configuration options
- General configuration options
- Home Page configuration options
- Hotword Analysis configuration options
- Item Prefetch Cache configuration options
- Item Prefetch Cache (Advanced) configuration options
- Policy Integration configuration options
- Profile Synchronization configuration options
- Random Capture configuration options
- Reviewing configuration options
- Search configuration options
- Security configuration options
- System configuration options
- Vault Directory Synchronization configuration options
- 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
Format of the Dataload.xml file
You can use the Dataload.xml file with both Compliance Accelerator and Discovery Accelerator, so it contains some information that applies to both applications. However, the file is well documented and shows which sections apply to which application.
Table: Primary Compliance Accelerator sections in Dataload.xml file
Section | Defines |
|---|---|
ApplicationVaultStore | Vault stores that the application uses. This section is mandatory. |
CaptureExclusions | Types of items, such as non-delivery reports and out-of-office replies, that Compliance Accelerator is not to capture and add to the review set. |
Employee | Employees to add to the system, their email addresses, and any application roles to assign to them. Employees are identified using the EmployeeID field, which equates to the box in the employee properties page of the Compliance Accelerator client. If you create some profiles using the Compliance Accelerator client and later want to update them using an XML file, ensure that each employee has a unique ID. |
EmployeeGroup | Employee groups, their members, and any application roles that are assigned to each group. |
HotWordCategory | Global hotwords sets. |
Attribute_n_Definition | Identity attributes that, when used in combination with the filter options in the Departments pane, let you hide or show selected departments in that pane. |
Department | Departments. This section includes definitions of the following:
|
Partition | Partitions, and the departments in them. |
Proxy | Delegates for reviewers and compliance supervisors. |
StandardReviewComment | Common comments that reviewers can add to the items that they review. |
The second part of the file describes each XML entry. The last part of the file provides sample entries for a Compliance Accelerator system.
If you use any non-ASCII characters in a dataload file, you must specify the appropriate encoding. For example, you can save a file that contains accented European characters in Unicode format or add the following at the start of the file:
<?xml version="1.0" encoding="iso-8859-1" ?>