Summary

This document describes the process for installing the Tracking Data Destruction (TDD) plug‐in for E2.

Prerequisites

The following is needed before starting the plug‐in installation procedure.

·         A download of the “E2P” plug‐in installation file, which is attached to this page.

·         A configured E2 server.

·         Local or domain administrator privileges on the Windows server where E2 is to be installed.

·         ‘sysadmin’ privileges on the Microsoft SQL Server database instance where the E2 database resides.

Known Issues

•     There is an issue with the plug‐in installation framework that prevents plug‐ins from properly performing necessary file copy operations. Pre‐ and post‐installation configuration steps have been added to work around this issue.

Pre-Installation Configuration

File Copy Work-Around

It is necessary to perform a manual file copy before installing the TDD plug‐in.

1.       If they do not exist, create the directories  C:\Program Files (x86)\Corp Ten International\Ember2\Install\ and  C:\Program Files (x86)\Corp Ten International\Ember2\HostBinBackup\

2. If you have not done so already, grant "IIS AppPool\Evolution" read and write access to all files and subfolders of C:\Program Files (x86)\Corp Ten International\Ember2\

3.       Browse to C:\Program Files (x86)\Corp Ten International\Ember2\Website\bin.

4.       Select all of the files within the bin directory and perform a Copy.

5.       Browse to C:\Program Files (x86)\Corp Ten International\Ember2\HostBinBackup.

6.       Perform a Paste, overwriting all existing files.

Installation Procedure

This procedure describes how to perform a full installation of Evolution on one server.

Ensure that the TDD plug‐in file has been uploaded to the Evolution server and unzipped, if

necessary.

1.       Copy the Tracking Data Destruction Plugin.e2p file into the Evolution install folder at C:\Program Files (x86)\Corp Ten International\Ember2\Install.

2.       Make note of the "Date Modified" of the plugin .dll and .pdb files.  (
In C:\Program Files (x86)\Corp Ten International\Ember2\Website\bin  they are TrackingDataDestruction.dll,
TrackingDataDestruction.pdb,
TrackingDataDestructionCore.dll, and
TrackingDataDestructionCore.pdb)

3.       Launch Internet Information Services (IIS) Manager and select Application Pools.

4.       Restart the E2 application pool by selecting Evolution in the list and clicking on Stop, wait 10 seconds, then click Start.

5.       The Tracking Data Destruction Plugin.e2p file is consumed and its components are installed to the server.

6.       If the "Date Modified" dates of the .dll files and .pdb files noted in step 2 have not been updated by  installation of the new .e2p file at this point, delete the .dll and .pdb files from C:\Program Files (x86)\Corp Ten International\Ember2\Website\bin and repeat the steps starting from step 2.

7.       Follow the procedure for Post‐Installation Configuration.

Post‐Installation Configuration

It is necessary to perform a manual file copy after installing the TDD plug‐in.

1.       Browse to C:\Program Files (x86)\Corp Ten International\Ember2\Website\bin.

2.       Select all of the files within the bin directory and perform a Copy.

3.       Browse to C:\Program Files (x86)\Corp Ten International\Ember2\HostBinBackup.

4.       Perform a Paste, overwriting all existing files.

Configure the TDD Log Output Directory

The Tracking Data Destruction plug‐in creates log files recording the delete operations that are performed. These logs must be placed in a directory that SQL Server has permissions to write too. It is recommended that a separate directory be created for this purpose; however, any directory with the proper permissions will work.

To configure a directory with permissions for SQL Server, add Read, Write, and Modify permission for the SQLServerMSSQLUser&SERVER&INSTANCE user account, where SERVER is your server name and INSTANCE is your SQL Server instance name (MSSQLSERVER by default).

1.       Launch SQL Server Management Studio as an Administrator and connect to the database instance where the Evolution database resides.

2.       Create a New Query and paste the following script into the new query window. Ensure that quotation marks have copied correctly. Ensure that the highlighted section matches a valid location on your server and that the SQL Server user account has permission to write to that directory. 

USE evo_dev
EXEC evo.p_Configuration#Updater
 @ConfigurationSection =N'PluginTrackingDataDestruction'
,@ConfigurationName=N'DeviceAuditLogOutputDirectory'
,@ConfigurationValue=N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA'
,@ConfigurationUpdated='2015‐12‐16'
,@ConfigurationDeltaStatusUserID_LastUpdatedBy=1

The SQL Server default data directory is noted here as an example, but will vary between versions of SQL.