Introduction
VIDIZMO is an Event-Driven system that utilizes RabbitMQ as the broker service for inter-communication between component services. Data is transferred between different applications and services using messages.
A message is a container decorated with metadata and contains data. The data can be any kind of information, including structured data encoded with the common formats such as JSON (JavaScript Object Notation), XML, Apache Avro, Plain Text, etc.
Configure RabbitMQ as Broker in VIDIZMO
A broker service is needed to exchange data and messages between different VIDIZMO services for the application to function. To configure broker service in the VIDIZMO application, please follow the instructions given below:
Step-1. Login VIDIZMO application with Administrator user.
Step-2. Go to Navigation Menu > Control Panel > Application Configuration > VIDIZMO Runtime Configuration and click ‘Edit’ to change/update existing config.
Step-3. Select your Event System as RabbitMQ and enter the connection information as needed i.e., IPv4 address of your RabbitMQ server, username and password of your RabbitMQ administrator account and AMQP port configured in your RabbitMQ server. See below screenshot:
Step-4. Click ‘Update’ to update the latest changes in the system.
Application Configuration and Component Services
This section provides information about VIDIZMO related configurations that you may need to investigate in case of issues.
Distributed Run-Time Config
The ‘Application Configuration’ portion in your VIDIZMO app includes the ‘Distributed Run Time Config’ section where you would configure Endpoints needed to establish a connection with the broker service. The application may run into unexpected issues if the Endpoints are not specified correctly. Make sure the correct Connection String is added with all VIDIZMO services in the ‘Distributed Run Time Config’ section. The example is shown below:
VIDIZMO Component Services
VIDIZMO uses different component services that run in the background to allow the application to function. The VIDIZMO application may run into issues when one or more services are in a stopped state.
When one or more VIDIZMO services are in a stopped state, it can cause the broker service to stop relaying messages between component services. At this point, you will see the RabbitMQ message queue being piled up (see the count).
Please make sure VIDIZMO services are in running state on application and encoder servers. See the below example:
