Enterprise Vault™ Compliance Accelerator Installation Guide
- Introducing Compliance Accelerator
- Preparing to install Compliance Accelerator
- Configuration options for Compliance Accelerator
- Prerequisites for Compliance Accelerator
- Security requirements for temporary folders
- Configuring Intelligent Review API Authentication and Authorization
- Installing Compliance Accelerator
- Installing the Compliance Accelerator server software
- Configuring Compliance Accelerator for use in a SQL Server Always On environment
- Installing Compliance Accelerator in a clustered environment
- Installing the Compliance Accelerator server software
- Appendix A. Ports that Compliance Accelerator uses
- Appendix B. Troubleshooting
- Appendix C. Installing and configuring the Enhanced Auditing feature
- Appendix D. Introducing Veritas Surveillance web client
Configuring a dedicated server for Intelligent Review processing (optional deployment configuration)
Compliance Accelerator supports the installation of multiple Compliance Accelerator Servers in a single Compliance Accelerator environment. The Intelligent Review (IR) services get installed along with the installation of each Compliance Accelerator Server. Every IR component, by default, processes the customers for its own Compliance Accelerator Server.
The
feature enables a single Compliance Accelerator Server to be dedicated to processing all customers for Intelligent Review, irrespective of which Compliance Accelerator Server they are configured on. This option is provided so that the end user can move a load of IR processing to a less-loaded Compliance Accelerator Server if required.To configure a Compliance Accelerator server as a dedicated IR server
- On Enterprise Vault Accelerator Manager, select EVBAADMIN, and open the Server Properties dialog box
- Select the Dedicated IR Server check box adjacent to the Compliance Accelerator server you want to dedicate for Intelligent Review processing.
Note:
There can only be a single Dedicated IR Server in the environment and is supported in a scenario where Configuration Database is shared. Refer to the following example.
Refer to the scenario below.
Server TKVAS has only one customer (CAVAS2).
Server TKWIN2016TEST1 has two customers (CA1 and CA2).
By default, IR 2.0 services on TKVAS will process the customer CAVAS2 and IR 2.0 services on TKWIN2016TEST1 will process customers CA1 and CA2.
However, if you select the TKWIN2016TEST1 server as a Dedicated IR Server, it will serve as the only IR Server in the environment. It will process all the customers - CAVAS2, CA1, and CA2 for Intelligent Review. The IR components on another server TKVAS will not be used for IR Processing. These servers will only verify if there is any work to do. Else, these servers remain dormant. If you change the Dedicated IR Server to some other Compliance Accelerator Server, those services will then start processing Intelligent Review-related work.
Another deployment option is installing an additional Compliance Accelerator server only for IR processing. This server may not have any customers associated with it. For example, in the below sample image, there are 2 servers, where TKVAS does not have any customers and is only used for IR processing.