fbpx

eMAM Integration

eMam logoeMAM provides a number of integrations with Drastic products including Net-X-Code, Net-X-Convert, and Net-X-Proxy.  For most cases, the main configuration is done within eMAM itself. In the case of live capture, configuring the Drastic server to send messages to eMAM allows eMAM to detect new records and allow the user to start using them while they are still recording. This article has the details for that setup.

 

eMAM Notification Configuration

Net-X-Code uses eMAM's REST API to notify eMAM of new records. To use that API, the localtion of the eMAM server on the network must be specififed and the authentication for the server must be set up on the Net-X-Code server.  The eMAM server must have an IPv4 address (like '192.168.1.200') and it must have a name that can be resolved to that address (like 'mam').  This can be setup on your DNS server, or just in the host file of the Net-X-Code server.  So long as you can ping 'mam' on the drastic server and get back the IP address, you are ready to configure.

OAuth2 - secure authorization setup

To specify the eMAM location, run DDRConfig, select the Advanced tab and go to /VVW/Config. Add a new string called 'eMAMServer' (without the quotes) and specify the server name or address:

eMAM DDRConfig

You will also need to set up the OAuth2/Token server address at /MediaReactor/OAuth2/<eMAMServer>, or in this case the key would be /MediaReactor/OAuth2/mam/.  Under that key, you will need a new string call oauth2server.  That should be set to the token server address on the eMAM server.

eMAM DDRConfigOAuth2

To set up the authentication, you will need to create a JSON file in a text editor that will be used when connecting to the eMAM server. This file must have the same name as the server (in this case mam.json) and must be placed in the following location

Windows:

C:\ProgramData\Drastic\

Linux

~/Drastic/

OS-X

/Library/Application Support/Drastic/

The file needs to contain the following items

{
  "grant_type": "password",
  "client_id": "0",
  "client_secret": "thesecretprovidedbytheemamserver",
  "username": "yourusername",
  "password": "yourpassword"
}

Server API Location

This setting lets the server know where to send the API commands.  This is in the eMAMServer element under \VVW\Config\.  It should be the base address of the HTTP server (e.g. http://emamdrastic or http://192.168.0.100 if using the IP address)

DDRConfig eMAMServer

Record/Proxy Drives and HTTP Location

The record drive and location can be set on a per channel basis in /VVW/Internal0 (where 0 is between 0 and the number of channels you have).  To allow eMAM to locate these file, the relationship between the base record drive and the http sharing of that location needs to be know.  For example, if the record path is

\\emamdrastic\emamfolders\capture\today\new.mxf

and from the HTTP servers point of view the file exists at

http://emamdrastic/capture/today/new.mxf

then the server needs to know what the common base for both would be.  In this case it would be

\\emamdrastic\emamfolders\  ==  http://emamdrastic/

as the rest of the path is the same in both cases.  There are two sets of settings for this:  eMAMFileBaseDrive/eMAMFileBaseHTTP and eMAMProxyBaseDrive/eMAMProxyBaseHTTP.  They are found under Advanced VVW/Config/

DDRConfig eMAMPaths

Conclusion

With this setup, whenever a new high res and proxy file pair starts recording, a message will be sent to the eMAM server letting it know that the new record has started and where it is.  This will allow eMAM to add the recording to its database, and allow the user to open the proxy recording while it is still ingesting, and begin workng with the media.