1. Introduction

eMAM Enterprise is a powerful scaled system to create, manage, and share media storage, in any number of cloud or local/on-premise environments, to meet the needs of the largest organizations. It is a set of configurations to achieve load balancing, high availability or disaster recovery. eMAM Enterprise system software package includes two sets of Web Node and App Node component licenses in 4 servers and additional servers for eMAM Database Node.

Here’s a comparison chart of different eMAM products:

For more details on eMAM Enterprise, click here.

2.1 eMAM Web Node

The eMAM Web Node consists of software components; eMAM Gateway and eMAM Director. Multiple eMAM Web Nodes can be placed behind a load balancer to perform automatic failover and network load balancing. The load balancer configuration is separate from eMAM Web Node configuration, and it must be done by the customer or the Systems Integrator. 

eMAM Enterprise system includes two licenses for the eMAM Web Node software bundle. 

2.2 eMAM Application Node

The eMAM Application Node consists of software components; eMAM Delivery Service, eMAM Cloud Connector, eMAM Ingest Service and eMAM Archive Service. The eMAM Application Node is responsible for making low resolution proxy copy of the source media for web-based preview. eMAM Application Node can manage a server-based transcoder like Drastic Net-X-Code, Telestream Vantage or ATEME Titan installed in another server. eMAM App Node can also manage a Command line transcoder like FFMPEG installed on the same server. While multiple eMAM Application Nodes can interact with the eMAM Web Node, failover between Application Nodes must be performed manually through the eMAM Super Administrator interface.

eMAM Enterprise system includes two licenses for the eMAM App Node software bundle.

2.3 eMAM Database Node 

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. Clustering and Automatic failover configuration is possible at the SQL Server and the OS level. eMAM Database Node can be hosted in a traditional SQL Cluster or in the High Availability Group configurations. here are no additional licensing requirements for eMAM Database Node.

3. Server Specifications

The eMAM Enterprise software package consists of 2 licenses for eMAM App Nodes and eMAM Web Nodes which require 4 servers. Additional servers are required for SQL Servers cluster to eMAM Database Node, Transcoding and Archive systems.

Basic server specifications or requirements to install eMAM DB Nodes, eMAM Web Nodes & eMAM App Nodes for eMAM Enterprise system are as follows:

4. Network Diagrams

Below are the high-level network diagrams for eMAM Enterprise system installed on-prem or on cloud or in a hybrid environment.

4.1 On-prem Network Diagram

4.2 Cloud Network Diagram

5. Firewall Ports

Listener ports: 443, 8443

Target groups ports: 80, 8080

6. Need Help

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

7. Appendices

Appendix 1: Online Storage

eMAM stores the original and proxy files in online storage for immediate access. Storage size can be determined based on the daily ingest volume and the amount of content that needs to be kept in the online 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. This can be a NAS, DAS or SAN storage depends on the architecture.  In the configuration illustrated the online storage will be used for distribution media only not for the graphics archive.

** 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. 

eMAM can also store the contents in Object or Block Storage buckets such as EBS, FSx etc. 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 an 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. http://aws.amazon.com/s3/
2. http://aws.amazon.com/cloudfront/ 
3. https://azure.microsoft.com/en-us/services/storage/ 
4. https://cloud.google.com/storage/ 
5. https://wasabi.com 

Appendix 2: Hardware 

• NAS/SAN storage that can support CIFS/SMB (Provided by Customer)
• For best performance on streaming, you may want to go with an Object Storage for proxies.

** 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.

Appendix 3: Archive Appliance / Archive Server (only based on customer requirement)

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. 

http://emamsolutions.com/partners.aspx

Appendix 4: Transcode Appliance / Transcode Server

This server is required 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. 

http://emamsolutions.com/partners.aspx

Appendix 5: Prerequisites (Server Instance)

• The host computer must be a WSFC node. The instances of SQL Server that host availability replicas for a given availability group reside on separate nodes of the cluster. 
• If you plan to use a SQL Server failover cluster instance (FCI) to host an availability replica, ensure that you understand the FCI restrictions and that the FCI requirements are met.
• Each server instance must be running the same version of SQL Server to participate in an Always On Availability Group.
• All the server instances that host availability replicas for an availability group must use the same SQL Server collation.
• Enable the Always On availability groups feature on each server instance that will host an availability replica for any availability group. 
• Each server instance requires a database mirroring endpoint.

For more info, please refer this page – 

https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability?view=sql-server-ver15#PrerequisitesSI

** 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.