Error message

  • Deprecated function: Return type of DatabaseStatementBase::execute($args = [], $options = []) should either be compatible with PDOStatement::execute(?array $params = null): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2244 of /home/techwhitepapers/public_html/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/techwhitepapers/public_html/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/techwhitepapers/public_html/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/techwhitepapers/public_html/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/techwhitepapers/public_html/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home/techwhitepapers/public_html/includes/database/database.inc).
Published Date: Oct 03, 2014

Maximizing Uptime for Mission-Critical File Transfers: Availability and Scalability for Managed File Transfer Deployments.

This whitepaper provides guidance on common high-availability and scale-out deployment architectures, and discusses the factors to consider for your specific business environment. Three basic models are described for deploying an on-site managed file transfer (MFT) solution. The attributes of each option are described; each has pros and cons and offers a different balance of cost, complexity, availability, and scalability. The paper explains that, no matter how reliable each model is, any deployment can experience outages. The recommendation is to use clustering services to protect your data when the inevitable hardware, software, or network failures occur.

 

Keywords: clustering, uptime, failover, MFT, network failure, high volume, scale-out configuration, SLA, HA cluster, high availability, load balancer, mission-critical transfers, active/passive, EDI

Download Here

We are constantly expanding our library of resources. Fill in your information here to download your whitepaper and to receive important TechWhitePapers updates: