Edge Application - Storm Streaming Server

Applications are separate group of streams with specific set of parameters and settings. An application defines how streams can be published and viewed.

Sample configuration

An edge application is the basis for creating a video streaming cluster. It is very similar to a live application. A single edge application will connect to an origin application (or multiple ones) and copy its streams when requested. You cannot push streams into an edge-type application.

The basic edge-type application configuration stored in config/preferences.xml looks as follow:

<Application name="edge" type="edge">

            <ClusterManager host="mydomain.com" port="443" isSSL="true">

	<SecureStream enabled="false">


	<DVRSettings enabled="false">


Main parameters explanation

Application:nameName of this application. If there are more applications within your preferences .xml they all must have unique names.
Application:typeThis value must be set to “edge” for this type of Application.
Table 1. Main parameters table

Streaming Cluster Settings

This block defines a list of ReverendMothers to which information about streams and their status within the cluster is sent. Later, Edge-type applications connected to these same ReverendMothers will be able to locate the stream on the appropriate server with an Origin-type application.

It is possible to define more than one ReverendMother in the list for the purpose of redundancy.

ClusterManager:hostURL or IP to a server hosting ReverendMother instance.
ClusterManager:portPort for ReverendMother connection.
ClusterManager:isSSLTrue/false depending on whenever SSL layer is required.
SecretA secret for connection authorization
PriorityPriority for ReverendMother (if more available). Higher the number, higher the priority
CopyOnPublishWhenever stream from an Origin application should be immediately copied to this Edge application, otherwise it'll wait for a first request from a viewer.
Table 2. Streaming cluster settings table

SecureStream Settings

SecureStream allows to protect stream playback using a special token. Can will change depending on viewer’s IP (optionally) or time. If you wish to learn more about this function, check our guide for SecureStream.

SecureStream:enableDefines whenever SecureStream is enabled for this application or not.
PasswordUnique password that will be used for creating a token.
CheckViewerIPDefines whenever viewer’s IP should be used to create a token.
TokenLifespanDefines token’s lifespan (in minutes).
Table 3. SecureStream settings table

MP4 Muxer Settings

MP4MuxerSettings block defines basic options for MP4 packager that is used for MSE/HLS connections

VariableFPSIf the source stream has no const frame rate (e.g. WebRTC-based source) muxer will try to fix the stream by adjusting composition times for selected frames.
KeyFrameCompensationEnables mechanism where “empty” frames are inserted into a stream if Audio/Video desynchronization is detected.
Table 4. MP4 muxer settings table

DVR Settings

DVR function allows for short live-stream rewind mechanism based on cached stream.

DVRSettings:enabledDefines whenever DVR is enabled.
CacheSizeNumber of MB within memory for storing video stream. Length of stored video material will depend on resolution and bitrate.
Table 5. DVR settings table