1. Introduction

eMAM is an all-in-one, web-based Digital Asset Management (DAM) software system designed to organize, share, and collaborate digitized information such as audios, videos, images, and documents. EMAM has taken a ground-breaking approach to create a flexible, feature-rich, and modular digital asset management platform to meet asset management requirements of individuals, as well as major enterprises. 

EMAM can offer basic hardware specs for the different packages and platforms, but it is ultimately up to the Reseller/ SI or cloud vendor to finetune the hardware specs with their offerings and the customer’s requirements. This document is meant as a starting point guide. 

Here’s a comparison chart of different eMAM products:

FIGURE 1- EMAM PRODUCTS COMPARISON CHART

2.1 eMAM Database/Web/Application Node

In eMAM Publish system configuration, eMAM database, web and application nodes are installed in one server. We recommend keeping the database and log files in a RAID10 array with daily backup configuration. For the high transcoding requirements, we recommend running the server based transcoding engine and eMAM application server components from a separate server. 

• The eMAM Web Node consists of software components; eMAM Gateway and eMAM Director and are pointed to the eMAM Database running in the same server. eMAM Director application will be deployed in the same server and these components will be pointed to eMAM Gateways running in the same server. 

• The eMAM Application Node consists of software components; eMAM Delivery Service, eMAM Cloud Connector, eMAM Ingest Service and eMAM Archive Service and are deployed in the same server or a separate server depends on the ingest, archive and delivery volume. All these application components are deployed as backed windows services and these components will be pointed to eMAM Gateways. 

• The eMAM Database Node consists of a set of Stored Procedures, Functions, Tables and other configurations. The eMAM Database Node can be hosted in Microsoft SQL Server. eMAM uses less expensive NAS storage or LTO tape library as archive storage. Content can be kept in both online disk storage and archive storage. Disk retention rules settings are available in eMAM to automatically move the content from disk storage to archive. Content from the archive can be restored to online disk storage or it can be delivered outside eMAM in any desired file format. eMAM supports partial restore for supported broadcast file formats. EMAM recommends LTO library to preserve and protect the content in archive for long term. eMAM requires third party software to manage Robotic LTO libraries. 

In case of any server failure, we can manually bring up these services from another server. eMAM database can be restored from the backup or from the RAID array. Failed jobs can be easily resubmitted from the eMAM Director Dashboard.

Click here to know more about eMAM Publish.

The eMAM Publish software package consists of one eMAM App Node, one eMAM Web Node and one eMAM Database Node. In eMAM Publish configuration, eMAM software components can be deployed in one or two servers.

Basic Server hardware requirements for eMAM Publish are as follows:

eMAM allows users to login to the application using any standard web browser. eMAM supports three types of logins: using normal login, Active Directory login and SSO login.

4. Network Diagram

4.1 On Premise Network Diagram

FIGURE 2- ON PREMISE NETWORK DIAGRAM

4.2 Cloud Network Diagram

FIGURE 3- CLOUD NETWORK DIAGRAM

5. Firewall Ports 

Listener ports: 443, 8443 

Target groups ports: 80, 8080 

FIGURE 4- FIREWALL PORTS

6. Need Help 

Please contact your Sales Representative for details. sales@emamsolutions.com , +1.888.808.3856

7. Appendices

7.1 Archive Appliance / Archive Server

This server is required to manage a robotic LTO library. eMAM Archive module will interface with the archive server/appliance to perform archive, restore and partial restore functions from LTO tapes. 

https://www.emamsolutions.com/tech-partners/

7.2 Transcode Appliance / Transcode Server

eMAM requires a transcoder to create .h264 MP4 proxy files for eMAM. eMAM Ingest and delivery modules will interface with the transcode server/appliance to perform transcodes. Transcoding is done by a 3rd party partner. In eMAM Vault, in most cases you may use the same server that is running eMAM.

https://www.emamsolutions.com/tech-partners/

7.3 Online disk storage

eMAM stores the original and proxy files in online disk storage for immediate access. Storage size is determined based on the daily ingest volume and the amount of content that needs to be kept in the online disk storage. eMAM has built in options to move the content from online storage to archive storage based on storage threshold, archive threshold (days) and other archive rules. eMAM uses NAS, DAS or SAN storage as online disk storage depends on the customer requirements. Additional third-party software may require connecting to the multi-write SAN volumes. ** Please note – eMAM uses windows service users that must have read/write/delete access to the Storage. This in most cases requires the same user is also a valid user on the storage.

7.4 Cloud Storage (Optional)

eMAM can store the content in Object Storage buckets. The eMAM Cloud connector can upload the original content and proxy files into separate cloud storage buckets. Content that exists in AWS S3 buckets can be presented through Amazon CloudFront (CDN) URL within eMAM. For example, if somebody tries to preview a video from Los Angeles, the video will be loaded from a datacenter in Los Angeles. If somebody tries to preview the same video from London, the video will be loaded from a datacenter near to London. Cloud storage can be considered as archive storage too.

Purchase the cloud services from a cloud vendor and provide the account configuration details to eMAM implementation team. (Sample cloud vendors below)

1. https://aws.amazon.com/s3/   
2. https://aws.amazon.com/cloudfront/
3. https://cloud.google.com/storage/ 
4. https://wasabi.com