Axinom Encoding sends events to the message publisher which you supply with the job. The article describes the support types for the publishers and how to configure them.

Message Publishers

Axinom Encoding progress tracking is built on the "push" model. This means that Encoding sends events to defined endpoints when a job’s state changes. Each such event contains useful information. It is up to your application to listen for these events and to define the handling behavior.

To start receiving events during job processing, you should specify target endpoints in the API request’s MessagePublishers section. Encoding broadcasts the same event message to all defined endpoints. Here is a quick example:

    "MessagePublishers": [
            "Type" : "rabbitmq",
            "Host" : "localhost",
            "VirtualHost" : "your-rabbitmq-vhost",
            "Queue": "messages",
            "CredentialsName" : "guest",
            "CredentialsSecret" : "guest",
            "CredentialsProtection": "Unencrypted"
            "Type": "AzureServiceBusQueue",
            "Connection": "Endpoint=sb://;SharedAccessKey=secret"

In this case, a RabbitMQ message publisher is used. Axinom Encoding supports a variety of message publishers, each has its own properties. Also, all message publishers support credentials protection via the CredentialsProtection property.

You can have a maximum of 5 message publishers.


This publisher pushes messages to a single target queue. The actual JSON serialized message body is placed in the payload, while its type name is placed in the AMQP message properties, under the type field.

Target queue should be manually created before using. This client uses default exchange and queue name as the routing key.
    "Type" : "rabbitmq",
    "Host" : "localhost",
    "VirtualHost" : "your-rabbitmq-vhost",
    "Queue": "messages",
    "CredentialsName" : "guest",
    "CredentialsSecret" : "guest"

Note that the "VirtualHost" property is optional. If it is omitted, the default value is used. However, if it has already been set in the Job Request, the value cannot be empty. If it is set and empty, the Job Request is not accepted and the following error is displayed: "VirtualHost value for RabbitMQ message publisher is not valid - is empty".

Azure Service Bus

Messages are published to Azure Service Bus Queues. You need to create a Azure Service Bus with a preferred name.

Azure supports two kind of queues: Service Bus Queues and Storage Queues (part of a Storage Account). Only the former are supported by Axinom Encoding as a Message Publisher.

Use the key and endpoint to fill in the MessagePublishers section of the encoding job. The snippet below is an example. Replace the service bus name and secret key with actual values.

    "Type": "AzureServiceBusQueue",
    "Connection": "Endpoint=sb://<azure_service_bus_name>;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=<your_secret_key>"

You can find the connection string of the Service Bus Queue from the Azure Service Bus page. In the left-hand menu, under Settings, click Shared access policies. If you are using RootManageSharedAccessKey policy, then you can select the connection string for that policy. If you wish to use another policy, you need to change the SharedAccessKeyName also according to the policy you select.

azure shared access policies
Figure 1. Find the policy from the list

Then you can get the connection string of the policy. The keys and connection strings are displayed on the right. Copy the value by clicking the relevant icon on the row.

azure connection string
Figure 2. The primary and secondary key have been excluded from this example but you should see your values
We recommend you to use credentials protection via the CredentialsProtection property. For instance, in the connection string above, you need to use credentials protection for the Shared Access key.

For each message type, you need to create a new queue with the "queue" postfix in its name. For instance, for the message of the type "jobcreated", there will be a queue called the "jobcreatedqueue". In addition, a message has a custom property "OriginalMessageType", which reflects the message type, for example, "JobCreated".

You can see the details of the message queue if you click the queue, then click Service Bus Explorer (preview), click Peek at the top (next to Send and Receive) and then click Peek again at the bottom.

message details azure
Figure 3. This is how you see the message details

Further, you can copy the message and check message body using a Json formatter (e.g.

Amazon SQS Queue

Messages are published to the Amazon SQS target queue. You need to create an Amazon SQS Queue with a preferred name. You have to replace uri Path, credentials Name and credentials Secret with actual values.

    "Type": "AmazonSqs",
    "UriPath": "<your_account-id>/<your_Queue-path>",
    "CredentialsName": "<YOUR_AWS_ACCESS_KEY_ID>",
    "CredentialsSecret": "<YOUR_AWS_SECRET_ACCESS_KEY>"

From the queue details section, you can find the URL of the queue you just created.

amazon sqs details
Figure 4. Queue details
We recommend you to use credentials protection with the CredentialsProtection property. For instance, in the connection string you are using for Amazon SQS, you need to use credentials protection for CredentialsSecret.

To see the incoming messages,go to "Send and receive messages" panel. Under the Receive messages section, click Poll for messages to see the messages. You may have to poll time to time to receive the list of messages when there are a lot of messages. You can click a message and see the details of each message.

Message list aws sqs
Figure 5. Message list


Unlike the previously mentioned publishers, the FTPS message publisher creates log files to a specified log folder. For example, the log files could be created to the source video location, based on the incoming message types. Each message type can be mapped to a certain type of a log file, the exact title of which is configurable in the message publisher configuration.

Every message other than that of type success or error is appended to the end of the generic log file. Upon a successful or unsuccessful job completion, the publisher creates – or overwrites, if the file already exists – the respective log files and writes the message content to the file.

    "Type": "Ftps",
    "UriPath": "ftps://",
    "CredentialsName": "username",
    "CredentialsSecret": "password",
    "LogFileName": "all.txt",
    "SuccessFileName": "success.txt",
    "ErrorFileName": "errors.txt"

Revision History

The table below lists the document versions and any changes to them.

Version Date Description


October 20, 2020

  • Initial version.


March 1, 2021

  • Optional property "VirtualHost" added for RabbitMQ.


May 4, 2021

  • Azure Service Bus queues need to be created manually.


June 10, 2021

  • Detailed instructions about creating Azure Service Bus queues.


June 22, 2021

  • Azure Service Bus queue details moved into a separate article.