Follow

Summation Pro Installation Type

Created by: Tod Ewasko
Created date:
Last Updated date:

This document is intended to help correctly configure environments for long term success and prevent hardware related bottlenecks. You need to use this as a supplement to the specification guide.

Component descriptions:

  • MAP = End User Website
    • Includes IIS Application Pool ADG.MAP.APPPOOL
  • WCF = This will host the majority of Services used by Accessdata software (Service List below as of 6.0)
    • Accessdata Async Processing Services
    • Accessdata Business Services Common
    • Accessdata Ediscovery Business Services
    • Accessdata Orchestration Service
    • Accessdata RTT Business Services
    • Accessdata Work Manager (WM)
  • SS = Site Server (Service below as of 6.0)
    • Accessdata Site Server
  • MS SQL = Microsoft SQL Server
  • FTK = Forensic Tool Kit
  • EP = Local Evidence Processor
  • DPE = Distributed Processing Engine
    • Accessdata Processing Engine Service
  • DPM = Distributed Processing Manager
    • Accessdata Processing Manager Service

Single Server

Description: Single Server install most commonly used for mid-market accounts on a budget. Most commonly installed with local storage. With this type of install recommend processing, imaging and productions when users are not in the system. Use this configuration for light review with smaller caseload and processing after hours.

  • Server 1: MAP, WCF, EP, MS SQL, FTK
    • SQL set to 50% Memory
    • EP Throttling on

Two Server

Option a

Description:  This two Server install is a step up from the single Server with a dedicated SQL Server will allow for larger case size. With this type of install we recommend processing, imaging and productions when users are not in the system. Use this configuration with large cases with minimal processing needed during the work day with moderate internal reviewing.

  • Server 1: MAP, WCF, EP, FTK
    • EP throttling enabled.
  • Server 2: MS SQL 
    • SQL set to 75% Memory

Option b

Description:  This two Server install is designed to offload processing to another server to allow 24 hour processing without affecting users. Use this configuration with moderate internal reviewing and large amount of processing.

  • Server 1: MAP, WCF, DPM, MS SQL, FTK
    • SQL set to 50% Memory
  • Server 2: DPE

Three Server

Option a

Description:  This three Server install is designed to offload processing to another server to allow 24 hour processing without affecting users and a dedicated SQL Server for larger cases. Use this configuration with heavy processing and heavy review internal reviewing.

  • Server 1: MAP, WCF, DPM, FTK
  • Server 2: DPE
  • Server 3: MS SQL 
    • SQL set to 75% Memory

Option b

Description:  This three Server install is designed to allow users to connect via HTTPS on a public web address and a dedicated SQL Server for larger cases. Use this configuration with light processing and heavy review external review. Depending on resources on Server 1 you may experience end user slowness while processing.

  • Server 1: WCF, EP, FTK
  • Server 2: MAP
    • DMZ Zoned web server
  • Server 3: MS SQL 
    • SQL set to 75% Memory

Option c

Description:  This three Server install is designed to allow users to connect via HTTPS on a public web address and a dedicated DPE Server for heavy processing. Use this configuration with heavy processing and medium review external review

  • Server 1: WCF, DPM, FTK, SQL
    • SQL set to 50% Memory
  • Server 2: MAP
    • DMZ Zoned web server
  • Server 3: DPE

Four Server

Option a

Description:  This four Server install is designed spread the processing over 2 servers to allow 24 hour processing without affecting users and a dedicated SQL Server for larger cases. Use this configuration with heavy processing load and heavy review internal reviewing.

  • Server 1: MAP, WCF,  DPM, FTK
  • Server 2: MS SQL
    • SQL set to 75% Memory
  • Server 3: DPE
  • Server 4: DPE

Option b

Description:  This four Server install is designed to allow users to connect via HTTPS on a public web address, a dedicated SQL Server for larger cases and offloading processing to a dedicated processing server. Use this configuration with heavy processing load and heavy review external review

  • Server 1: WCF, DPM, FTK
  • Server 2: DPE
  • Server 3: MS SQL 
    • SQL Set to rule
  • Server 4: MAP
    • DMZ zoned web server
Was this article helpful?
3 out of 3 found this helpful
Have more questions? Submit a request

Comments

  • Avatar
    Kursad

    In this guide AsyncProcessingServices jobs initiated by MAP interface still run locally on the machine with EP installed and set to (no local processing) right? All other processing is handed by the WM to the DPE and subsequently distributed to the EP's?
    So in the 4 server scenario:
    Running OCR using MAP would run on SERVER1 and running a processing job using the Summation or FTK(LAB) interface would be run by the Server2 and then pushed to the EP on Server1 by the DPE?

  • Avatar
    Tod Ewasko

    Great Question. All EP processing is pushed to the DPE Via ProcessingHost, this includes Async, Work Manager and FTK jobs.

    For Async
    Your Async Web.config "ProcessingManager" determines this and should be on localhost is configured properly. There are additional endpoints in this file referencing processing manager that should be changed to localhost.

    For Work Manager
    Your Infrastructure.Workexecution.exe.config "ProcessingManager", same applies as above, this should be on localhost.

    FTK
    Nothing needs to change, it automatically looks locally for processinghost.

    I will create a KB with Processing Manager information in it, with the above detail.

    NOTE: You should never have 2 Processing Hosts (locally installed EP) or Distributed Processing Managers (DPM) in any environment. Any of the following can cause corruption to the indexes and database, examples of what you shouldn't do:
    1 Processing Host and 1 DPM
    2 DPMs
    2 Processing Host

  • Avatar
    Kursad
    Kursad Delete 2 minutes ago
    

    Thank you Tod. I am just trying to figure out the best distribution on our current setup. ( keeping in mind the HW specs of the servers ) So I have a followup question.

    Sorry if this is not the right place to ask :

    Is this setup possible in any way? :

    SERVER 1: Running all Summation components + SQL server
    SERVER 2: Running FTK LAB interface
    SERVER 3: Running just a distributed processing client
    SERVER 4: Running just a distributed processing client

    And then configure it all so that :
    - Summation Processing and FTK LAB processing is distributed across SERVER 1 and SERVER 2 and SERVER 3 AND SERVER 4.
    - FTK LAB on SERVER 2 can run jobs only on SERVER 2 and SERVER 3 AND SERVER 4 (not using SERVER 1 when a lot of users are reviewing)

  • Avatar
    Kursad

    I know Tod is working on and will be posting KB article soon. But is it possible to get more information in this feature/setting ? "EP Throttling on"

  • Avatar
    Tod Ewasko

    EP Throttling lowers the priority of the evidence processing in task manager. It is designed for single server installs to limit affecting users as much as possible.

  • Avatar
    Kursad

    Hi Tod, so is it recommended to just add the processing engines to the
    Processing.Host.exe.config . If so could you please post a few lines on the syntax to add multiple engines.

    Or is it still better to utilize a Distributes processing manager?

  • Avatar
    Tod Ewasko

    It is recommended to use processinghost config change, the instructions for this can be found in our multi-server install here: https://support.accessdata.com/hc/en-us/articles/203219539-Summation-Pro-5-6-1-Install-Guides

  • Avatar
    Kursad

    I am sorry I should read more carefully. It's well documented.

Powered by Zendesk