Working of eMAM Uploader and Feeder in MAC and window

Working of eMAM Uploader and Feeder in MAC and window

eMAM Uploader

Users can upload files via drag and drop or by scanning folders. Once the file is added to the upload queue, uploader will check whether port 8080 is open or not. To avoid conflicts we have to make sure that 8080 port is configured. Port will listen the requests and sent back the request to Apache server. eMAM will check whether the uploader URL is up and running or not. See the below URL and screen shot for example.
eMAM Feeder in Mac

Install and configure the Feeder from the eMAM Director interface.
Users can drag and drop or scan folders.
Ensure that the logged in user is associated with the preferred ingest profile.
·This can be managed under "User Management" section of Admin Tools page. 

  • In MAC system, we have to mount the UNC path with the configured credentials(feeder usually mount the folders automatically).
  • Feeder will check the path is mounted if not it will try to mount ingest path configured using the ingest credentials from the settings. 
  • We have different order of connection type. we can get this option from Super Admin->Ingest profile->Advanced settings->Folder config.The order of connection type which we can be configured in the ingest profile are as follows,
a) Local path
b) Filecatalyst
c) FTP
d) UNC(Universal Naming conversion, A standard for identifying servers, printers and other resources in a network, which originated in the Unix community. A UNC path uses double slashes or backslashes to precede the name of the computer. )

Feeder in Windows

  • Install and configure feeder after downloading from th eMAM Director interface.
  • Users can drag and drop or scan folders, ensure that the logged in user is associated with the right ingest profile.
  • This can be managed under "User Management" section of Admin Tools page.
  • Feeder uses FTP (if it is configured for the ingest profile) or http/https to connect to the eMAM Gateway and transfer files.
  • Feeder will check whether the UNC path is accessible or not, If not, we have to access the UNC path with any of the admin credentials.(no need of mentioning).

    • Related Articles

    • Bug Fixes eMAM 5.4

      Bug Fixes in eMAM 5.4 BUG ID DESCRIPTION 5.3.1_18NOV2021 11889 Storage DNA API change to handle "404 not found" in the response. 11899 Schedule metadata is not getting updated for PATCH api/v1/assets/{AssetId}/AssetMetadata 11708 PFR is not working ...

    • Working of Feeder in MAC and Windows and Uploader

      Working of Feeder in MAC Step 1: Install and configure the eMAM feeder by using the JNLP file. Step 2: Users can drag and drop or scan folders Step 3: ensure that the logged in user is associated with the right ingest profile. Step 4: This can be ...

    • eMAM version 5.1 Bug Fixes

      eMAM version 5.1 Bug Fixes The following table lists the significant bugs that were fixed in the eMAM 5.1 version with Bug ID and description of the problem. BUG ID DESCRIPTION 5.0.3_patch_20NOV2018 8705 AI process is not working in eMAM 5.1 set up ...

    • eMAM Version 5.2 Bug Fixes

      eMAM Version 5.2 Bug Fixes The following table lists the significant bugs that were fixed in the eMAM 5.2 version with Bug ID and the description of the problem BUG ID DESCRIPTION 5.1.0.1_17APR2019 9770 mediainfo.dll missing in eMAM Client ...

    • eMAM Super Admin Console 5.1

      Please find the attachment.