Get your questions answered from our list of frequently asked questions.
The following information from Vitrium's license keys are communicated back to Vitrium's main server once every 24 hours. The information is strictly summary and statistical information. It does NOT contain any specific details. It's purely top level aggregate info.
For all 3 components:
In addition, the following items depending on the component checking the license:
For content server (ServerAPI):
For EIP/auth server (AuthAPI):
For WebViewer server (WebAPI):
IMPORTANT NOTE: These are the minimum requirements for self-hosting Vitrium Security. Requirements may differ for different use cases. The installed version is only available for Vitrium Security Enterprise.
The Vitrium Security software requires Microsoft IIS and SQL Server. The recommended configuration depends primarily on the volume of the content that will be protected and/or the volume of expected unlocks/views.
It is recommended to set up three hosts:
One or two hosts are acceptable for a test or staging environment, or for a low-volume setup.
Unless otherwise specified, the following components must be installed on the front-end host prior to installing the Vitrium Security software:
Note that the content conversion performance is CPU-bound and also depends on network speed to upload/download the content to/from the server.
Disk space on the front-end host is dictated by the size of the content to be processed and stored:
Vitrium recommends using a SAN or NAS or network share for storing the raw and/or protected content and web viewer converted files (the "repository") in anything but large volume environments. The repository can be located anywhere.
Vitrium does not recommend running the database on the same server as the Vitrium Security software.
Vitrium recommends setting up a separate agent host for protecting content in medium to high volume environments so that this processing does not affect content unlocks and/or admin processes.
Note that the content conversion performance is CPU-bound, and also depends on network speed to upload/download the content to/from the server.
The Vitrium Security software is designed to be load balanced for scalability, redundancy, and ease of maintenance. Session state is persisted all the way to the database so any of the front-end servers can randomly serve requests and perform the security handshake. To set this up, install as many front-end application servers with the same configuration. All of these servers should point to the same SAN or NAS or network share for the content repository and to the same back-end database server. And, the back-end database server can leverage Microsoft SQL Server’s built-in clustering for scalability, redundancy and ease of maintenance.