- Stop the Alfresco Content Services server.
Unzip the Alfresco Media Management package
into a new system directory; for example, opt/media-management:
You will see four folders:
- activemq: contains ActiveMQ software
- amps-repository: contains one AMP file to be applied to the Alfresco Content Services repository
- amps-share: contains one AMP file to be applied to Alfresco Share
- remote-node: contains content services node software and configuration file
Install the repository AMP file. Navigate to the amps-repository
directory and copy the following file to the Alfresco
Install the Share AMP
file. Navigate to the amps_share directory and copy the following
file to the Alfresco
- Delete the tomcat\webapps\alfresco and tomcat\webapps\share folders in the Alfresco installation directory.
Navigate to the bin directory and run the Module Management Tool
(MMT) file to install the repository AMP files:
For the Alfresco Content Services
java -jar alfresco-mmt.jar install ../amps/alfresco-mm-<version>.amp ../tomcat/webapps/alfresco.war
java -jar alfresco-mmt.jar install ..\amps\alfresco-mm-<version>.amp ..\tomcat\webapps\alfresco.warwhere alfresco-mm-<version>.amp is the specific AMP file that you downloaded.
For Alfresco Share:
java -jar alfresco-mmt.jar install ../amps_share/alfresco-mm-<version>.amp ../tomcat/webapps/share.war
java -jar alfresco-mmt.jar install ..\amps_share\alfresco-mm-<version>.amp ..\tomcat\webapps\share.warwhere alfresco-mm-<version>.amp is the specific AMP file that you downloaded.
Check the output to ensure that the AMP files have installed successfully.
- For the Alfresco Content Services repository:
- Take a copy of the most recent tomcat/webapps/alfresco.war<numbers>.bak file in case you need to uninstall Media Management.
Define properties relevant to Media Management in your
A sample alfresco-global.properties file is shipped in the root folder of the Media Management distribution zip, which defines custom properties. See Configuring Media Management for the full list.
If you have ActiveMQ on a separate server, configure the host and port number for
# Messaging broker, default is localhost messaging.broker.url=failover:(tcp://broker1:61616,tcp://broker2:61616)where broker is each ActiveMQ instance that you have configured.
You need to set this property only if your ActiveMQ instance is not on the same server as Alfresco.
Configure FFmpeg and ExifTool if they are not already available on the command line
# FFmpeg executable path, default is ffmpeg ffmpeg.exe= # ExifTool executable path, default is exiftool exiftool.exe=
If you want to preview raw images, set the following properties in the
Set the transformer.strict.mimetype.check property to true, and use the transformer.strict.mimetype.check.whitelist.mimetypes property to add the x-raw-adobe MIME type to an existing whitelist.
- If you are using shared content workspaces, remote transformations or publishing channels, configure these as specified in Configuring Media Management.
- If you have ActiveMQ on a separate server, configure the host and port number for ActiveMQ:
Update the remote-node/config.yml file that you extracted from the
Media Management installation
Specify the ActiveMQ host name and prefetch policy (to ensure that transformations can be processed in parallel):
messaging: broker: url: tcp://localhost:61616?jms.prefetchPolicy.queuePrefetch=1
The content services node uses ImageMagick and FFmpeg and requires that the executable directories are available on the system PATH variable or are specified using img.exe and ffmpeg.exe system properties.
For more information about the recommended architecture for Media Management, see Media Management architecture. For information about the content services framework, see Content services node architecture.
- Restart the server.
Launch Alfresco Share.
To check that the Media Management AMPs have installed correctly, add a video or image to Share, open the file and check that you can see that the media loading and a Renditions Panel is available.