Passing configuration parameters into Red5 application

Often your Red5 project may need some external variable to be passed into Red5 application as a part of your configuration data, such that its not hard coded into the red5 application and you can change it as and when needed. For example : A database name, a configuration file path etc etc


Here we will demonstrate two ways to pass configuration data into Red5 application.


  1. Though red5-web.xml directly
  2. Through routed via red5.xml


Passing parameters through red5-web.xml

This is the first method used to pass configuration data into your red5 application. In this example we will pass variable into the main application class.


package org.red5.core;

import org.red5.server.Scope;
import org.red5.server.adapter.ApplicationAdapter;
import org.red5.server.api.IConnection;
import org.red5.server.api.IScope;
import org.red5.server.api.service.ServiceUtils;

public class Application extends ApplicationAdapter {

public String database = "mydb.sqlite";

/** {@inheritDoc} */
public boolean appStart(IScope scope) {
return true;

public boolean connect(IConnection conn, IScope scope, Object[] params) {
return true;

public void disconnect(IConnection conn, IScope scope) {
super.disconnect(conn, scope);

public void setDatabase(String dbname)
database = dbname;


Note the last function: setDatabase this is the public setter function which will set the value of the variable database. Now the second part of this process is sending value to this function from outside Red5. For that we will be usingt the Red5 bean configuration file – red5-web.xml

So now we will edit the red5-web.xml file at the application’s bean handler definition and add the the variable property to it.

<?xml version="1.0" encoding="UTF-8"?>
Defines a properties file for dereferencing variables
<bean id="placeholderConfig" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
    <property name="location" value="/WEB-INF/" />

Defines the web context
<bean id="web.context" class="org.red5.server.Context"
    autowire="byType" />

Defines the web scopes
<bean id="web.scope" class="org.red5.server.WebScope"
    <property name="server" ref="red5.server" />
    <property name="parent" ref="global.scope" />
    <property name="context" ref="web.context" />
    <property name="handler" ref="web.handler" />
    <property name="contextPath" value="${webapp.contextPath}" />
    <property name="virtualHosts" value="${webapp.virtualHosts}" />

Defines the web handler which acts as an applications endpoint
<bean id="web.handler" class="org.red5.core.Application" singleton="true">
    <property name="database" value="mydb.sqlite"/>


Note the application bean definition to see how the database property is passed into the application bean handler to the public setter function

<bean id="web.handler" class="org.red5.core.Application" singleton="true">
    <property name="database" value="mydb.sqlite"/>

At this stage it is important to note of the setter function is named:
public function setDatabase, like in the following format

setVariablename. The variable name is camel-cased along with the word”set”

Deploy applications to Red5 without restart

Although Red5 is well on its way to its  official 1.0 version (currently on 0.9.1), there are some things still not perfected for rigorous use. One of those crucial things is , installing/uninstalling applications without having to restart the entire server everytime.

The Hot-Deploy feature in Red5 lets you install RTMP applications to Red5 without having to disturb the running server. (more…)

Web Media Live Encoder – The Flex Based Online Broadcasting Application

Web Media Live Encoder is launching a new site pretty soon –, dedicated to Realtime products, based on RTMP and RTMFP Protocols. Our first major release is the Web Media Live Encoder. (more…)

last comments
Taro Yamada
Taro Yamada


Ready to use – Red5 streamer with stream security

As RTMP continues to grow, and Red5 triumphs as the only open source RTMP server alive, there are concerns to protect your application from misuse. The following red5 application implements stream security for both playback and publishing.

You can edit the files – allowedHTMLdomains.txt and allowedSWFdomains.txt and add the domain names that you want to be able to playback/publish using your application. Each domain name must be added in a  new line.

The application also lets you allow/disallow publishing entirely. To do so edit the file red5-web.xml and set enable publish as true/false according to your needs:

<bean class="" init-method="init" id="publishSecurity">
<property name="application" ref="web.handler" />
<property name="htmlDomains" value="/WEB-INF/allowedHTMLdomains.txt" />
<property name="swfDomains" value="/WEB-INF/allowedSWFdomains.txt" />
<property name="publishNames" value="/WEB-INF/allowedPublishNames.txt" />
<property name="enablePublish" value="true" />

You can also set stream publish security by defining specif stream names that are allowed for recording/broadcasting in the file allowedPublishNames.txt

Note : putting a * in any of the three security files will disable security for the particular context. Eg: Putting a * in allowedPublishNames.txt means that stream check is disabled.

This application is created for a quick and easy deployment, with guidance from



Customstreamer_domaincontrol_deployable_0.8 [rtmp application name: domaincontrol]

Or generate your own with Red5 – Online Application Generator