EMAM Install Guide 5.3
EMAM Install Guide 5.3
Version 5.3
Oct 2021
Notice
The content in this document represents the current view of EMAM, Inc. as of the date of publication. As EMAM responds continually
to the changing market conditions, this document should not be interpreted as a commitment on the part of EMAM. EMAM, Inc.
cannot guarantee the accuracy of any information presented after the date of publication.
EMAM is a US registered trademark of Empress Media Asset Management and is used by permission. eMAM logos are US registered
trademarks of EMAM Inc.
Revision History
5.1 April 2019 Scott Eik eMAM 5.1 Comprehensive Install Guide
– Reseller Manual
5.1.0.7 July 2019 Scott Eik Support for Windows 2019 / MSSQL 2019
Disclaimer –
Although EMAM uses Microsoft products such as the Windows Operating System, MSSQL, IIS, Windows Failover Cluster
Services, Active Directory as the base software for the functioning of the eMAM software, the responsibility for the
maintenance and troubleshooting of those products resides with Microsoft, the Reseller or the Customer.
Table of Contents
1 OPERATING SYSTEM CONFIGURATIONS – ALL SEVER INSTALLS ............................................................................................ 5
7 EMAM SOFTWARE........................................................................................................................................................... 23
17 SUPPORT ........................................................................................................................................................................ 73
7. The default selection is good for the eMAM install If using MSSQL Express Edition.
(SQL EXPRESS)
Do not select the following: PolyBase Query Service, Analysis Services, Distributed Replay
Controller or the Master Data Services.
16. For best database performance, Microsoft suggests placing the Database, TMP, LOG and
database backup files for the database into separate drives. Use the Data Directories tab
(#3) and TempDB tab (#4) to specify the locations.
18. Newer versions of MSSQL will display this Consent form. To continue, you must select Accept
and then Click Next >
19. The Newer MSSQL also requires you to Consent on installing Python. Click Accept and then
click Next >
21. When the install completes successfully, you will see the status as Succeeded for all
Features. Click Close
2. In the interface on the Left-hand side, Click the arrow ( > ) to reveal additional items.
3. Select the items one at a time. What you are looking for is if everything is marked as
Enabled. If it is marked as Disabled, you want to change it to Enabled.
4. Once all the settings have been changed and verified as Enabled, Click on SQL Server
Services in the Left panel (#1) and then click on SQL Server (MSSQLSERVER) in the Right
panel. (#2).
6. You may now exit the SQL Server Configuration Manager software.
2. Click Install.
6 eMAM License
Before you run the eMAM installer, you must get a temporary license. On the next page is a copy of
the license request form. Send the license request to [email protected]
The form must be filled out completely. All installs will be a temporary license until EMAM has
received full payment. The license consists of 3 parts. Only 1 will be of interest when you are
licensing the servers, that is the License Code. The other 2 are for locating the license in our license
server if the license needs to be extended or updated in some way.
1. Customer Code This will always begin with EMCU followed by some numbers.
(This is the Customer Number)
2. ID This is an individual server ID that is issued in the eMAM license gateway.
3. License Code This is the license string that will be entered by you in the eMAM license
application.
*Please note the eMAM license is Non-Transferable from one server to another.
**License requests are handled only M-F 9am-4pm EST
7 eMAM Software
eMAM software is available only for download to Authorized Resellers. For software FTP location,
please email [email protected] for links.
7.1 eMAM Software Install Prerequisites
1. Download the eMAMSetup_5.2_10SEPT2020.zip file,
2. Uncompress the .zip file
3. Decide, do you install the software with Hostname, IP or FQDN? Remember it is difficult to
change once you have installed eMAM.
4. Have your eMAM temporary license string ready to enter.
5. Will you require eMAM to send out emails? IF so, make sure you have the SMTP mail server
credentials ready during the install, as the installer will ask for that information.
7.2 eMAM Software Install
1. Run the eMAMSetup 5.3 installer as Administrator.
2. Click the I agree to the license terms and conditions – after reading them.
3. Click Next >
b. IF you are installing for eMAM on multiple systems (2 or more) such as eMAM
Workgroup, your eMAM Gateway/Database Server would be selected like this:
7. eMAM DB Mailer Profile Configuration This is used to send emails out from the eMAM
Database, for example as part of an eMAM workflow. IF this install is part of a POC and sending
emails from the system is not necessary then you can simply skip this step by clicking Next.
If you skip this step and later decide that you want to have the database send emails, then in
the scrips section of this manual is a script to alter to add this functionality
a. Account Name (#1): This is the name you will use in the eMAM workflows when it asks
for
“DB Mailing Profile Name “. It may be easier to use the one in the example.
eMAMDBMailerProfile
The install will make you at least enter an Account Name at a minimum.
b. Description (#2): This can be any description.
c. Email (#3): This is the “sender” email address used for the SMTP server.
d. SMTP Username (#4): This is the username to log into the SMTP server.
e. SMTP Password (#5): This is the password for the SMTP user. This is mandatory for the
system to send emails even if the SMTP server does not require this, eMAM does.
f. SMTP Server (#6): This is the SMTP server URL/IP address
a. Organization Name (#1): This is the Name of the Company the eMAM system is for. Do
not leave this blank, this is important so that if automated emails are sent to either the
eMAM support team or the Reseller support team they know which server is having
issues.
b. Gateway URL (#2): This is where you input the Hostname, IP or FQDN for the access of
the server. Example by default it will choose the Hostname. In the above example, the
host name is DEMO-LAB-EMAM If you choose to use an IP, make sure it’s a static IP and
replace the existing hostname with the IP address. If the choice is to use a FQDN then
replace the existing Hostname with the FQDN. Example: http://DEMO-LAB-
EMAM/emamgateway/emamservice.asmx becomes
http://scott.emamcloud.com/emamgateway/emamservice.asmx
c. Analytics Gateway URL (#3): This is where you input the Hostname, IP or FQDN for the
access of the server. Example by default it will choose the Hostname. In the above
example, the host name is DEMO-LAB-EMAM If you choose to use an IP, make sure it’s
a static IP and replace the existing hostname with the IP address. If the choice is to
use a FQDN then replace the existing Hostname with the FQDN. Example:
http://DEMO-LAB-EMAM/emamanalyticsgateway/emamanalyticsgateway.asmx
becomes
http://scott.emamcloud.com/emamanalyticsgateway/emamanalyticsgateway.asmx
a. UserName (#1): This is the eMAM Windows user that eMAM uses for licenses. This is
defaulted to a local Windows user that the eMAM Setup installer will create. By
default, this username is emam .
i. If you are using Active Directory and have the dedicated eMAM service user
credentials enter them in here now.
b. Password (#2): This is the eMAM Windows user’s password.
c. For support purposes it is requested that it is left to default unless using Active
Directory.
a. User Name (#1): This is the eMAM Service user that eMAM uses for starting / stopping
the eMAM Windows services. This is defaulted to a local Windows user that the eMAM
Setup installer will create. By default, this username is emam
i. If you are using Active Directory and have the dedicated eMAM service user
credentials enter them in here now.
b. Password (#2): This is the eMAM Windows user’s password.
c. For support purposes it is requested that it is left to default unless using Active
Directory.
d. Typically, this is the same user as the eMAM Windows user.
a. Much like you did in STEP 7, you will want to change the HostName in the URL to the
HostName, IP or FQDN depending on what the choice was earlier. IF there were 2 or
more servers, then you will want to make sure the HostName is changed to the eMAM
App Server information. Make sure to leave the rest of the URL as is. Example.
http://scott.emamcloud.com:8080/eMAMUploadManager/EMAMUploader
Setup includes
*****************************************
9.1.1 Folders
1. Create a top-level Folder “emamfolders” (C or D drive for the POC/DEMO environment is fine
depending on available test space)
2. Do not use spaces or illegal characters in the folder names as this will cause URL issues later.
(~ " # % & * : < > ? / \ { | }. )
3. Inside the “emamfolders” directory create the following folders
a. Original
b. Proxy
c. Ingest
d. Archive
e. Delivery
4. Inside the Original and the Proxy folders, place a .PNG, .JPG or a .GIF file, anything image file
type that a browser can display. You can do a quick google search and find a sample file for
the test that follows.
9.1.2 Windows Share
You will need to share the top-level folder, in this example “emamfolders”. Share this folder and
its contents with full Read/Write access to the emam user.
d. Right click on Default Web Site and select Add Virtual Directory
e. Add the Alias (#1), typically we use emamfolders (which was the top level shared
folder name.)
f. Add in the Physical Path (#2) This is the physical location of the top-level shared
folder.
i. UserName (#1) is the eMAM Windows user that has full Read/Write access to the
storage.
j. Password (#2 & #3) is the eMAM Windows user that has full Read/Write access to the
storage.
k. Click OK.
l. Click OK.
m. Click Test Settings
n. Test Connection
You should get Green connection status. If not, there are networking or permission
issues and IIS is not able to properly connect to the storage.
o. Click Close
p. Click OK
3. If you have not already, place a small .PNG, .JPEG, or .GIF file into the shared Original and
Proxy folders. This will be used to test the IIS/Browser connectivity. (You can download a
test file from a google search if you do not have one handy.)
4. Click on the Arrow next to the emamfolders virtual directory that you previously created. In
the Left Panel of IIS under Connections. To display the folders under it.
5. This will open a Browser window and if everything is set correctly with permissions you
should now see your image in the browser window. (Leave this window open – or copy the
URL into a notebook for use later in the set-up.)
a. Sample URL: http://localhost/emamfolders/Original/Image1.png
b. Change out the “localhost” with the Hostname, IP or FQDN you plan to use during the
eMAM software install to make sure it is valid.
e. Display of Proxy test image in Browser (Leave this window open – or copy the URL into
a notebook for use later in the set-up.)
1. Sample URL: http://localhost/emamfolders/Proxy/image2.jpg
2. Change out the “localhost” with the Hostname, IP or FQDN you plan to use
during the eMAM software install to make sure it is valid.
d. Click Add (#1) Under Actions in the Right Panel. (This brings up the Pop-up)
e. Name (#2) Enter in the following: Access-Control-Allow-Origin
f. Value (#3) Type in an Asterisk: *
g. Click OK
Note if you have multiple Virtual folders in IIS for eMAM you will need to do this for each
top-level virtual directory. In most cases you will only have 1 as in this example.
8. If you have not already done the Readme instructions as part of the eMAMSetup do it now
while you are in IIS.
a. Add Filename Extension as . as a MIME Type
b. Click on the Server Name (#1) Under Connections – Left Panel
c. Double click on MIME Types (#2) – Middle Panel
c. Click OK.
d. Save the license Key to your desktop, and email to
[email protected] and let us know what customer this is for. If there
are multiple eMAM servers a license key will need to be generated per eMAM server.
Rename the keys with the server name so we can keep them strait when issuing the
licenses for each server.
e. Once we receive and process the .key file(s) we will issue you a license.dat file for
each of the servers.
f. Try to not close the eMAM License Manager prior to importing the license.dat file.
g. Once you receive the license.dat file, Click on Browse (#1) locate the file.
h. Click on Update (#2)
If you do need Component URLs, this is a list of the URL addresses, all you need to do is change the
Server Name from LOCALHOST to the correct URL name. Again, this is only needed if the Component
is on a different server. If all components are on the same server, you may leave all blank except
the eMAM Transcode Manager.
4. Emails (#4) these can be set to a local admin user for the reseller or the customer if this is a
POC/Demo system. If this is a production, please refer to the eMAM SuperAdmin Manual for
more details of what to enter here.
Be sure to include all information including a SMTP password for a SMTP user otherwise the mails
will not go out. Even if the SMTP Mail server does not require a username or password eMAM does.
Click on SUBMIT when done.
Save AS creates a duplicate of the Unit you are editing. This makes it easy to create a new unit that
has similar attributes as the original. This does not carry over users, assets or workflows. This option
will only work if you have a multiple UNIT license.
If you are editing, make sure you select SUBMIT.
13.1.3 User Management Tab
The User Management Tab is to create Admin users for a specific UNIT.
If you have multiple units, this is the interface that you will use to add the user to the next unit. The
system will prompt you saying the user already exists, do you want to merge the 2 accounts. You will
need respond in the affirmative.
If you have set up Active Directory, then you do not need to do this step as eMAM will verify users
based on that.
eMAM’ s License is based on named users. Vault by default has 10 users, Publish and Workgroup have
25 users, Enterprise has 50 users. You can always purchase additional users. (With the exception of
the eMAM MINI which is restricted to 5 users.) Please keep in mind that the eMAM SuperAdmin user
is counted as one of the users.
Local Users:
1. Enter in the email address of the local user you would like to add. (#1)
2. Select the business Unit you wish the user to be added to. Note – This will be the unit you
created, and not the “EMAM” unit. (#2)
3. Click PROCEED (#3)
14. If you need to Edit a user account, click on the pencil icon. (#1)
1. Click the “+” (#1) to open/edit the Storage configuration for the UNIT.
1. Please do not use spaces in the paths as that will cause URL issues.
2. Folder Name (#1) This is usually “Original” in a POC/DEMO but can be named anything that
makes sense for the Original High-Resolution files to reside. If you believe the customer may
have multiple Original locations, it may be a good idea to start thinking about some sort of
naming convention to keep them strait.
3. Highres File folder (#2) – This may be a Drive Letter or a UNC path. It is best practice to
open the folder from the server (Windows File Explorer) and copy / paste the path here to
make sure there are no mistakes and you can successfully access the folder.
(Make sure the folder has read/write access for the eMAM windows user)
4. Highres Virtual Path (#3) This is the URL you tested earlier in IIS. You will change the
“localhost” to the URL of the system and drop the File name you tested earlier to only go to
the Original folder. (NO trailing slash in the URL)
5. Low Res. Folder Type (#4) This is a pull-down Menu. Local is meant for Drive letters,
Network is meant for a UNC path.
6. Low Res Folder (#5) This is the path to the Proxy location that was set-up earlier. Much like
the Original folder, use Windows File Explorer to navigate to the Proxy folder. Copy / paste
the path into this location. Make sure the eMAM windows user has full read/write access to
this location.
7. Low Res Virtual path (#6) This is the URL you tested earlier in IIS. You will change the
“localhost” to the URL of the system and drop the File name you tested earlier to only go to
the Proxy folder. (NO trailing slash in the URL)
8. Archive Threshold (#7) This is set to number of Days if you want the system to Auto Archive
files going to this Storage.
9. Archive Purge Threshold (#8) This is the number of days to keep the content in the Original
High-Resolution location online after Archiving before the system deletes the content from
the Original location. Then the content only resides in the Archive only.
10. Purge Threshold (#9) This is how many days to keep the RESTORED content from Archive
on the Original disk location before it auto deletes again. Keeping the only copy in the
Archive.
11. Volume Name (#10) If you plan on using Adobe Premiere and on a MAC operating system,
this is where you enter in the MAC mount point name.
12. Excluded Extension(s) For Archive Purge (#11) Key in all the file extensions (multiple values
separated by semicolon), which needs to be filtered out from the purge queue after archive
operations (when immediate archive with delete file flag is enabled or archive purge
threshold criteria is met).
13. Selected Servers (#12) This is a list of the eMAM servers this system is licensed to. Typically,
you select all the servers.
14. Select Task Manager Server (#13) You may have multiple Task Manager servers in a larger
system configuration. (Example multiple locations) Select the Task Manager server for this
specific location.
15. Select Upload URL (#14) for Ingesting content into eMAM, you may use the browser-based
upload tool. This is the URL to that server and the port that will be used.
16. Auto Create Sub Folders (#15) Windows allows up to 4,294,967,295 files in a folder. This
also slows down searches when there a lot of files in 1 folder. With this selection you can
choose to automatically create a new storage location once the existing one hits a pre-
determined number of files or a specific data size in TB.
1. Transcode Profile Name (#1) This is a general descriptive name for the transcoder.
2. Transcoder Server IP / Host Name (#2) This is the hostname or IP of the transcode server.
3. Transcode Server (#3) This is the eMAM server with the Transcode Manager service installed.
4. Transcoder Type (#4) This is a pulldown menu with the supported API level transcoders. Each
transcoder type will give you different options based on the transcoder you select.
5. We will focus on FFMPEG for this manual.
6. Video Settings (#5)
a. App Path: Path to FFMPEG.exe
i. C:\Program Files\EMAM Media\eMAM Ingest Manager\CLTranscoders\ffmpeg.exe
b. Parameters:
i. -i "eSourceFile" -y -s 1280x720 -b:v 1024k -vcodec libx264 -r eSourceFrameRate -movflags faststart -pix_fmt yuv420p
"eVideoProxy"
7. Audio Settings (#6)
a. App Path: Path to FFMPEG.exe
i. C:\Program Files\EMAM Media\eMAM Ingest Manager\CLTranscoders\ffmpeg.exe
b. Parameters:
i. -i "eSourceFile" -y -ab 128k "eAudioProxy"
8. Thumbnail Settings (#7)
a. App Path: Path to FFMPEG.exe
i. C:\Program Files\EMAM Media\eMAM Ingest Manager\CLTranscoders\ffmpeg.exe
b. Parameters:
i. -i "eSourceFile" -y -ss 00:00:08.000 -f image2 -vf scale=176:-1 -vframes 1 "eThumb"
9. Image Proxy Settings (#8) Set the Max Width and Max Height of the image proxy etc.
10. AV ingest threads (#9) This is the number of Audio/Video Threads the system can handle.
Based on the system this is normally between 1-4.
11. Otherfiles ingest threads (#10) This is other files such as documents. Normal is again 1-4.
2. Transcoders – This shows the transcoder options you have already set-up.
3. Users – This is one of many areas you may select users that have access to this ingest profile.
4. Extension – This is where you add an extension of the video, audio, document files you are
ingesting. This is also where you enter in a pattern or extension you wish the ingest to
exclude from ingesting. Many of the most common are added by default.
6. Click SAVE
This is where you would set-up a Delivery Profile what you would assign to individual users. Manage
Delivery Profiles is split into 2 Tabs.
1. Profile Name: (#1) This is the Name the end user will see for a delivery profile. Give it a
descriptive name.
2. eMAM Delivery Server: (#2) This is the eMAM Application server that has the Windows
delivery service on it.
3. Delivery Type: (#3) This is the type of delivery. In this sample we will not be using a
transcoder to transcode it, we will just deliver the Original file format as it was when
ingested. Check the eMAM Super Admin manual for additional options.
4. Include Asset: (#4) 99.9% of the time you will want to deliver the asset itself.
5. Include EDL: (#5) This delivers the EDL file to the delivery location.
6. Include eMAM Metadata XML: (#6) This option sends an XML of all the assets metadata both
custom and embedded metadata.
7. Include Sidecar File: (#8) This option allows you to have a custom XML side car with only
specific metadata supplied. This can be customized per another system’s expected XML.
8. Destination File Name: (#9) Choose a variable from the drop-down list and click on Insert
button to set it as the delivery destination file name.
9. Delivery Location Type: (#10) Choose the delivery location type.
10. Network UNC path: (#11) Using Windows File Explorer, copy / paste the path for the
Delivery folder.
5. Click SAVE
This is the Profile that a user would have access to when selecting assets for archive.
1. Profile Name (#1) This is what the end user will see if they have access to an archive
profile.
2. Archive Host Server (#2) This is the server name you created in the Manage Archive Host
Servers above.
3. Server (#3) This is a pulldown menu for the eMAM application server that has the eMAM
Archive Service installed on it.
4. Archive Folder (#4) Using Windows File Explorer, copy / paste the path for the Archive
folder.
5. Options:
a. Delete Files from Storage – Deletes files from the “Original” storage.
b. Delete Files from Source – Deletes files from the Indexed Storage.
c. Full Restore – Only relevant to Restores that the middleware supports partial file
restores.
d. Is Default – You must have at least 1 Archive profile set to Default for each UNIT.
6. Click SAVE
7. After adding or changing an archive profile you will need to restart the eMAM Archive
Manager windows service.
1. AI Profile Name (#1) Give a name to the profile that makes sense. Typically, the AI service
provider’s name.
2. AI Server (#2) This is the eMAM application server.
3. AI Type (#3) This is broken down to 2 AI Types.
a. Insight – Face and image recognition
b. Transcribe – Transcribes audio into text
c. Insight & Transcript – Combines both
4. Click SAVE
Note – After any changes in the Super Admin for Archive, Delivery, Ingest Profiles you will
need to restart the related windows eMAM service before those changes take effect.
Restarting an eMAM windows service does not adversely affect the existing queued files.
15 Firewall ports
Service Ports Notes
FTP Passive Ports 50000- Passive port range – TCP (eMAM eFeeder)
50009 (On the eMAM Application Server)
AME – Adobe Media Encoder 8008 TCP/UDP (eMAM AME panel communication)
(On the eMAM Application Server)
Only needed if eFeeder is integrated with **If you have FileCatalyst it typically installed on the eMAM
FileCatalyst Application server.
17 Support
eMAM provides level 2 support for the Resellers / SI. Resellers are expected to take 1st level support
call as the issues reported may be outside eMAM software support such as Hardware infrastructure,
3rd party software issue etc. The Reseller would be in a better position to determine if the issue is
an eMAM or 3rd party issue. EMAM is more than happy to work with a reseller/ SI to determine where
the root issue is located.
Please supply eMAM support with eMAM version information, steps on how to reproduce the issue,
any log files to help them determine the root cause of the issue. Be prepared to share a Teamviewer-
14 ID and password along with a user account information so they can physically see and try to
reproduce the issue.
Email support for fastest response.
17.1 EMAM Web Support
1. Ticketing System: http://support.empressmam.com/Main/
a. Register or log into your account to view your current ticket status.
2. Web Chat: http://support.empressmam.com/Main/
a. Top left corner of the web page.
3. Email: [email protected]
a. Based on your email address this will automatically create a support ticket in our
support ticketing system. Please always respond back to the same thread for the issue
and split all issues into their own ticket for easier tracking of issues.
17.2 EMAM Phone Support
1.888.808.3856
17.3 EMAM Customizations – Web and Application development
EMAM can be your partner in both eMAM and non-eMAM Web and Application development as
well. Contact your sales representative for more details.
http://emamsolutions.com/
[email protected]
1.855.855.6006