Administration

General

Standard structure of the server

For the COGLAS Web WMS installations, an infrastructure of the following virtual servers is usually used:

  • Production system – one application server for the COGLAS web application and three redundant database servers for MongoDB.
  • Test system – a server running both the COGLAS application and MongoDB.
  • Port 443 must be enabled for access to COGLAS.

Hardware requirements per server

Production system – application server

vCPU RAM OS Diskspace Programm
6 32 GB Win2019 150 GB Teamviewer, Notepad++, Processexplorer, Robot3T, HTML5 capable browser, 7zip, IIS Manager

Production system – database server

Server vCPU RAM OS Diskspace Programm
3x* 4 32 GB Win2019 300 GB Teamviewer, Notepad++, Processexplorer, Robot3T, HTML5 capable browser, 7zip, latest MongoDB version

* The use of 3 DB servers is required for the replica set, which can compensate for a longer downtime of one DB server. Furthermore, when using 3 DB servers, DB maintenance can be performed without downtime.

Test system

vCPU RAM OS Diskspace Programm
6 32 GB Win2019 200 GB Teamviewer, Notepad++, Processexplorer, Robot3T, HTML5 capable browser, 7zip, IIS Manager, latest MongoDB version

System requirements devices

The COGLAS HTML5 web application can be run on any operating system (OS) and supports at least the listed web browsers.

Browser Google Chrome* Mozilla Firefox* Microsoft Edge
from version 73.0 61.0 44.0

* recommended

The following hardware components have proven themselves in use:

Tablets Handhelds Scanner Printer
Flatman 10,1″ Tablet (W10 IoT) Flatman 5,98″ Handheld-Tablet (W10 IoT) Zebra DS3678-ER ZT22042-T0E200FZ
XPLORE XSlate D10 (Android 6.0.1) XPLORE M60 (Android 8.x) Zebra RS6000
Advantech DLT-V6210 (WES7/W10 IoT) Zebra TC25Plus (Android 7.x) MARK 2 mid range

Data availability

System reliability of 99.95% to 30 calendar days in the Open Telekom Cloud (OTC).

Redundant database system by three database servers, the servers synchronize permanently in Primary → Secondary principle (Primary performs all accesses, Secondary mirrors the accesses). In the event of a primary instance failure, a secondary instance is selected as a replacement within a few seconds and takes over the tasks. There is no interruption for the user in this process.

Data security

On-Premises (Local Installation)
A dump of the database can be pulled every n-hours and can be overwritten after m-hours.
Optional backup methods to be set up (the customer must provide the additional hardware needed for this):

  • Hot-Backup
  • Backup software for snapshots of the servers (e.g. Nakivo).

COGLAS Cloud (OTC / Open Telekom Cloud)
MongoDB is backed up as a dump every two hours. These fuses are held 24h.

A snapshot backup of the hard disks is performed every 24h. The saved snapshot of the first day of the month is available until the first day of the following month. The snapshots of the last four days are saved and retained.

Requirements for printer control from the cloud / PrintController / MaterialFlowController

With the PrintController you can control your local printers directly from the cloud.

vCPU RAM OS Diskspace Programm
2 8 GB Win2019 30 GB Teamviewer, Sumatra PDF, Seagull Drivers

Additional requirements:

  1. A server provided by you at your site so that we can install our PrintController locally
    • Remote access must be provided to COGLAS.
    • Windows login and local admin rights are available
    • With at least Microsoft .NET Framework 4.8
    • The server needs a permanent connection with our OTC server
  2. The printers are set up on the server and accessible via test print.
    • Customer must provide printer driver
  3. We needed Sumatra PDF, but we like to install it ourselves.
  4. In addition, the workstations must be activated and configured in COGLAS.