Hardware and Software Requirements

If you plan to install eSign and run it on premises, review these minimum hardware and software requirements before you installation.

Bare Metal Setup

Described below are all the requirements for a successful installation of an eSign solution over a traditional bare metal infrastructure.

Minimum Requirements

  • 2.3 GHz CPU (4 Cores).

  • 4 GB of RAM dedicated to the JVM.

  • 4 GB of SSD storage SSD (configuration and rotative logs).

Adjust RAM to match your latency requirements, average PDF sizes and the number of concurrent sessions.

Required Software

Verify that you use a supported version of Java before you install eSign.

Software Version

JRE

1.8.0 (with JCE)

Tomcat

8.0
eSign recommends using the OpenJDK Java distribution and using the latest available release of JRE 1.8.

Supported Software

eSign runs on any operating systems that runs a supported Java Runtime Environment (JRE). eSign passed functional testing against the following software and operating systems:

Software Version

OS

Windows Server (2012 R2,2016 and 2019), RHEL 7, Ubuntu 18.04, Alpine 3

JRE

1.8.0 (with JCE)

Container-based Setup

For containerized environments (such as Docker or Kubernetes), below follows the requirements for a successful installation.

Minimum Requirements for eSign

  • 2 GHz vCPU.

  • 4 Gi RAM.

  • 4 GB Storage (if logs are kept inside the container).

Minimum Requirements for Postgres Database

  • 4 GHz vCPU.

  • 16 Gi RAM.

  • 2 GB Storage (pod).

  • 512 GB Storage (pvc).

Required Resources

eSign performs encryptions and signatures with keys that must be exclusive to your organization. For a correct installation the following resources are required:

Resource Details

Singing Certificate

The certificate that will be used to certify certain types of signatures (ex: handwritten, click-2-sign), and will optionally be used to seal finished documents. (see more: Installing a Signing Certificate).

Public Key

A public key used, exclusive to your organization, that will be used to cipher the biometric data associated with a handwritten signature. (see more: Installing an Encryption Key).
eSign might work with other software and operating systems, but those will not be supported. We recommend that you always run eSign on tested software and operating systems versions.

Supported Databases

eSign uses a relational database for its persistence layer. eSign passed functional testing against the following relational databases:

Software Version

SQL Server

2012, 2017, 2019

Oracle

12c

Postgres

9, 10, 11
eSign is expected to work with versions higher that the ones listed above, assuming database providers ensure retro-compatibility. Other database providers are not supported.

Recommended Architecture

In a productive environment we highly recommend redundancy of the application layer (with a minimum of 2 esign instances). On top of the application layer, a load-balancer should exist to distribute the load between the various instances.
All instances are served by a relational database, for which advise redundancy with a fail-over strategy.

The load-balancer requires sticky-sessions/session-affinity.
diagram