Enterprise Vault™ Using the Enterprise Vault Analytics Connector
Example configurations for large Enterprise Vault installations
Figure: Multiple Analytics Connector instances each with their own output folder shows an example Enterprise Vault installation that has three instances of the Analytics Connector configured on the same Enterprise Vault server. In this example, each connector instance produces metadata for a different third party application, so each connector has its own output folder.
In Figure: Multiple Analytics Connector instances using the same output folder, each instance of the connector is on a separate Enterprise Vault server. They all produce metadata for the same application, so they all use the same output folder. This configuration could be used, for example, to process different groups of archives that are hosted on different Enterprise Vault storage servers.
Note that the configuration for all the connector instances in these examples exists in the single file, CrawlerPluginsSettings.xml, on the Enterprise Vault server identified by the Vault Site alias.
In a large, busy Enterprise Vault installation, we recommend the following:
Do not place the output folders on the Enterprise Vault server.
The third party application should not run on the Enterprise Vault server.
A suitable location for the output folder may be on the same computer as the third party application that manages that output folder.