Skip to content
+90 850 885 27 43 info@argeict.com

Business applications

Electronic document management system (EDMS) server and cloud infrastructure

ARGE ICT builds, backs up, and monitors the server, database, and file store behind the EDMS (known in Türkiye as EBYS) you choose, in a virtual private cloud (VPC) on ARGE Cloud or in your own environment.

An electronic document management system (EDMS) keeps an organization's incoming and outgoing correspondence, scanned documents, and approval workflows in one place. Registering, routing, signing, and archiving all depend on that record. In Türkiye the system is called EBYS (elektronik belge yönetim sistemi). When the EDMS server stops, document intake and signing stop with it, and if the database or file store is damaged, past correspondence cannot be reached.

We do not sell EDMS software or provide licenses or functional support. The organization chooses the software; we build and operate the server, database, file store, network, backups, and security it runs on. The software vendor manages the application, and we manage the infrastructure. If you use Bimser eBA, see also our eBA infrastructure page.

When you need it

  • The EDMS server runs on an old machine in a basement or a branch office and needs replacing.
  • The disk holding scanned documents fills up every year, and nobody has worked out when it will run out.
  • Backups are taken, but nobody knows whether the database and the document files belong to the same point in time.
  • A restore has never been tried, so it is unclear how much correspondence would come back after a failure.
  • Scanners and users at branches reach the central server over an unprotected connection.
  • No log shows who opened which document and when.

The layers of EDMS infrastructure

Most EDMS products have several layers. Which components are needed depends on the software's architecture, and before installation we confirm the versions it requires in the vendor's documentation.

  • The web and application server that users reach with a browser or client program.
  • The database that holds the document records. Depending on the vendor, this is SQL Server, Oracle, or PostgreSQL.
  • The file store that holds scanned documents and attachments. This part grows the most over time.
  • The full-text search and optical character recognition (OCR) service. OCR turns text in a scanned image into searchable text.
  • Active Directory or LDAP for sign-in, and a mail server for notifications.
  • Connections to registered electronic mail (KEP) and signature services, and network access for scanners at branches.

Official correspondence, KEP, and e-signature

For public bodies and those who correspond officially with them, the framework is the Regulation on Procedures and Principles to Be Applied in Official Correspondence (Resmî Yazışmalarda Uygulanacak Usul ve Esaslar Hakkında Yönetmelik, Official Gazette No. 31151, June 10, 2020). The regulation takes electronic preparation, signing, delivery, and storage of documents as its basis and defines the EDMS. How you must store each type of document depends on this regulation and your organization's retention plan, and we do not give legal opinions on it.

The e-Yazışma Technical Guide (e-Correspondence Technical Guide), published by the Digital Transformation Office of the Presidency, defines the package structure, metadata, signature, and encryption format of electronic correspondence. The letter, its attachments, and its metadata travel in one package (the e-Yazışma Package), which the receiving EDMS can read without human intervention. TS 13298, the Turkish Standards Institution's standard for electronic records management, is another yardstick against which EDMS software is assessed. Compliance of the software with these is the vendor's responsibility, and we do not issue conformity certificates.

Correspondence between institutions is also carried out through registered electronic mail (KEP), which you obtain from a KEP service provider; we are not one. E-signatures and mobile signatures sit on the user side. Institutions that send many letters a day use an electronic seal. We do not sell any of these. We prepare the EDMS server's secure outbound path to KEP and signature services, and the server-side environment for the signing components.

Scope

  • Server and database. We install the application and database servers and apply patches on a schedule. We size resources by number of users, daily document volume, and the volume of scanned documents.
  • File store. We build the storage for scanned documents and track its growth. We renew the capacity plan each year based on the trend and warn you before the disk fills.
  • Backup. We back up the database and the file store at the same point in time and write the backups to the isolated backup area on ARGE Cloud. We test restores and report the result in writing.
  • Access and monitoring. We assign permissions by role and collect access logs and firewall logs in a central log system (SIEM). A web application firewall (WAF) protects the application, and access from outside the organization goes through ARGE ZTNA or a VPN. The infrastructure is monitored 24/7; who looks at which alert, and within what scope, is written in the contract.
  • High availability. Optionally, we build a cluster in which a second server takes over if one fails. The need depends on your user count and how well your correspondence can tolerate downtime.

Backup and archive for EDMS

The most common EDMS mistake is backing up the database and the file store at different times. After a restore, a record exists without its document file, or a file exists without its record. We therefore take both at the same point in time and restore them together.

