Media Management provides a content services node infrastructure to process your transformations. You can create content services nodes remotely to offload low level transformations.
You can have multiple content services nodes running on the same server, ideally separate from your Alfresco server, however configuring a single content services node on a single server (with servers scaled as required) provides the optimum framework for multiple parallel transformations.
- Client Application (Alfresco repository): Task messages are generated and sent from the Alfresco repository, containing a reference to the source content (Source ContentReference) and other options. The options specified depend on the task; for example, a target reference or media type. The content reference needs to be in a format that the task nodes can handle; for example, a file on a shared disk, an S3 path, or a CMIS document ID. The source and target content is stored in a content workspace. Supported formats are shared file or Amazon S3 storage.
- Message Routing (ActiveMQ): A message routing system, for example; ActiveMQ, then directs the request to the appropriate queue for consumption by processing nodes. When you view the ActiveMQ queues in the web console (http://localhost:8161/admin), there are separate queues for image transform requests, image transform responses, video transform requests and video transform responses.
- Transform Component: A component listens for messages on a queue and calls on ImageMagick or FFmpeg workers to perform the task specified by the source content reference. The component can optionally send a reply that is consumed by the original requestor or another party.
- Task Node: Task nodes bootstrap one or more components.
For more information on launching a content services node, see Starting Media Management.
For more information on advanced ActiveMQ settings, see Configuring advanced settings in ActiveMQ.