Installation Prerequisites

Required software products

64-Bit systems

ImageVault only supports 64-bit systems

Operating system

Any of the following is required

  • Azure Web Application (SKU Basic or greater*)
  • Microsoft Windows Server 2016 (IIS 10)
  • Microsoft Windows Server 2012 R2 (IIS 8.5)
  • Microsoft Windows Server 2012 (IIS 8)
  • Microsoft Windows Server 2008 R2 (IIS 7.5)
  • Microsoft Windows Server 2008 (IIS 7)

Note: Can also be run on non server OS but not supported for production.

* Basic is required since it is the lowest SKU that supports the always-on feature.

Web server (if not Azure)

Any of the following must be installed as part of the Windows Server installation:

  • Microsoft Internet Information Services (IIS) 10
    • Requires the role Web Server (IIS)/Web Server/Application Development/ASP.NET 4.6
  • Microsoft Internet Information Services (IIS) 8.0 - 8.5 (Windows Server 2012/Windows Server 2012R2)
    • Requires the feature Internet Information Services/World Wide Web Services/Application Development Features/ASP.NET 4.5
  • Microsoft Internet Information Services (IIS) 7.5
  • Microsoft Internet Information Services (IIS) 7.0

.NET

Microsoft .NET Framework 4.6 is required

Visual C++ runtime

Visual C++ 2010 Redistributable Package (64 bit) must be installed. (This is not a requirement on azure installations)

SQL Server

Any of the following versions of SQL Server must be installed and running:

  • SqlServer (Azure)
  • Microsoft SQL Server 2008 64 bit
  • Microsoft SQL Server 2008 R2 64 bit
  • Microsoft SQL Server 2012 64 bit
  • Microsoft SQL Server 2014 64 bit

You need to have an empty or existing and compatible ImageVault database available when running the ImageVault setup.

Out-of-process cache (optional)

If you intend to use load balancing on your ImageVault installation, you need to have a out of process cache (a Redis cache for example).

Browser for accessing ImageVault UI

The following browsers are supported:

  • Microsoft Internet Explorer, version 9 or later. (We recommend using at least Internet Explorer 10)
  • Mozilla Firefox, latest
  • Google Chrome, latest

Recommended Hardware Requirements

This guideline presents the hardware recommendations for ImageVault 4 in two typical scenarios. Since a web applications general performance depends on a lot of varying variables, like amount of load and type of clients involved (viewer/editor), it is impossible to make a universal specification of hardware, required for a certain situation. So, this document focuses on two typical scenarios: A small- and a large installation. Note that the following specifications is recommendations, the software might work satisfactory with less, in certain situations.

A small installation

Typically, a small installation is made up by one Core service instance, providing converted media to a site with peak load below 500 requests/s. In this scenario, it is possible to install ImageVault and Episerver on the same server.

ResourceMinimal requirement
CPUSingle core processor @ 2 GHz
Memory8 GB
Hard drive4-16 GB of free space (starting size for storage of media)

A large installation

One Core, providing converted media to multiple sites or for both extranet + intranet with a peak load above 500 requests/s. In this scenario, ImageVault Core Service is, typically, installed on a separate server.

ResourceMinimal requirement
CPUDual core processor @ 2 GHz
Memory16 GB
Hard drive4-16 GB of free space (starting size for storage of media)

Disk space considerations

The recommended amount of free space on the hard drive depends on the amount of media, stored in ImageVault. The uploaded and converted media files, smaller than 1MB, are stored in the database while the larger files are stored on disk.

As the recommendation is to upload high resolution originals to ImageVault, the amount of disk needed might rapidly grow as more assets are added to the library. Hence we suggest disk space should constantly be monitored and extended to conform to the needs.

Load-balancing ImageVault

If a site is very media intense and requires a lot of media conversions on-the-fly, our recommendation is to balance the load between multiple instances. Typically, one media conversion corresponds to the delivery of 3 converted media assets, concerning response time. Read more about configuring load balancing

comments powered by Disqus