The volume of scanned documents grows over the years. As far as the vendor supports it, we can move documents from earlier years off the live system to a cheaper storage tier. This shortens the backup window and shrinks the live disk, while older documents remain reachable. How long each document is kept follows the organization's retention plan, and we do not set those periods.

Documents contain personal data. Under Law No. 6698 on the Protection of Personal Data (KVKK), we build the infrastructure side: role-based access, encryption, access logs, and an isolated backup. The legal decisions rest with the organization, and our service alone does not meet your KVKK obligations.

Head office and branch connectivity

Users and scanners at head office and branches reach the EDMS server in one of three ways. The right one depends on the type of line and the number of branches.

  1. Your carrier's MPLS line. The provider's private line links head office and branches. MPLS carries traffic without crossing the internet.
  2. MPLS with a private link to ARGE Cloud. The same line is extended to ARGE Cloud. Even when the EDMS runs in the cloud, documents from a branch reach the server without crossing the internet.
  3. IPsec when there is no MPLS. Over the existing internet line, we set up an encrypted IPsec tunnel with SD-WAN capable routers and firewalls. SD-WAN manages several lines and steers traffic to the better one.

Our page on connecting head office and branches covers these options in more detail. We also assess together whether a branch needs a backup line.

Out of scope and limits

We do not sell EDMS software licenses, we do not provide functional support for the software, and we are not an authorized partner of EDMS vendors. Whether the software complies with the regulation, the e-Yazışma Technical Guide, and TS 13298 is the vendor's matter, and we are not a certification body. KEP service, e-signature certificates, mobile signatures, and electronic seals come from the relevant providers. Retention periods, destruction decisions, and privacy notices are legal matters, so please consult your legal counsel.

How we work

  1. We map where the EDMS server runs today, the number of users, daily document volume, the volume of scanned documents, and the branches.
  2. We confirm the software vendor's server and network requirements in its documentation and propose the design and capacity plan in writing.
  3. Before moving, we back up the database and file store and test restoring them together. We make the switch outside working hours and watch document intake and the signing flow during the first days.
  4. We report backup results and storage growth; the reporting frequency is written in the contract.

Service models

In both models we design the architecture around your organization: the needs of the EDMS, your user count, daily document volume, and the volume of scanned documents. We size processors, memory, disk, and network to your actual workload and make a forward-looking capacity plan based on your growth rate.

  1. On ARGE Cloud: The EDMS servers run on infrastructure we operate in a data center in Istanbul, in a VPC dedicated to you. If you wish, we also build a disaster recovery site, the second environment where work continues when the main system stops. It is optional.
  2. In your own environment (on-premises): We design and manage the server layout. As needed, we size the hardware and help with its purchase, handle operating system and database license planning, install the system, and take on management, maintenance, and monitoring of the environment.
  3. Combined: The system runs in your environment, and backups sit in the isolated backup area on ARGE Cloud.

Technologies we use: Windows Server · Linux · Microsoft SQL Server · PostgreSQL · Active Directory · IPsec · SD-WAN · MPLS · SIEM · WAF

For more on backups and the second environment, see our backup and disaster recovery page.

Frequently asked questions

Do you also provide the EDMS software? No. The organization chooses the software and buys the license from the vendor. We build and operate the server, database, file store, network, backups, and security. Configuring the software and functional support stay with the vendor.

Can you move our current EDMS to ARGE Cloud? We can if the vendor supports the server and database version. Before moving, we back up the database and file store and test restoring them together. Installing and configuring the software stays with the vendor; we prepare the environment, move the data, and set up the network connection.

Can a restore bring back a record without its document? It can happen if the two are backed up at different times. That is why we back up the database and file store at the same point in time, and in the restore test we restore both together and check that the documents open. We report the result in writing.

Does this service make us compliant with KVKK? No. The organization decides on what basis documents are processed and how long they are kept. We only build the infrastructure measures: role-based access, encryption, access logs, and an isolated backup.

How much will storage grow, and how do you plan for it? The volume of scanned documents differs from one organization to another. We first work out today's volume and the yearly trend, then track growth and update the capacity plan. Moving earlier years to cheaper storage is also an option, as far as the vendor supports it.

Talk to us about EDMS infrastructure

Tell us which EDMS software you use, your user count, and your document volume; we reply within 1 business day.

Request an infrastructure call