Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

A Digizuite installation has four main components

  • Web server
  • Database server
  • Processing server (Digibatch)
  • Asset Storage

Multiple Server Setups

The installation of the components can be split in one, two or more servers and thereby distributing the workload. At least two servers are recommended for production environments.

Note. In this context Small and Large refers to the number of assets and the frequency of use and not directly to the size of company.

Single server setup

It is possible to install and run all components on the same server.  This is typically done during development and for testing or validating scenarios and is not recommended for production.  For example the user experience can be significantly impacted when there is load on asset processing.

Two server setup

The standard low-end environment has two servers where the web server handling the UI is separated from the processing server and thereby minimizing the influence from large jobs on the experience.  The database and storage is then typically installed on the web server.

Four or more

In a large scale setup the components are distributed on seperate servers and thereby distributing the load.  In some scenarios it is also beneficial to add multiple processing servers.

The value in having more than one Web server is limited as the DAM solution typically does not have a high load on this service and it is more often the underlying processing that needs capacity.

Server Requirements

The requirements for the servers depends on what components they have to support.  When components are combined on a single server then the requirements are aggregated.

Web Server

  • Windows Server 2016 or Windows Server 2019
  • Administrative access
  • Connection to SQL server typically on port 1433
  • Open on port 443 HTTPS (or 80 HTTP).  If HTTPS is used then a certificate is required.

Database Server

  • Windows Server 2016 or Windows Server 2019
  • Microsoft SQL Server 2017 or Microsoft SQL Server 2019 or Microsoft Azure SQL can be used as an alternitive.
    • The Edition must be Web (or higher)
    • The SQL Server must use mixed mode authentication
    • TCP/IP has to be enabled
    • It is also required that the full-text filter daemon is installed
  • Administrative access
  • Open on port 1433 Standard SQL connections

Processing Server

  • Windows Server 2016 or Windows Server 2019
  • Administrative access

Storage Server

Digizuite DAM Center supports storage either on local UNC share or as Azure storage.

UNC

  • Windows Server 2016 or Windows Server 2019
  • Administrative access
  • Note when the storage is not on the same server as the web server then a network path (UNC) has to be created with sufficient access rights, see section 2.1

Azure storage

When using Microsoft Azure storage then account details are required - see documentation

  • Storage account name
  • Access key

Server Hardware Recommendations

The required hardware depends on the specific usage, configuration, number of assets, asset types and more.  Only use the following as inspiration and include an assessment of the specific use cases.

Single server

(no recommendations)

Two servers 


Web Server (SQL + Storage)Processing
RAM

(Min 16Gb) 28Gb  

(Min 8Gb) 16Gb
CPU

(Min 4 Cores) 8 Cores

4 Cores

Four servers - large enterprise


Web ServerSQL ServerProcessingStorage
RAM

(min 8Gb) 16Gb  

(Min 16Gb) 32Gb

(Min 8Gb) 16Gb8 Gb
CPU

(Min 4 Cores) 8 Cores

8 Cores4 Cores4 Cores

Advanced server setup

CDN

If the solution is used to server images, videos and documents to a large audience via e.g. a web site or social media the a CDN which helps distributing and caching the assets through their network.  See supported CDNs.

SSO

Many companies can benefit from a centralized management of users.  See supported SSO solutions.

Load Balancing

Digizuite supports load balancing on both web and database servers. For such setups, the number of servers increases. These setups are used for production environment where uptime and response times are very critical.


  • No labels