• Quick Start Guide

    This tutorial will help you to get started using your Wowza Streaming Engine™ 4.0.3 software.

    Contents


    Introduction

    Installation and configuration
    Install Java
    Install Wowza Streaming Engine
    Starting (and stopping) the software
    Perform a quick streaming test

    Administration
    About Wowza Streaming Engine Manager
    Managing Sign-In credentials
    Creating applications
    Configuring properties
    Configuring modules
    Configuring server listeners
    Configuring streaming ports
    Adding new license keys
    Tuning for performance
    Logging
    Installing example applications
    Getting help

    Streaming concepts
    Streaming protocols
    Supported media file formats
    Content storage

    Introduction


    Wowza Streaming Engine (formerly known as Wowza Media Server®) is high-performance, extensible, and fully interactive media streaming software platform that provides live and on-demand streaming, chat, and remote recording capabilities to a wide variety of media player technologies. The Streaming Engine can deliver content to many popular media players such as Adobe Flash Player; Apple iPhone, iPad, and iPod touch and Apple QuickTime player; Microsoft Silverlight player; Android smartphones and tablets; and IPTV/OTT set-top boxes. Wowza Streaming Engine includes support for many streaming protocols including Adobe HTTP Dynamic Streaming (Adobe HDS), Apple HTTP Live Streaming (Apple HLS), Microsoft Smooth Streaming, MPEG-DASH streaming, MPEG-2 Transport Streams (MPEG-TS), Real Time Messaging Protocol (RTMP), Real Time Streaming Protocol (RTSP), and Real-time Transport Protocol (RTP). It's an alternative to the Adobe Media Server, Darwin Streaming Server, Microsoft IIS Media Services, and other media servers.

    Installation and configuration


    Installing Java

    Wowza Streaming Engine is a Java 6 (aka 1.6) and Java 7 (aka 1.7) application and requires the installation of a Java Runtime Environment (JRE) that supports deploying Java in server environments. The server JRE has everything you need to run the Streaming Engine software on your system.

    The following Java packages can be used with Wowza Streaming Engine:

    • Java Development Kit (JDK). The JDK includes a complete JRE and enables Java developers to develop and debug server-side applications.
    • Java Server JRE. The Server JRE is a complete JRE. Install this package if you want to run Java programs, but not develop them.
    • Java JRE. The JRE also is a complete JRE; however, the server environment that's required to run Wowza Streaming Engine is removed from 32-bit installations of the JRE, starting in JRE 7 Update 21 (JRE 7u21). To run Wowza Streaming Engine on 32-bit platforms with a more recent Java JRE, you must use the Java Server JRE or Java JDK.

    To get the best performance and to take advantage of transcoding functionality provided by Wowza Transcoder AddOn (which is only available for Windows or Linux when using a 64-bit operating system and 64-bit version of the Java VM), we recommend that you deploy Wowza Streaming Engine on a 64-bit operating system with the latest 64-bit Java package (JDK, Server JRE, or JRE). Java packages can be downloaded from the Java SE Downloads webpage.

    After your Java environment is installed and configured, you can validate that it's correct by opening a Command Prompt window (Windows) or terminal window (Mac OS X/Linux) and entering the command java –version. If correctly installed and configured, a version number that's equal to or greater than 1.6 is displayed.

    IMPORTANT

    Oracle has changed the default Java installation experience to benefit the average consumer. When you go to www.java.com and click the Free Java Download button, a JVM that matches your web browser architecture (which is typically 32-bit) is automatically provided for download. A 32-bit JVM has a "client" runtime, not the "server" runtime that Wowza server software requires for production use.

    Wowza recommends a 64-bit JVM (which contains the "server" runtime required by our server software) and 64-bit operating system for use in production environments. Some features, such as Wowza Transcoder, require a 64-bit platform. To get a 64-bit JVM for production use, go to http://www.java.com/en/download/manual.jsp to download and run a 64-bit installer.

    You can run Wowza server software on 32-bit operating systems, but we recommend that you do this only for evaluation purposes. A Wowza server may not run at peak efficiency when using the "client" runtime in a 32-bit JVM and some features, such as Wowza Transcoder AddOn, aren't supported on 32-bit platforms. After installing a 32-bit JVM, use one of the following methods to enable Wowza server to work with the "client" runtime:

    1. In a text editor, open [install-dir]/conf/Tune.xml and remove the following property from the file:
      Code:
      <VMOption>-server</VMOption>
    2. Save the file and restart the Wowza server if it was running.

    - OR -

    1. Create a server folder in your default Java installation bin folder ([java-install-dir]\bin). For example, if your default Java installation root ([java-install-dir]) is C:\Program Files\java\jre7, create the following folder:
      Code:
      C:\Program Files\java\jre7\bin\server
    2. Copy the contents from the [java-install-dir]\bin\client folder to the new [java-install-dir]\bin\server folder.

    3. Confirm that the JAVA_HOME environment variable value matches the Java installation root ([java-install-dir]). For example, C:\Program Files\java\jre7. If the variable value is incorrect, see After installing latest Java version, java command is still using old Java for more information about how to change it.

    Install Wowza Streaming Engine

    On the Windows and Mac OS X platforms, the Wowza Streaming Engine software is installed using an installer. On Linux/Unix-based platforms, the software is installed using a self-extracting binary installer. The installers are available for download from the Wowza Installers webpage.

    During the installation process, you'll be asked to enter a valid product license key. You'll also be asked to create a user name and password for an Administrator account. You'll use this account to sign-in to Wowza Streaming Engine Manager, a browser-based application that you can use to control the Streaming Engine software. The user name and password values are case-sensitive.

    Notes:
    • You must uninstall any previously installed Wowza server software before installing Wowza Streaming Engine 4.0.3. To preserve your previous Wowza server configuration, see the Wowza Streaming Engine Upgrade Guide.
    • During the installation process, you can select options to start Wowza Streaming Engine and the browser-based Streaming Engine Manager automatically after the installation is finished. These options configure the server and manager software to start automatically as system services. If you don't choose one or both of these options, you must start the server software and/or the manager manually. See Starting (and stopping) the software.

    Windows


    To install the Wowza Streaming Engine software on Windows operating systems, double-click the installer file and follow the instructions on the screen. To find the installer file, press WIN key + F and search for WowzaStreamingEngine-4.0.3.

    The default installation directory ([install-dir]) for the Streaming Engine software is:
    /Program Files (x86)/Wowza Media Systems/Wowza Streaming Engine 4.0.3

    Mac OS X


    To install the Wowza Streaming Engine software on Mac OS X, mount the disk image (open the WowzaStreamingEngine-4.0.3.dmg file), double-click the installer package (Wowza Streaming Engine 4.0.3.pkg) file, and then follow the instructions on the screen. Files will be installed to the following locations:
    /Applications/Wowza Streaming Engine 4.0.3
    - Readme file, startup/shutdown applications, and symlinks to server sample content, examples, documentation, and other items
    /Library/LaunchDaemons
    - background service scripts com.wowza.WowzaStreamingEngine.plist and com.wowza.WowzaStreamingEngineManager.plist
    /Library/WowzaStreamingEngine
    - symlink
    /Library/WowzaStreamingEngine-4.0.3
    - server application files and applications, bin, conf, content, examples, lib, and logs folders

    Linux


    Note: The Linux package manager will extract the Wowza Streaming Engine software files to the /usr/local/WowzaStreamingEngine-4.0.3 directory and the server will be installed as the root user.
    Red Hat Package Manager Systems
    Code:
    sudo chmod +x WowzaStreamingEngine-4.0.3.rpm.bin
    sudo ./WowzaStreamingEngine-4.0.3.rpm.bin
    Debian Package Manager Systems
    Code:
    sudo chmod +x WowzaStreamingEngine-4.0.3.deb.bin
    sudo ./WowzaStreamingEngine-4.0.3.deb.bin
    Other Linux and Unix Systems
    Download WowzaStreamingEngine-4.0.3.tar.bin to any directory and then execute the self-extracting installer:
    Code:
    sudo chmod +x WowzaStreamingEngine-4.0.3.tar.bin
    sudo ./WowzaStreamingEngine-4.0.3.tar.bin

    Starting (and stopping) the software


    Start (and stop) Wowza Streaming Engine

    You can start the Wowza Streaming Engine software either as a service or in standalone mode.

    Windows (service)


    To start the Wowza Streaming Engine service:

    1. Open the Services MMC snap-in (press WIN key + R, type services.msc in the Run dialog box, and then click OK).

    2. In the Services MMC snap-in, right-click Wowza Streaming Engine 4.0.3, and then click Start.

    To stop the service:

    1. Open the Services MMC snap-in (press WIN key + R, type services.msc in the Run dialog box, and then click OK).

    2. In the Services MMC snap-in, right-click Wowza Streaming Engine 4.0.3, and then click Stop.

    Windows (standalone)


    To start Wowza Streaming Engine in standalone mode, make sure that the Wowza Streaming Engine service is stopped (see above), and then do the following:

    1. Open a Command Prompt window (press WIN key + R, type cmd in the Run dialog box, and then press ENTER).

    2. Execute the following commands:
      Code:
      cd %WMSAPP_HOME%\bin
      startup.bat

    To stop the server:

    1. Open a Command Prompt window (press WIN key + R, type cmd in the Run dialog box, and then press ENTER).

    2. Execute the following commands:
      Code:
      cd %WMSAPP_HOME%\bin
      shutdown.bat

    Mac OS X (service)


    To start Wowza Streaming Engine as a Mac OS X launchd service, invoke the Start Services application in /Applications/WowzaStreamingEngine-4.0.3 or open a terminal window and enter the following command:
    Code:
    sudo launchctl load -w /Library/LaunchDaemons/com.wowza.WowzaStreamingEngine.plist
    To stop the service, invoke the Stop Services application in /Applications/WowzaStreamingEngine-4.0.3 or open a terminal window and enter the following command:
    Code:
    sudo launchctl unload -w /Library/LaunchDaemons/com.wowza.WowzaStreamingEngine.plist
    Note: Invoking the Start Services and Stop Services applications also starts and stops the Wowza Streaming Engine Manager system service. See Start (and stop) Wowza Streaming Engine Manager.

    Mac OS X (standalone)


    To start Wowza Streaming Engine in standalone mode, invoke the Start Standalone Mode application in /Applications/WowzaStreamingEngine-4.0.3 or open a terminal window and enter the following commands:
    Code:
    cd /Library/WowzaStreamingEngine-4.0.3/bin
    ./startup.sh
    To stop the server, invoke the Stop Standalone Mode application in /Applications/WowzaStreamingEngine-4.0.3 or open a terminal window and enter the following command:
    Code:
    cd /Library/WowzaStreamingEngine-4.0.3/bin
    ./shutdown.sh
    Note: Invoking the Start Standalone Mode and Stop Standalone Mode applications also starts and stops Wowza Streaming Engine Manager in standalone mode. See Start (and stop) Wowza Streaming Engine Manager.

    Linux (service)


    Note: The operations in this section must be performed as the root user with sudo access.
    To start Wowza Streaming Engine as a Linux service, open a terminal window and enter one of the following commands (the commands differ based on your Linux distribution):
    Code:
    sudo service WowzaStreamingEngine start
    -or-
    Code:
    /etc/init.d/WowzaStreamingEngine start
    To stop the service, enter:
    Code:
    sudo service WowzaStreamingEngine stop
    -or-
    Code:
    /etc/init.d/WowzaStreamingEngine stop
    Note: The method of running init.d-based services may be different on different Linux distributions. If these instructions don't apply to your Linux distribution, consult your Linux manual.

    Linux (standalone)


    To start the server in standalone mode, open a terminal window and enter the following commands:
    Code:
    cd /usr/local/WowzaStreamingEngine/bin
    ./startup.sh
    To stop the server, enter:
    Code:
    cd /usr/local/WowzaStreamingEngine/bin
    ./shutdown.sh

    Verify that Wowza Streaming Engine is running

    To verify that the Wowza Streaming Engine software is running, open a web browser and enter the following URL:
    http://[wowza-ip-address]:1935

    Where [wowza-ip-address] is the IP address or domain name of the local or remote Wowza server. It should return the Wowza Streaming Engine version number. If not, make sure that the server is running and that TCP port 1935 is open on your router, firewall, and/or software firewall (iptables on Linux).

    Start (and stop) Wowza Streaming Engine Manager

    You can start the Wowza Streaming Engine Manager software either as a service or in standalone mode.
    Note: Wowza Streaming Engine must be started to use Wowza Streaming Engine Manager. See Start (and stop) Wowza Streaming Engine.

    Windows (service)


    To start the Wowza Streaming Engine Manager service:

    1. Open the Services MMC snap-in (press WIN key + R, type services.msc in the Run dialog box, and then click OK).

    2. In the Services MMC snap-in, right-click Wowza Streaming Engine Manager 4.0.3, and then click Start.

    To stop the service:

    1. Open the Services MMC snap-in (press WIN key + R, type services.msc in the Run dialog box, and then click OK).

    2. In the Services MMC snap-in, right-click Wowza Streaming Engine Manager 4.0.3, and then click Stop.

    Windows (standalone)


    To start Wowza Streaming Engine Manager in standalone mode, make sure that the Wowza Streaming Engine Manager service is stopped (see above), and then do the following:

    1. Open a Command Prompt window (press WIN key + R, type cmd in the Run dialog box, and then press ENTER).

    2. Execute the following commands:
      Code:
      cd %WMSAPP_HOME%\manager\bin
      startmgr.bat

    To stop the manager:

    1. Open a Command Prompt window (press WIN key + R, type cmd in the Run dialog box, and then press ENTER).

    2. Execute the following commands:
      Code:
      cd %WMSAPP_HOME%\manager\bin
      shutdownmgr.bat

    Mac OS X (service)


    To start Wowza Streaming Engine Manager as a Mac OS X launchd service, invoke the Start Services application in /Applications/WowzaStreamingEngine-4.0.3 or open a terminal window and enter the following command:
    Code:
    sudo launchctl load -w /Library/LaunchDaemons/com.wowza.WowzaStreamingEngineManager.plist
    To stop the service, invoke the Stop Services application in /Applications/WowzaStreamingEngine-4.0.3 or open a terminal window and enter the following command:
    Code:
    sudo launchctl unload -w /Library/LaunchDaemons/com.wowza.WowzaStreamingEngineManager.plist
    Note: Invoking the Start Services and Stop Services applications also starts and stops the Wowza Streaming Engine system service. See Start (and stop) Wowza Streaming Engine.

    Mac OS X (standalone)


    To start the manager in standalone mode, invoke the Start Standalone Mode application in /Applications/WowzaStreamingEngine-4.0.3 or open a terminal window and enter the following commands:
    Code:
    cd /Library/WowzaStreamingEngine-4.0.3/manager/bin
    ./startmgr.sh
    To stop the manager, invoke the Stop Standalone Mode application in /Applications/WowzaStreamingEngine-4.0.3 or open a terminal window and enter the following commands:
    Code:
    cd /Library/WowzaStreamingEngine-4.0.3/manager/bin
    ./shutdownmgr.sh
    Note: Invoking the Start Standalone Mode and Stop Standalone Mode applications also starts and stops Wowza Streaming Engine in standalone mode. See Start (and stop) Wowza Streaming Engine.

    Linux (service)


    Note: The operations in this section must be performed as the root user with sudo access.
    To start the Streaming Engine Manager as a Linux service, enter one of the following commands (the commands differ based on your Linux distribution):
    Code:
    sudo service WowzaStreamingEngineManager start
    -or-
    Code:
    /etc/init.d/WowzaStreamingEngineManager start
    To stop the manager, enter:
    Code:
    sudo service WowzaStreamingEngineManager stop
    -or-
    Code:
    /etc/init.d/WowzaStreamingEngineManager stop
    Note: The method of running init.d-based services may be different on different Linux distributions. If these instructions don't apply to your Linux distribution, consult your Linux manual.

    Linux (standalone)


    To start the manager in standalone mode, open a terminal window and enter the following commands:
    Code:
    cd /usr/local/WowzaStreamingEngine/manager/bin
    ./startmgr.sh
    To stop the manager, enter:
    Code:
    cd /usr/local/WowzaStreamingEngine/manager/bin
    ./shutdownmgr.sh

    Perform a quick streaming test

    By default, the Wowza Streaming Engine installer creates a simple video on demand (VOD) application that enables you to quickly see if Wowza Streaming Engine is running properly and can serve content. To do this, do the following:

    1. Make sure that the Wowza Streaming Engine software is started on the server computer that you want to use (see Starting (and stopping) the software).

    2. Open Wowza Streaming Engine Manager in a web browser with the following URL:
      http://[wowza-ip-address]:8088/enginemanager

      Where [wowza-ip-address] is the IP address or domain name of the local or remote Wowza server that you want to test.

      Notes:
      • You can use Streaming Engine Manager with the latest versions of most modern web browsers that support HTML5 and Cascading Style Sheets level 3 (CSS 3). We recommend that you use the latest version of the Google Chrome browser for best results.
      • By default, Wowza Streaming Engine is configured to accept connections from Streaming Engine Manager on the localhost. For more information about how to connect to the Streaming Engine from a remote (non-localhost) computer, see How to connect to remote Streaming Engine installations (whitelist).
    3. Sign-in to Wowza Streaming Engine Manager with the Administrator account that you created when you installed the Wowza Streaming Engine software:



      Note: The user credentials are stored in the admin.password file in the Wowza Streaming Engine installation ([install-dir]/conf/admin.password).
    4. In Streaming Engine Manager, in the Test Video area of the Home page, click Test Players.



    5. In the Test Players dialog box, click the tab for the streaming protocol that you want to test and click the Start button.

    The test players for VOD applications are preconfigured to playback the [install-dir]/content/sample.mp4 video file that's installed with the server software. The following figure shows the Adobe HDS test player streaming the sample video.



    Administration


    About Wowza Streaming Engine Manager

    Wowza Streaming Engine™ Manager enables you to easily set up, manage, monitor, and measure streams using a web browser on your computer, tablet, or phone. By extending programmatic and command-line configuration and management of the Wowza Streaming Engine software to a web-based user interface, publishers with a diverse range of technical abilities can have greater control and confidence when streaming video. For details about how to navigate the Streaming Engine Manager user interface, see How to find your way around Wowza Streaming Engine Manager.

    Managing Sign-In credentials

    The first time you start Wowza Streaming Engine Manager, you'll be asked to sign in with the case-sensitive user name and password that you created when you installed the Streaming Engine software. This account has administrator access to enable control of the Streaming Engine through the manager. However, it doesn't provide access to advanced settings, which are reserved for expert Wowza users. Some server features have advanced settings on Properties and Server Listeners tabs to adjust the server configuration while applications and some application features have Properties and Modules tabs to adjust the application configuration.



    The tabs that provide access to the advanced properties and settings aren't visible unless the signed-in user has advanced permissions. After you sign in, you can enable access to the advanced settings for the default administrator account and add accounts for other users. You can create additional user accounts with both administrative and read-only access.

    To enable access to advanced settings for the default administrator account, do the following:

    1. In Streaming Engine Manager, click the Server tab and then click Users in the contents pane.

    2. On the Users page, click the Edit icon for the user name for the administrator account in the Users list.


    3. Select the Allow access to advanced properties and features check box.


    4. (Optional) Enter a new password in the Password and Confirm Password fields. The password values are case-sensitive.

    5. Click Save. As the signed-in user, you'll be signed-out automatically and must sign in to the manager again.

    Administrators can create accounts for other users with full administrative access to the Streaming Engine manager or with read-only privileges. To create new user accounts, do the following:

    1. In Streaming Engine Manager, click the Server tab and then click Users in the contents pane.

    2. On the Users page, click Add User.


    3. Configure settings for the new user.



      1. Enter a name for the user in User Name and a password for the user in Password and Confirm Password fields. The user name and password values are case-sensitive.

      2. Specify the access level (Read-Only or Administrator) for the new user by selecting the appropriate Access Level option.

      3. To enable the new user to either manage (Administrator user) or view (Read-Only user) advanced settings, select the Allow access to advanced properties and features check box.

      4. Click Add.

    Creating applications

    To begin using Wowza Streaming Engine, first create an application. An application is defined simply by clicking the Applications tab in Wowza Streaming Engine Manager and then selecting one of the following application types on the Add Application page.



    Live
    Use a Live application to deliver live streams to players (single server) or as an origin server to deliver live streams to other servers running Wowza Media Server® or Wowza Streaming Engine to scale content delivery to a large number of players. A default live application is included in the Wowza Streaming Engine installation.
    VOD
    Use a VOD application to stream video on demand (VOD) files to players (single server) or as an origin server to deliver VOD files to other servers running Wowza Media Server or Wowza Streaming Engine to scale content delivery to a large number of players. A default vod application is included in the Wowza Streaming Engine installation.
    Live Edge
    Use a Live Edge application to ingest live streams from a live application on an origin server that's running Wowza Media Server or Wowza Streaming Engine. This application is then used to deliver the live streams to players (single server).
    VOD Edge
    Use a VOD Edge application to ingest video on demand files from a Media Cache source. This application is then used to stream the VOD files to players (single server).
    Live HTTP Origin
    Use a Live HTTP Origin application to deliver live streams to an HTTP caching infrastructure using HTTP streaming protocols (MPEG-DASH, Apple HLS, Adobe HDS, and Microsoft Smooth Streaming).
    VOD HTTP Origin
    Use a VOD HTTP Origin application to deliver video on demand files to an HTTP caching infrastructure using HTTP streaming protocols (MPEG-DASH, Apple HLS, Adobe HDS, and Microsoft Smooth Streaming).

    For example, to create a new VOD application named myapplication, do the following:

    1. Click the VOD button:


    2. Enter the application name myapplication in the Add Application dialog box.


    3. Click Add.

    The application's default settings enable it to be used for simple video on demand streaming to Adobe Flash Player; Apple iPhone, iPad, or iPod touch devices; Microsoft Silverlight; DASH players, and RTSP/RTP-based players at the same time.



    For additional configuration details for all application types, refer to the following tutorials:


    Configuring properties

    Properties are a list of name/value pairs that provide a means for tuning and modifying the default application configuration. Properties can also be used server-side as a means to pass data to custom modules from applications. In Wowza Streaming Engine Manager, you can click the Properties tab on a feature or application page and enable default properties to either add them to the configuration or to override existing property values.


    Many articles on the Wowza website prescribe custom properties for tuning the server and for adding advanced functionality. Use the procedures in this section to configure the default properties and to add new properties.

    Note: Access to the Properties tab is limited to administrators with advanced permissions. For more information, see Managing Sign-In credentials.

    To configure properties


    1. In the Streaming Engine manager contents pane, click the server feature or application for which you want to configure properties.

    2. In the details page, click the Properties tab.

    3. In the Quick Links bar, click the link for the correct property section.

    4. In the property section, click Edit.

    5. To enable a property, click the Enabled check box for the property and then select the option True for the property (if required).

      - or -

      Click the Enabled check box for the property and then specify an appropriate Value.

    6. Click Save and then restart the server or application.

    To add a custom property


    1. In the Streaming Engine manager contents pane, click the server feature or application for which you want to add properties.

    2. In the details page, click the Properties tab.

    3. In the Quick Links bar, click Custom.

    4. In the Custom properties section, click Edit and then click the Add Custom Property button.

    5. Specify optional property settings in the Add Custom Property dialog box and then click Add.



    6. Click Save and then restart the server or application.

    Configuring modules

    Modules are Java classes that are loaded dynamically when an application instance is loaded and provide an application's functionality. In Wowza Streaming Engine Manager, the Modules list defines an order-dependent list of modules to be loaded for a given application. Many AddOn packages provide additional functionality through the use of modules. In the manager, click the Modules tab on an application page to see the list of modules that are loaded.

    Note: Access to the Modules tab is limited to administrators with advanced permissions. For more information, see Managing Sign-In credentials.


    Each module must have a unique Name. The Description information is for providing a detailed description of the module and isn't used in any operations. The Class item is the fully qualified path to the Java class that provides the module's functionality. In general, new modules are always added to the end of the Modules list. The Java class that makes up a server-side module is most often bound to a .jar file in the Streaming Engine installation. The Wowza Streaming Engine software comes with many modules that can be added to the Modules list to provide additional functionality. For a complete list of the modules, see "Built-in Server Modules" in the Wowza Streaming Engine User's Guide.

    You can use the Eclipse Integrated Development Environment (IDE) tool to develop your own custom modules to provide additional functionality. Wowza also provides a collection of custom utility modules that are ready to use in Wowza applications. (For more information, see Module Collection.)

    To add a custom module


    1. In Wowza Streaming Engine Manager, click the desired live application in the contents pane.

    2. In the details page, click the Modules tab.

    3. Click Edit and then click the Add Module button.

    4. Specify the required module entries in the Add New Module dialog box and then click Add:



    5. Click Save and then restart the application.

    Configuring server listeners

    Server listeners are Java classes in the Wowza Streaming Engine object hierarchy that implement a notifier interface for notification of specific events at the server level. Listener methods are called for each listener in the order that they appear on the Server Listeners tab for the Server Setup feature in Wowza Streaming Engine Manager.

    Note: Access to the Server Listeners tab is limited to administrators with advanced permissions. For more information, see Managing Sign-In credentials.


    The Fully Qualified Class Name item is the fully qualified path to the Java class that provides the server listener's functionality.

    You can use event listeners to capture certain events in order to extend the server functionality. Server event listeners and VHost event listeners are called when events occur at a server or VHost level. Other event listeners can be invoked using API methods and are called when events occur that the listener is configured to listen for. For more information about these methods, see the Wowza Streaming Engine Server-Side API. Wowza also includes server listeners in its Module Collection that are ready to use with the Wowza server software.

    To add a custom server listener


    1. In Wowza Streaming Engine Manager, click the Server tab and then click Server Setup in the contents pane.

    2. In the details page, click the Server Listeners tab.

    3. Click Edit and then click the Add Server Listener button.

    4. Specify the required server listener entries in the Add Server Listener dialog box and then click Add:



    5. Click Save and then restart the server.

    Configuring streaming ports

    When you are ready to make your Wowza server available to the public Internet, you will need to make sure that the appropriate ports are open on your firewall. Wowza Streaming Engine uses the following default ports for streaming:
    Note: This will require connecting and modifying settings in the core router / firewall in your server networking environment. A typical enterprise environment will likely require approval and the assistance of a network administrator. In home or small offices, this involves configuring "port forwarding" traffic, on a particular port, to the port and IP address of your server (see your router / firewall documentation on "Port Forwarding" for more information).
    TCP 1935 RTMP/RTMPE/RTMPT/RTSP-interleaved streaming/WOWZ™
    TCP 8086-8088 Administration
    UDP 6970-9999 RTP UDP streaming

    By default, Wowza Streaming Engine is configured to use only TCP port 1935 for streaming. You may want to configure additional ports for streaming such as TCP port 80 for HTTP or RTMPT streaming or TCP port 554 for RTSP streaming. To add an additional port, go to the Virtual Host Setup page in Wowza Streaming Engine Manager and edit the Default Streaming host port.

    Wowza Streaming Engine can not share ports with other programs or services, so make sure that there are no other programs or services running that share the added ports. The following ports are also commonly used for streaming:

    TCP 80 Adobe HDS, Apple HLS, Microsoft Smooth Streaming, MPEG-DASH streaming, RTMPT
    TCP 443 RTMPS, HTTPS
    TCP 554 RTSP



    In the Edit host port dialog box, add the additional ports to the Port(s) list (this list is comma-delimited).



    Adding new license keys

    License keys for all Wowza® products, including the Wowza Streaming Engine software and AddOns, are stored in the Server.license file in the Wowza Streaming Engine installation ([install-dir]/conf/Server.license). Subscription users can run an unlimited number of server instances and AddOns under a single license key. Perpetual Edition users must enter a separate license key for each server instance and for each AddOn.

    To add a license key in Wowza Streaming Engine Manager, do the following:

    1. Click the Server tab and then click Server Setup in the contents pane.

    2. In the Server Setup page, click Edit.

    3. Enter each new license key on a new line in the License Keys box, and then click Save.

    4. Click the Restart Now button at the top of the Server Setup page.

    After the standalone server is restarted, the new license(s) are in effect. The licenses are additive, so when adding additional licenses, be sure to retain the original license information in the License Keys box and add each new license key on its own new line. The order in which the keys are listed isn't important. The first and last five digits of the license key are displayed in the License Keys box:



    Tuning for performance

    Wowza Streaming Engine is automatically tuned to take best advantage of available hardware resources when the server starts. The server calculates an appropriate Java heap size, garbage collection (GC) settings, and other Java command-line options based on available hardware, the computer and Java Virtual Machine (JVM) bitness, and other factors.

    By default, the server sets the Java heap size to a value that's suitable for application development environments. Before you deploy the server in production environments where it may use memory extensively when heavily loaded, you can select an option in Wowza Streaming Engine Manager that automatically sets the heap size to a predefined value that's appropriate for production use. You can also adjust many other performance settings from the default values that are calculated by the server in Streaming Engine Manager to fine-tune the server's performance. For more information, see Performance Tuning.

    Logging

    Wowza Streaming Engine log files are written to [install-dir]/logs. The default logging level (INFO) enables monitoring and collects information to help troubleshoot most issues while adding minimal load to the server. When working with Wowza to troubleshoot an issue, you may be asked to temporarily turn on debug logging (increase the amount of information written to the logs). To do this, open [install-dir]/conf/log4j.properties in a text editor and change the log level on the first line from INFO to DEBUG. Debug logging shouldn't be used in a production environment due to its increased load on the server.

    Installing example applications

    The Wowza Streaming Engine software includes example streaming applications that highlight the server functionality and to help you get started. The examples are located in [install-dir]/examples. After you install Wowza Streaming Engine, you can install the example streaming applications and configure the application settings in Wowza Streaming Engine Manager.

    Windows


    Select: Start > All Programs (or All Apps) > Wowza Streaming Engine 4.0.3 > Examples
    Double-click: installall.bat

    Mac OS X


    Open folder: /Library/WowzaStreamingEngine-4.0.3/examples
    Double-click: installall.command

    Linux


    Enter the following commands in a terminal window:
    Code:
    cd /usr/local/WowzaStreamingEngine-4.0.3/examples
    ./installall.sh
    In a default installation of Wowza Streaming Engine, fully functional live and vod applications are included; therefore, the example applications aren't installed for these application types:



    After the example applications are installed, go to the Server Setup page in Streaming Engine Manager and click the Restart Server button in the upper-right corner of the page. Then click the Applications tab in the manager to see the installed example applications in the contents pane.



    Notes:
    • You may need to refresh the Streaming Engine Manager web browser to see the example applications in the contents pane.
    • See the README.html file in the examples root folder ([install-dir]/examples/README.html) for more information about the example applications.

    Getting help

    Support is available in the following ways:

    • Wowza Support
      Learn about the Wowza Support Policy and how to get help for Wowza Streaming Engine.
    • Wowza Articles
      Find articles to help you get up-and-running and to resolve many common issues.
    • Wowza Forums
      Get help from Wowza Streaming Engine experts around the world.

    Streaming concepts


    Streaming protocols

    A single application can be configured to deliver a stream to Adobe Flash Player; Microsoft Silverlight; Apple iPhone, iPad, or iPod touch devices; DASH players, and RTSP/RTP-based players at the same time using the streaming protocols that are described in this section.

    Adobe HDS (Adobe Flash Player)


    Wowza Streaming Engine can stream adaptive bitrate live and video on demand (VOD) content to Adobe Flash Player 10.1 or later using the Adobe HTTP Dynamic Streaming (Adobe HDS) protocol. Adobe HDS is a chunk-based streaming protocol that uses HTTP for delivery. All media-chunking and packaging necessary to deliver a stream using this protocol is performed by the Streaming Engine software. Adobe HDS is referred to as "San Jose" streaming in the Streaming Engine configuration files.

    When streaming VOD content over Adobe HDS, Wowza Streaming Engine supports MP4 files (QuickTime container) and MP3 files. FLV files aren't supported. The Streaming Engine supports the following video and audio codecs when using this streaming protocol:

    Video
    • H.264
    • On2 VP6 (live only)
    • Screen video and Screen video 2 (live only)
    • Sorenson Spark (live only)

    Audio
    • AAC, AAC Low Complexity (AAC LC), AAC High Efficiency (HE-AAC) v1 and v2
    • MP3
    • Nellymoser Asao (live only)
    • Speex (live only)

    Adobe HDS streaming leverages an XML manifest file to describe the list of chunks available for streaming. An Adobe HDS streaming playlist URL has the following form:
    http://[wowza-ip-address]/[application]/[application-instance]/[stream-name]/manifest.f4m

    • [wowza-ip-address]: IP address or domain name and port of the the Wowza server (default port 1935)
    • [application]: Application name
    • [application-instance]: Application instance name (if omitted, defaults to _definst_)
    • [stream-name]: Stream name with stream prefix

    For example, to play the VOD file mycoolvideo.mov located on the Wowza server at the address mycompany.com, using the application name myapplication, the URL is:
    http://mycompany.com:1935/myapplication/mp4:mycoolvideo.mov/manifest.f4m

    Adobe HDS streaming requires a Flash-based player that's built using the Open Source Media Framework (OSMF). The Wowza Streaming Engine software installation has the following OSMF-based example players:

    • [install-dir]/examples/VideoOnDemandStreaming/FlashHTTPPlayer/player.html
    • [install-dir]/examples/LiveVideoStreaming/FlashHTTPPlayer/player.html

    For more information about Adobe HDS streaming, see the Wowza Streaming Engine User's Guide.

    Apple HLS (iPhone, iPad, iPod touch, QuickTime, and more)


    Wowza Streaming Engine can stream adaptive bitrate live and VOD H.264, AAC, and MP3 content to iOS-based devices (iPhone/iPad/iPod touch iOS version 3.0 or later), QuickTime player (version 10 or later), Safari browser (version 4.0 or later), and other devices such as the Roku and Amino set-top boxes and some brands of smart TVs using the Apple HTTP Live Streaming (Apple HLS) protocol. Apple HLS is a chunk-based streaming protocol that uses HTTP for delivery. All media-chunking and packaging necessary to deliver a stream using this protocol is performed by the Streaming Engine. Apple HLS is referred to as "Cupertino" streaming in the Streaming Engine configuration files.

    Wowza Streaming Engine populates the playlist file with metadata that describes each of the available streams in an adaptive bitrate presentation. This enables iOS-based players to intelligently select the appropriate streams based on hardware device capabilities.

    The Streaming Engine supports the following video and audio codecs when using this streaming protocol:

    Video
    • H.264

    Audio
    • AAC, AAC Low Complexity (AAC LC), High Efficiency AAC (HE-AAC) v1
    • Dolby Digital 5.1 Surround Sound (AC-3) and Dolby Digital Plus (Enhanced AC-3 or E-AC-3)
    • MP3

    Apple HLS streaming leverages a playlist wrapper to describe the list of chunks available for streaming. An Apple HLS streaming playlist URL has the following form:
    http://[wowza-ip-address]/[application]/[application-instance]/[stream-name]/playlist.m3u8

    • [wowza-ip-address]: IP address or domain name and port of the Wowza server (default port 1935)
    • [application]: Application name
    • [application-instance]: Application instance name (if omitted, defaults to _definst_)
    • [stream-name]: Stream name with stream prefix

    For example, to play the VOD file mycoolvideo.mov located on the Wowza server at the address mycompany.com, using the application name myapplication, the URL is:
    http://mycompany.com:1935/myapplication/mp4:mycoolvideo.mov/playlist.m3u8

    The Wowza Streaming Engine software installation has the following Apple HLS-based example players:

    • [install-dir]/examples/VideoOnDemandStreaming/IOSMacOSX/player.html
    • [install-dir]/examples/LiveVideoStreaming/IOSMacOSX/player.html

    For more information about Apple HLS streaming, see the Wowza Streaming Engine User's Guide.

    Microsoft Smooth Streaming (Microsoft Silverlight and more)


    Wowza Streaming Engine can stream adaptive bitrate live and VOD H.264, AAC, and MP3 content to Microsoft Silverlight, Windows Phone devices, and other devices using the Microsoft Smooth Streaming protocol. Microsoft Silverlight is a cross-browser, cross-platform technology that exists on many personal computing devices. Smooth Streaming is a chunk-based streaming protocol that uses HTTP for delivery. All media chunking and packaging necessary to deliver a stream using this protocol is performed by the Streaming Engine so there's no need for an IIS web server.

    The Streaming Engine supports the following video and audio codecs when using this streaming protocol:

    Video
    • H.264

    Audio
    • AAC, AAC Low Complexity (AAC LC), AAC High Efficiency (HE-AAC) v1 and v2
    • Dolby Digital 5.1 Surround Sound (AC-3) and Dolby Digital Plus (Enhanced AC-3 or E-AC-3)
    • MP3

    Smooth Streaming leverages a playlist wrapper (called a manifest) to describe the list of chunks that are available for streaming. A Smooth Streaming manifest URL has the following form:
    http://[wowza-ip-address]/[application]/[application-instance]/[stream-name]/Manifest

    • [wowza-ip-address]: IP address or domain name and port of the Wowza server (default port 1935)
    • [application]: Application name
    • [application-instance]: Application instance name (if omitted, defaults to _definst_)
    • [stream-name]: Stream name with stream prefix

    For example, to play the VOD file mycoolvideo.mov, located on the Wowza server at the address mycompany.com, using the application name myapplication, the URL is:
    http://mycompany.com:1935/myapplication/mp4:mycoolvideo.mov/Manifest

    The Wowza Streaming Engine software installation has the following Smooth Streaming-based example players:

    • [install-dir]/examples/VideoOnDemandStreaming/SilverlightPlayer/player.html
    • [install-dir]/examples/LiveVideoStreaming/SilverlightPlayer/player.html

    For more information about Smooth Streaming, see the Wowza Streaming Engine User's Guide.

    MPEG-DASH streaming (DASH clients)


    Dynamic Adaptive Streaming over HTTP (DASH), also known as MPEG-DASH, is a new international standard for adaptive streaming that's being adopted by the streaming industry. Wowza Streaming Engine includes MPEG-DASH technology for streaming live and VOD content over HTTP to select DASH clients. MPEG-DASH is similar to proprietary adaptive streaming technologies such as Adobe HDS, Apple HLS, and Microsoft Smooth Streaming in that it's a chunk-based streaming technology that uses HTTP for delivery. All media-chunking and packaging necessary to deliver a stream using this technology is performed by the Streaming Engine. Note that in MPEG-DASH terminology, chunks are called "segments."

    The Streaming Engine supports the following video and audio codecs when using this streaming protocol:

    Video
    • H.264

    Audio
    • AAC, AAC Low Complexity (AAC LC), AAC High Efficiency (HE-AAC) v1 and v2
    • Dolby Digital 5.1 Surround Sound (AC-3) and Dolby Digital Plus (Enhanced AC-3 or E-AC-3)

    An MPEG-DASH server provides DASH clients with a list of the available media chunk URLs in a Media Presentation Description (MPD) manifest. The MPD describes chunk information such as timing, language, timed text, and media characteristics (video resolution and bitrate). Clients sequentially request media chunks based on network conditions, device capabilities, and other factors to enable uninterrupted playback of the adaptive bitrate media presentation. An MPEG-DASH MPD manifest URL has the following form:
    http://[wowza-ip-address]/[application]/[application-instance]/[stream-name]/manifest_mp[manifest-profile]_mv[manifest-variation].mpd

    • [wowza-ip-address]: IP address or domain name and port of the Wowza server (default port 1935)
    • [application]: Application name
    • [application-instance]: Application instance name (if omitted, defaults to _definst_)
    • [stream-name]: Stream name with stream prefix
    • manifest-profile]: The manifest chunk profile (container and encoding formats). For details, see MPD URL syntax.
    • manifest-variation]: The chunk-addressing scheme token. For details, see MPD URL syntax.

    For example, to play the VOD file mycoolvideo.mov, located on the Wowza server at the address mycompany.com, using the application name myapplication, the URL is:
    http://mycompany.com:1935/myapplication/mp4:mycoolvideo.mov/manifest_mpm4sav_mvlist.mpd

    The Wowza Streaming Engine software installation has the following DASH-based example players:

    • [install-dir]/examples/VideoOnDemandStreaming/MPEGDASHPlayer/player.html
    • [install-dir]/examples/LiveVideoStreaming/MPEGDASHPlayer/player.html

    The MPEG-DASH standard (ISO/IEC 23009-1) defines segment container formats for ISO Base Media File Format (ISOBMFF) and MPEG-2 Transport Streams (MPEG-2 TS). MPEG-DASH is codec-agnostic and supports multiplexed and non-multiplexed encoding. Multiple content protection (DRM) schemes are supported; however, a Common Encryption (CENC) standard (ISO/IEC 23001-7) is being developed in conjunction with MPEG-DASH to allow content to be encrypted once and then streamed to DASH clients that support different licensing systems. For more information about MPEG-DASH support in Wowza Streaming Engine, see the Wowza Streaming Engine User's Guide.

    Adobe RTMP (Adobe Flash Player)


    Wowza Streaming Engine communicates with Adobe Flash Player using the Real Time Messaging Protocol (RTMP). The Streaming Engine can deliver adaptive bitrate live and VOD content to Flash Player using RTMP and it supports other features such as shared objects, video recording, video chat, remote procedure calls, and more. The Streaming Engine supports all video and audio formats that Flash Player supports:

    Video
    • H.264
    • On2 VP6
    • Sorenson Spark
    • Screen video and Screen video 2

    Audio
    • AAC, AAC Low Complexity (AAC LC), AAC High Efficiency (HE-AAC) v1 and v2
    • MP3
    • Speex
    • Nellymoser Asao

    Adobe Flash Player is a cross-browser, cross-platform technology that exists on many personal computing and mobile devices. The Adobe Flash plugin runs SWF files that are generated by Flash authoring tools such as the Adobe Flash authoring tool and Adobe Flex. ActionScript is the most common Flash programming language. Using ActionScript, an SWF file can be programmed to do many things within a webpage including playback of streaming media.

    Wowza Streaming Engine and Adobe Flash Player communicate using a NetConnection object and media is streamed using a NetStream object. The NetConnection.connect method is used to establish a connection between the Wowza server and Adobe Flash Player. It takes an RTMP URL in the following form:
    [protocol-method]://[wowza-ip-address]/[application]/[application-instance]

    • [protocol-method]: rtmp, rtmpe (encryption), rtmpt (tunneling), rtmpte (encryption and tunneling), or rtmps (tunneling over SSL)
    • [wowza-ip-address]: IP address or domain name and port of the Wowza server (default port 1935)
    • [application]: Application name
    • [application-instance]: Application instance name (if omitted, defaults to _definst_)

    For example, to connect to a Wowza server at the address mycompany.com, using the application name myapplication, the URL to use in the NetConnection.connect method is:
    rtmp://mycompany.com/myapplication

    The NetStream.play method is used to start streaming. It takes as its first argument a stream name. For example, to play the media file mycoolvideo.mov, you would use the stream name mp4:mycoolvideo.mov. Some pre-built players combine the server connection URL used in the NetConnection.connect method and the stream name used in the NetStream.play method into a single URL. This URL takes the form:
    [protocol-method]://[wowza-ip-address]/[application]/[application-instance]/[stream-name]

    For example, to connect to a Wowza server at the address mycompany.com, using the application name myapplication to play the video on-demand file named mycoolvideo.mov, the URL is:
    rtmp://mycompany.com/myapplication/mp4:mycoolvideo.mov

    Adobe RTMP streaming requires a Flash-based player that's built using the Open Source Media Framework (OSMF). The Wowza Streaming Engine software installation has the following OSMF-based example players:

    • [install-dir]/examples/VideoOnDemandStreaming/FlashRTMPPlayer/player.html
    • [install-dir]/examples/LiveVideoStreaming/FlashRTMPPlayer/player.html

    For more information about Flash streaming, see the Wowza Streaming Engine User's Guide.

    RTSP/RTP (QuickTime, VLC, 3GPP devices, set-top boxes, and more)


    Wowza Streaming Engine can stream live H.264, AAC, and MP3 content to players and devices that support the Real Time Streaming Protocol (RTSP), Real-time Transport Protocol (RTP), and MPEG-2 Transport Stream protocol (MPEG-2 TS). This includes players and devices such as QuickTime player (version 10 or later), VideoLAN VLC player, set-top boxes, and 3GPP devices. The Streaming Engine can also accept incoming streams from encoding devices that use these protocols. The Streaming Engine supports RTP and MPEG-2 TS input and output over UDP as well as multicast. In addition, the Streaming Engine supports interleaved RTSP/RTP (RTP over the RTSP TCP connection) and RTSP/RTP tunneling (RTSP/RTP over HTTP), which enables RTSP/RTP to be delivered in network environments that don't allow UDP transmission..

    An RTSP/RTP URL in Wowza Streaming Engine has the following form:
    rtsp://[wowza-ip-address]/[application]/[application-instance]/[stream-name]

    • [wowza-ip-address]: IP address or domain name and port of the Wowza server (default port 1935)
    • [application]: Application name
    • [application-instance]: Application instance name (if omitted, defaults to _definst_)
    • [stream-name]: Stream name with stream prefix

    For example, to play the live stream with the stream name mylivestream, located on the Wowza server at the address mycompany.com, using the application name myapplication, the URL is:
    rtsp://mycompany.com:1935/myapplication/mylivestream

    For more information about RTSP-based streaming, see the Wowza Streaming Engine User's Guide.

    Supported media file formats

    Wowza Streaming Engine supports the MP4 (QuickTime container), FLV (Flash Video), and MP3 media file formats. (See the list below for common file extensions.) To play video on demand content, the proper prefix must be prepended to the file name to create a stream name. For example, to play the MP4 file mycoolvideo.mov, use the stream name mp4:mycoolvideo.mov. The following list shows the more common file type prefixes (for a complete list, see "Media Types" in the Wowza Streaming Engine User's Guide):

    MP4 (QuickTime container)


    This is the default media type so the file name prefix and extension can be omitted.
    Prefix: mp4:
    Extensions: .mp4, .f4v, .mov, .m4a, .m4v, .mp4a, .mp4v, .3gp, .3g2
    Example: mp4:mycoolvideo.mov

    FLV (Flash Video)


    Prefix: flv:
    Extension: .flv
    Example: flv:mycoolvideo.flv

    MP3


    Prefix: mp3:
    Extension: .mp3
    Example: mp3:mycoolsong.mp3

    SMIL


    XML file used to configure adaptive bitrate streams. For more information, see How to do adaptive bitrate streaming.
    Prefix: smil:
    Extension: .smil
    Example: smil:myStream.smil

    Content storage

    By default, Wowza Streaming Engine is configured to stream VOD content from (and record VOD content to) the [install-dir]/content folder. You can specify a different storage location for a VOD application in Wowza Streaming Engine Manager by changing the Content Directory value for the application. For example, to configure an application to use an application-specific content folder, you can select the Application-specific directory option:



    Using this setting, content is streamed from the [install-dir]/content/[application] folder, where [application] is the application's name.

    Files that are required for streaming live content, such as Session Description Protocol (SDP) files or .stream files are also stored in the [install-dir]/content folder by default. You can specify a different storage location for a live application in Streaming Engine Manager by changing the Streaming File Directory value for the application. For example, to configure an application to use an application-specific folder, you can select the Application-specific directory option:



    Using this setting, the files can be accessed from the [install-dir]/content/[application] folder, where [application] is the application's name.

    You can further customize content storage for your applications by specifying the fully qualified path to the storage location in the Use the following directory box. You can substitute variables in place of path elements. The following variables are supported:

    ${com.wowza.wms.AppHome} Application home directory
    ${com.wowza.wms.ConfigHome} Configuration home directory
    ${com.wowza.wms.context.VHost} Virtual host name
    ${com.wowza.wms.context.VHostConfigHome} Virtual host configuration directory
    ${com.wowza.wms.context.Application} Application name
    ${com.wowza.wms.context.ApplicationInstance} Application instance name

    Updated: For Wowza Streaming Engine 4.0.3 on 03-27-2014