eMAM post-implementation configurations

eMAM post-implementation configurations

1. Adding MIME type for epr, dmg, etc

Go to IIS >
 
#1. Click on Default Gateway (This way virtual directory that comes under it will inherit MIME types added to it).
#2. Click on MIME types
 
      
#3. Click on Add.
      
 
#4. Enter File name extension (.epr, .dmg, prproj, etc.) and MIME type accordingly.
      

And click OK. 

Add the following mime type under the Default website

1. Filename Extension as .
    Mime type : text/html

2. Filename extension : .dmg
    Mime type        :  application/octet-stream

3. Filename extension : .rtin
    Mime type        :  application/x-mpegURL 

4. Filename extension : .epr
    Mime type        :  application/octet-stream


2. If the registry entries are configured with HTTPS Configure URL rewrite in the web nodes

To make HTTPS configuration in the Empress Media folder in the registry follow this link


3. Clean up old Java versions and Install the latest

This article explains explains the process to find the older version of Java, uninstalling it, and updating it to the latest one.


4. Configure URL rewrite in the web nodes

 To solve the eMAM panel and eFeeder loading problem after Microsoft security patches follow this  link


5. Check the download path in the director and make sure it’s accessible

Go to file path “C:\Program Files\Empress Media\eMAM Director”  in Web server and open web.config

     

Inside <appsettings> you can find the key for “DownloadPath” where we have to give the value(URL) for the download path. This can be either IP or Domain name in HTTPS or HTTP

  

Saving the configuration.

 To make sure it’s accessible

 Go to the eMAM director and try to download an asset. We will be prompted with a new tab just like below with the same URL we configured on the web.config in Director.

     

6. Put SSO logout URL in the Gateway config for the WSFED

 

 Go to file path “C:\Program Files\Empress Media\eMAM Gateway” in Web server and open web.config


  

Inside <appsettings> you can find the key for “WsFedSignOutURL” where we have to give the value(URL) for the SSO sign-out URL. 

 



Save the configurations



7. Add HTTP response header in the virtual directory


In order to set IIS for HTML plackback to work with both IP addresses and different domain names. Please use this link



8. Machine key configuration for the REST API


In the case where the bearer token for RESTAPI created from the first web server won’t work when it is pointed to the second server by the load balancer. We have to make sure both servers have the same machine key for follow this steps

 


  1. Correct the connection string details in the Rest API config,
  </appSettings>
  <connectionStrings>
    <add name="EMAMConnectionString" connectionString="Data Source=SQL server hostname or IP;Initial Catalog=emamdb;Persist Security Info=True;User ID=emam;Password=*******;connection timeout=180;" providerName="System.Data.SqlClient" />
  </connectionStrings>
 
  2. Add the upload manager URL in the REST API config under <appSettings>
 
<add key="UploadManagerURL" value="http://domainOrIP:8080/eMAMUploadManager/EMAMUploader" />