Archive Integration Guide › Symantec Enterprise Vault Integration › Configure Enterprise Vault Integration › Configure the Domino Journal Task

Configure the Domino Journal Task

After installing the EV archive agent, you may need to configure the Domino journal task to allow the agent to ingest emails into the Enterprise Vault archive.

To configure the Domino journal task

(This task is not necessary if you are using Enterprise Vault 9.0 SP1)

You must update your Domino journal task configuration file, EVLotusDominoJournalTask.exe.config. The simplest method is to merge an example configuration file supplied with CA DataMinder into your existing configuration file. You may also need to edit the configuration file to reflect the version of Enterprise Vault that you are using.

1. Merge the <assemblyBinding> element from the example configuration file into the <runtime> element of your existing configuration file.

   By default, your existing configuration file is in C:\Program Files\Enterprise Vault on the Enterprise Vault server. The example configuration files are available on the CA DataMinder page of the CA Support Online site. If you do not have an existing configuration file:

   1. Select the appropriate example file (there are separate files for Enterprise Vault 9.0 GA and SP2).
   2. Copy the appropriate entire example file into C:\Program Files\Enterprise Vault.
2. For each assembly in the configuration file, ensure that the newVersion parameter in each <bindingRedirect> element matches the version of Enterprise Vault that you are using (the file contents are shown below).

   If you are using Enterprise Vault 9.0 SP1, no file changes are needed.

   If you are using any other version of Enterprise Vault 9.0:

   1. Locate each <binding Redirect> line in the configuration file:
   2. For Enterprise Vault 9.0 GA, ensure the newVersion parameters are set to:

      <bindingRedirect oldVersion="9.0.1.0" newVersion="9.0.0.0" />
      

      For Enterprise Vault 9.0 SP2, ensure the newVersion parameters are set to:

      <bindingRedirect oldVersion="9.0.1.0" newVersion="9.0.2.0" />
      

      For future, as-yet-unreleased service packs (for example, Enterprise Vault 9.0 SP3), ensure the newVersion parameters match the service pack number. In the case of SP3, ensure the parameters are set to:

      <bindingRedirect oldVersion="9.0.1.0" newVersion="9.0.3.0" />
      

3. Save the changes to EVLotusDominoJournalTask.exe.config

Example configuration file

The contents of the example EVLotusDominoJournalTask.exe.config configuration file are shown below:

<configuration>
  <runtime>
    <generatePublisherEvidence enabled="false"/>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="KVS.EnterpriseVault.LotusDominoInterfaces" 
         publicKeyToken="26c5e2ccf2b9267c" />
        <bindingRedirect oldVersion="9.0.1.0" newVersion="9.0.2.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="KVS.EnterpriseVault.Interop.IndexClient" 
         publicKeyToken="26c5e2ccf2b9267c" />
        <bindingRedirect oldVersion="9.0.1.0" newVersion="9.0.2.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="KVS.EnterpriseVault.Interop.EVContentManagementAPI" 
         publicKeyToken="26c5e2ccf2b9267c" />
        <bindingRedirect oldVersion="9.0.1.0" newVersion="9.0.2.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="KVS.EnterpriseVault.Interop.RetentionAPI" 
         publicKeyToken="26c5e2ccf2b9267c" />
        <bindingRedirect oldVersion="9.0.1.0" newVersion="9.0.2.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>