eMAM 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. 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:
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.
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
The file needs to contain the following items
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.