On the dashboard, click Download Agent and save the agent jar file to a folder on your machine.

Tips

When choosing the folder for saving the jar file, consider that this folder will be your <Agent Directory> below which the agent will be saving files by default when you start ingesting content.

It is strongly recommended not to save content in any system folders.

It is not recommended to run the agent from your Desktop.

Renaming the agent jar file is not recommended.

If you are planning to run multiple agents on the same machine, each agent jar file must be in its own folder.

Do one of the following to run the agent:

From your desktop environment, browse to the folder where you saved the agent jar file and double-click the file name. The Agent Registration page opens in your browser.

From a command prompt on Windows or with sudo on Mac or Linux:

Change to the directory where the agent jar file is located; for example, on Windows:
cd LOCATION_OF_AGENT

Run the following command:
java -jar agent.jar

The Register Agent page opens in your browser prompting you for an API key.

Tip

Alternatively, you can provide the API key as an argument from the command prompt:

java -jar agent.jar key:API_KEY

To register your agent with the configuration dashboard, enter your API key in the API Key box and click Register. If registration is successful, you will receive this message: "Success you've verified your API Key".

Tip

Check your browser's Address box to determine where the Agent Management page is located on your local machine. For example, if your agent registration address is localhost:8087/register, you can manage your agent from your local machine at localhost:8087/agent.

Text story formats. Text stories are available in the NITF or ANPA formats. The IPTC 7901 and hNews formats are no longer supported. Learn more about text formats >>

Media filters. Fewer video filters are now available for easier selection of video renditions. Newly added graphics renditions include JPEG, PNG and JPEG Matte full-resolution images. Freehand 8 and 9 graphics are no longer available. For audio, supported formats now include only MP3 and MPEG. Learn more about media renditions >>

Naming formats. Content file naming formats now include the two most popular options: <ItemID>-<Version>-<ContentID>.<ext> and <OriginalFileName>-<PartialContentID>.<ext>. When you import a WebFeeds configuration profile, options containing <OriginalFileName> are converted to <OriginalFileName>-<PartialContentID>.<ext>, and the other WebFeeds file naming options are converted to <ItemID>-<Version>-<ContentID>.<ext>. Learn more about Content Save options >>

Folder structure. WebFeeds options 'One folder per Entry' and 'One folder per entry and entitlement' are converted to the AP Media API option 'One folder per entitlement and one subfolder per version'. The other two folder structure options ('One folder per entitlement' and 'One folder for all content') are mapped to their direct counterparts. Learn more about folder structure >>

Duplicate settings. Options for filtering out duplicate content in the AP Media API have been simplified and are set to the default option of "Discard duplicates" when you import a WebFeeds profile. If you are interested in saving duplicates, make sure to change this setting in your AP Media API profile. Learn more about duplicate settings >>

Content post-processing. The option to specify a script for post-processing content is no longer available. If you are interested in tighter integration of your system with AP Media API, you can write your own custom program for processing a feed or searching and downloading content. To learn more, see AP Media API Developer documentation.