• Quick Start Guide


    Table of Contents


    Introduction
    Streaming Concepts
    Installation and Configuration
    Administration

    Introduction



    Overview


    This article is a very short and quick tutorial to get you started with Wowza Media Server 3. Wowza Media Server 3 is a high performance media streaming server software for delivering content to the following player technologies and devices: Adobe Flash® (Adobe Flash player), Microsoft Smooth Streaming (Microsoft Silverlight® player), Apple HTTP Live Streaming (iPhone®, iPad™, iPod® touch, Safari® browser, QuickTime™ player), Real Time Streaming Protocol (RTSP/RTP) (QuickTime player and VLC media player and many mobile devices) and MPEG2 Transport Streams (MPEG-TS) (set-top boxes and IPTV solutions).

    Wowza Media Server 3 has three AddOn features:
    • Wowza Transcoder™ AddOn
    • Wowza nDVR™ AddOn
    • Wowza DRM™ AddOn

    Documentation for these features and Wowza Media Server 3 User's Guide can be found here:
    Wowza Media Server 3 Documentation

    For more up to date information visit the online forums at: http://www.wowza.com/forums. Wowza Server also provides some great examples to get your started. Once the server is installed, the examples are located at: [install-dir]/examples (see the README.html file at the root of the examples folder).

    This guide refers to third party software that is not licensed, sold, distributed or otherwise endorsed by Wowza® . Please ensure that any and all use of Wowza® software and third party software is properly licensed.

    Throughout this document and in other Wowza Media Server documentation we will refer to [install-dir] as the folder to which Wowza Media Server was installed. The installation folder differs based on platform:

    • Windows: C:\Program Files\Wowza Media Systems\Wowza Media Server [version]
    • Mac OSX: /Library/WowzaMediaServer
    • Linux/Unix: /usr/local/WowzaMediaServer

    To obtain free support, either visit the Wowza forum or send email to support@wowza.com.
    When emailing support@wowza.com be sure to provide the following information:
    • Wowza Media Server 3 version and build number
    • Platform, operating system and Java version on which Wowza Media Server is running
    • Detailed description of problem which includes the following:

    1. URL of tutorial or instructions being used
    2. Player technology being used (Adobe Flash, Microsoft Silverlight, iOS device, Set-top box...)
    3. Zip up and send [install-dir]/logs, [install-dir]/conf and [install-dir]/transcoder folders
    4. Live encoder/IP camera manufacturer/version and exact encoding settings (live streaming only)


    Streaming Concepts



    Application Configuration


    To begin using Wowza Media Server 3, first create an application. An application is defined simply by creating a folder in the [install-dir]/applications folder. For example, to create a new application named myapplication, create the folder:

    [install-dir]/applications/myapplication

    The application is now ready to use for simple video on demand streaming. It will use the default configuration file which is located in the [install-dir]/conf folder:

    [install-dir]/conf/Application.xml (Default configuration file)

    To give an application its own Application.xml instead of using the default configuration file, create a folder with the same name in the [install-dir]/conf folder and copy the default configuration file to the new folder.


    [install-dir]/conf/myapplication/Application.xml (Configuration file for myapplication)

    It is a common mistake to put the Application.xml file in the [install-dir]/applications/[application] folder. All configuration files for Wowza Server and its applications are in the [install-dir]/conf folder.

    A single application can be configured to deliver a live or video on demand stream to the Adobe Flash player, the Silverlight player, an Apple iPhone, iPad or iPod touch device and an RTSP/RTP based player at the same time.

    Consult the User's Guide for more details on the configuration items defined in Application.xml.


    Stream Types


    In Wowza Media Server 3, MediaStreams represent an incoming or outgoing stream of video, audio or metadata. Wowza Server provides a mechanism for defining custom server-side MediaStream implementations or stream types. These stream types are configured using the Streams/StreamType property in the Application.xml file. The following table lists the more commonly used stream types and their intended use (for a complete list, consult the User's Guide):

    • default: Video on demand streaming of static Flash media, H.264/AAC and MP3 content
    • record: Video recording
    • live: Publish and play live video content (best for one-to-many streaming of live events)
    • live-lowlatency: Publish and play live video content (best for one-to-one or one-to-few video/audio chat applications)
    • live-record: Same as live plus content will be recorded
    • shoutcast: Audio re-streaming of a SHOUTcast/Icecast MP3 or AAC+ audio stream
    • shoutcast-record: Same as shoutcast plus content will be recorded
    • liverepeater-origin: Origin stream type used by live stream repeater to deliver a single streaming using origin/edge configuration
    • liverepeater-edge: Edge stream type used by live stream repeater to deliver a single stream using origin/edge configuration
    • rtp-live: Re-streaming of an RTSP/RTP, native RTP or MPEG-TS stream
    • rtp-live-record: Same as rtp-live plus content will be recorded


    Supported Media


    Wowza Media Server 3 supports the following media file formats: FLV (Flash Video), MP4 (QuickTime container) and MP3 content (see table 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 table lists the more common file type prefixes (for a complete list consult the User's Guide):

    • flv: FLV (Flash Video - this is the default media type so the qualifier and the file extension can be omitted)

      Example: "flv:mycoolvideo.flv"

    • mp4: MP4 (QuickTime container - .mp4, .f4v, .mov, .m4v, .mp4a, .3gp, and .3g2)

      Example: "mp4:mycoolvideo.mov"

    • mp3: MP3 (.mp3)

      Example: "mp3:mycoolsong.mp3"

    • smil: SMIL (XML files used to configure multi-bitrate streams - .smil)


    Content Storage


    Wowza Media Server e is configured by default to use a single content directory which is located at [install-dir]/content. You can change the default content location on an application by application basis by changing the Streams/StorageDir property in Application.xml to the desired content path.


    Wowza Media Server for Amazon EC2


    Wowza Media Systems has teamed with Amazon Web Service to make billing quick, easy, and secure for the combination of Wowza Media Server 2, machine time with various EC2 instances and bandwidth. For more information:

    Wowza Media Server 2 for Amazon EC2 Details
    Wowza Media Server 2 for Amazon EC2 Support Center


    Real Time Messaging Protocol (RTMP - Adobe Flash Player)


    Wowza Media Server 3 can stream multi-bitrate live and video on demand content to the Adobe Flash player over RTMP. Wowza Server is a great alternative to Flash Media Interactive Server (FMIS) and Flash Media Streaming Server (FMSS). It supports media streaming as well as other features such as: Shared Objects, video recording, video chat, remote procedure calls and more. Wowza Media Server 3 supports all video and audio formats that the Flash player supports:

    Video

    • H.264
    • VP6
    • SorensonSpark
    • Screen Shared codec

    Audio

    • AAC - AAC, AAC Low Complexity (AAC LC), High Efficiency AAC v1 and v2 (HE-AAC)
    • MP3
    • Speex
    • NellyMoser ASAO

    The 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, a SWF file can be programmed to do many things within a web page including playing streaming media. Wowza Server and the 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 Wowza Server and the Flash player. The NetConnection.connect method takes an RTMP URL in the following form:

    [protocol-method]://[wowza-address]/[application]/[application-instance]

    where:

    • [protocol-method]: rtmp, rtmpe (encryption), rtmpt (tunneling), rtmpte (encryption and tunneling) or rtmps (tunneling over ssl)
    • [wowza-address]: IP address or domain name and port of server running 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 Media Server 3 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 playesr 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-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

    For more details regarding Flash streaming including secure streaming using SecureToken and RTMPE and multi-bitrate streaming, see the User's Guide.


    Flash HTTP Streaming (Adobe Flash Player)


    Wowza Media Server 3 can stream multi-bitrate live and video on demand content to Flash player 10.1 or greater using the Flash HTTP Streaming protocol. Flash HTTP 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 Wowza Server. Flash HTTP Streaming is referred to in the Wowza Server documentation and configuration files as San Jose Streaming. When streaming video on demand content, Wowza Server supports MP4 files (QuickTime container) and MP3 files (FLV files are not supported at this time).

    San Jose streaming leverages an XML manifest file to describe the list of chunks available for streaming. A San Jose streaming playlist URL has the following form:

    http://[wowza-address]/[application]/[application-instance]/[stream-name]/manifest.f4m

    where:

    • [wowza-address]: IP address or domain name and port of server running 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 video on demand file located on the Wowza Media Server 3 at the address mycompany.com, using the application name myapplication with the file name mycoolvideo.mov, the URL is:

    http://mycompany.com:1935/myapplication/mp4:mycoolvideo.mov/manifest.f4m

    As of the writing of this document, Wowza Media Server 3 supports the following video and audio codecs when using this streaming protocol:

    Video

    • H.264
    • VP6 (live only)
    • SorensonSpark (live only)
    • Screen Shared codec (live only)

    Audio

    • AAC - AAC, AAC Low Complexity (AAC LC), High Efficiency AAC v1 and v2 (HE-AAC)
    • MP3
    • Speex (live only)
    • NellyMoser ASAO (live only)

    Note: San Jose Streaming requires a Flash based player that is built using the Open Source Media Framework (OSMF). Wowza Media Server 3 ships with several OSMF based players in the examples folder:

    • [install-dir]/examples/SimpleVideoStreaming/clientOSMF/bin-release/SimpleOSMFPlayer.html
    • [install-dir]/examples/LiveVideoStreaming/clientOSMF/bin-release/LiveOSMFPlayer.html


    Apple HTTP Live Streaming (Cupertino Streaming - iPhone, iPad, iPod touch)


    Wowza Media Server 3 can stream multi-bitrate live and video on demand H.264, AAC and MP3 content to the iPhone, iPad, iPod touch, and specific versions of QuickTime player and the Safari browser using the Apple HTTP Live Streaming protocol. Apple HTTP Live Streaming is a chunked based streaming protocol that uses HTTP for delivery. All media chunking and packaging necessary to deliver a stream using this protocol is performed by Wowza Server. Apple HTTP Live Streaming is referred to in the Wowza Media Server 3 documentation and configuration files as Cupertino Streaming.

    Cupertino streaming leverages a playlist wrapper to describe the list of chunks available for streaming. A Cupertino Streaming playlist URL has the following form:

    http://[wowza-address]/[application]/[application-instance]/[stream-name]/playlist.m3u8

    where:

    • [wowza-address]: IP address or domain name and port of server running 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 video on demand file located on the Wowza Media Server 3 at the address mycompany.com, using the application name myapplication with the file name mycoolvideo.mov, the URL is:

    http://mycompany.com:1935/myapplication/mp4:mycoolvideo.mov/playlist.m3u8

    The iPhone, iPad and iPod touch support the following video and audio formats:

    Video

    • H.264 (Baseline profiile level 3.0 or below)

    Audio

    • AAC, AAC Low Complexity (AAC LC), High Efficiency AAC v1 (HE-AAC)
    • MP3

    The iPhone, iPad and iPod touch do not support High Efficiency AAC v2.

    For more details regarding Cupertino Streaming, including secure streaming using AES-128 encryption and multi-bitrate streaming, see the User's Guide.


    Smooth Streaming (Microsoft Silverlight)


    Wowza Media Server 3 can stream multi-bitrate live and video on demand H.264, AAC and MP3 content to the Microsoft Silverlight player using the Smooth Streaming protocol. Smooth Streaming is a chunked-based streaming protocol that uses HTTP for delivery. All media chunking and packaging necessary to deliver a stream using this protocol is performed by Wowza Server. Microsoft Silverlight is cross-browser, cross-platform technology that exists on many personal computing devices.

    Smooth Streaming leverages a playlist wrapper called the Manifest to describe the list of chunks available for streaming. A Smooth Streaming Manifest URL has the following form:

    http://[wowza-address]/[application]/[application-instance]/[stream-name]/Manifest

    where:

    • [wowza-address]: IP address or domain name and port of server running 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 video on demand file located on the Wowza Media Server 3 at the address mycompany.com, using the application name myapplication with the file name mycoolvideo.mov, the URL is:

    http://mycompany.com:1935/myapplication/mp4:mycoolvideo.mov/Manifest

    The Silverlight player, in combination with Wowza Media Server 3, supports the following video and audio formats:


    Video

    • H.264

    Audio

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

    For more details regarding Smooth Streaming, including multi-bitrate streaming, see the User's Guide.


    RTSP/RTP/MPEG-TS (QuickTime, VLC, mobile devices, set top boxes, encoders)


    Wowza Media Server 3 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 MPEG2 Transport Stream protocol (MPEG-TS). This includes players and devices such as QuickTime Player, VideoLAN VLC player, set top boxes and mobile devices. Wowza Server can also accept incoming streams from encoding devices that use these same protocols. Wowza Server supports RTP and MPEG-TS in and out over UDP as well as Multicast. In addition, Wowza Server 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 do not allow UDP transmission.

    An RTSP/RTP URL in Wowza Server has the following form:

    rtsp://[wowza-address]/[application]/[application-instance]/[stream-name]

    where:

    • [wowza-address]: IP address or domain name and port of server running 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 located on the the Wowza Media Server 3 at the address mycompany.com, using the application name myapplication with the stream name mylivestream ,the URL is:

    rtsp://mycompany.com:1935/myapplication/mylivestream

    For more details regarding Real Time Streaming Protocol streaming including support for RTSP/RTP/MPEG-TS encoders, see the User's Guide.



    Wowza Transcoder AddOn


    Wowza Transcoder AddOn is a real time video transcoding and transrating solution. It can decode and re-encode audio and video in multiple formats properly key-frame aligned for multi-bitrate deliver. Here are a few common scenarios:

    Transcoding
    • Take in a non-H.264 AAC media stream and convert it to a properly key frame aligned set of H.264 AAC multi-bitrate media streams.

    Transrate
    • Take in a H.264 AAC media stream and create multiple renditions that are key frame aligned to the source stream for adaptive bitrate delivery.

    Wowza Transcoder supports the following video and audio formats:

    Video (decoding)
    • MPEG2
    • MPEG4 Part 2

    Video (encoding)
    • H.264

    Audio (decoding)
    • MP3
    • MPEG1 Part 1/2
    • Speex
    • G.711 (a-law and mu-law)

    Audio (encoding)
    • AAC


    Wowza nDVR AddOn (beta)


    Wowza nDVR provides the ability to record a live stream with Wowza Media Server 3 while simultaneously allowing users to play, pause, resume and rewind the recorded stream. Custom configuration allows control over the archive strategy and availability of your recorded streams.

    Wowza nDVR is supported on all Wowza Media Server 3 platforms. Setup for client playback of recorded streams is similar to playback of live streams from Wowza Media Server.

    Full information regarding the Wowza nDVR can be found in the Wowza nDVR AddOn User’s Guide.


    Wowza DRM AddOn (beta)


    Wowza DRM provides integration with third party Digital Rights Management (DRM) Key Management Systems (KMS) to add on the fly encryption for both live and video on demand workflows. For the live workflow, encryption per-stream is available with the ability to rotate keys. For the video on demand workflow, encryption per-asset or per-session is available with the ability to rotate keys.


    Installation and Configuration



    Installing Java


    Wowza Media Server 3 is a Java 6 (aka 1.6) and Java 7 (aka 1.7) application. To run, it requires the installation of a Java 6 or greater runtime environment (JRE). To develop server side applications, a Java Development Kit (JDK) version 6, version 7 or later is required. The server also implements a Java Management Extensions (JMX) interface that can be used to manage and monitor the server. One of the more popular JMX consoles is JConsole, which ships with the JDK.

    So what does this all mean? If you are developing server side applications or are going to monitor a local or remote Wowza Server, you need to install Java Development Kit version 6 (aka 1.6), version 7 (aka 1.7) or greater. If you are simply deploying Wowza Server for production use, then you need only install a Java runtime environment version 6 (aka 1.6), Java 7 (aka 1.7) or greater. We recommend installing the most recent version of the Java JDK or JRE for your platform. Select the 64 bit Java installer if running on a 64 bit OS.

    Java can be downloaded from the Oracle website using the following URL: http://java.sun.com/javase/downloads

    To verify that Java 6 (aka 1.6) or Java 7 (aka 1.7) is installed an running properly, open a command prompt and enter the following command:
    Code:
    java -version

    Installing Wowza Media Server 3


    Download the software from the Wowza Media Store.

    Windows:
    Double click WowzaMediaServer-3.0.3.exe and follow the instructions on the screen.

    Note: To run the Wowza Transcoder on Windows Server 64-bit, the following two components are required:

    • .NET Framework 3.5.1 Feature
    • Desktop Experience

    Mac OSX:
    Double click WowzaMediaServer-3.0.3.dmg and follow the instructions on the screen.

    Red Hat Package Manager (RPM):
    Open a command shell and enter the commands:
    Code:
    sudo chmod +x WowzaMediaServer-3.0.3.rpm.bin
sudo ./WowzaMediaServer-3.0.3.rpm.bin
    Debian Package Manager(DEB):
    Open a command shell and enter the commands:
    Code:
    sudo chmod +x WowzaMediaServer-3.0.3.deb.bin
sudo ./WowzaMediaServer-3.0.3.deb.bin
    TAR Installer (TAR):
    Open a command shell and enter the commands:
    Code:
    sudo chmod +x WowzaMediaServer-3.0.3.tar.bin
sudo ./WowzaMediaServer-3.0.3.tar.bin
    Note: For all platforms other than Windows, the Wowza Server server must first be started in standalone mode. The first time the server is started in standalone mode you will be asked to enter the serial number. After the serial number is successfully entered, the server can run as a system service.



    Starting and Stopping the Server (Standalone)


    Windows Start Method1:
    Select:
    Start Menu->Programs->Wowza Media Server [version]->Wowza Startup

    Windows Stop Method1:
    Select:
    Start Menu->Programs->Wowza Media Server [version]->Wowza Shutdown

    Windows Start Method2:
    Open a DOS command prompt and enter the commands:
    Code:
    cd %WMSAPP_HOME%/bin
startup
    Windows Stop Method2:
    Open a DOS command prompt and enter the commands:
    Code:
    cd %WMSAPP_HOME%/bin
shutdown
    Mac OSX Start Method1:
    Double-click:
    /Applications/Wowza Media Server [version]/Wowza Startup

    Mac OSX Stop Method1:
    Double-click:
    /Applications/Wowza Media Server [version]/Wowza Shutdown

    Mac OSX Start Method2:
    Run the Terminal application and enter the commands:
    Code:
    cd /Library/WowzaMediaServer/bin
./startup.sh
    Mac OSX Stop Method2:
    Run the Terminal application and enter the commands:
    Code:
    cd /Library/WowzaMediaServer/bin
./shutdown.sh
    do

    Linux/Unix Start:
    Open a command shell and enter the commands:
    Code:
    cd /usr/local/WowzaMediaServer/bin
./startup.sh
    Linux/Unix Stop:
    Open a command shell and enter the commands:
    Code:
    cd /usr/local/WowzaMediaServer/bin
./shutdown.sh
    Note: While Wowza Media Server is running in standalone mode, the server will not return to the command prompt and will log informational, warning and error messages to the console window. The Wowza Server will log the statement INFO server comment - Wowza Media Server is started! when it is ready to accept streaming connections.


    Starting and Stopping the Server (System Service)


    Windows To Start:
    Select: Start Menu->Settings->Control Panel->Administrative Tools->Services
    Double-click the Wowza Media Server entry, set startup type to Automatic and click the Start button.

    Windows To Stop:
    Select: Start Menu->Settings->Control Panel->Administrative Tools->Services
    Right-click the Wowza Media Server entry and select Stop.

    Mac OSX To Start:
    Run the Terminal application and enter the command:
    Code:
    sudo launchctl load -w /Library/LaunchDaemons/com.wowza.WowzaMediaServer.plist
    Mac OSX To Stop:
    Run the Terminal application and enter the command:
    Code:
    sudo launchctl unload -w /Library/LaunchDaemons/com.wowza.WowzaMediaServer.plist
    Linux To Start:
    Open a command shell and enter the commands:
    Code:
    service WowzaMediaServer start

or

/etc/init.d/WowzaMediaServer start

or

/sbin/service WowzaMediaServer start
    Linux To Stop:
    Open a command shell and enter the commands:
    Code:
    service WowzaMediaServer stop

or

/etc/init.d/WowzaMediaServer stop

or

/sbin/service WowzaMediaServer stop
    To setup the service to start on reboot (Fedora and RedHat):
    Open a command shell and enter the commands:
    Code:
    chkconfig --level 345 WowzaMediaServer on
    Note: Consult your Linux distro documentation if your platform does not support chkconfig


    Port Used for Streaming


    The following ports are used by default by Wowza Media Server 3 for streaming. You will need to open up these ports on your firewall to enable streaming.

    • TCP 1935: RTMP (all variants), RTSP, Smooth and Cupertino Streaming
    • UDP 6970-9999: RTP UDP Streaming
    • TCP 8084-8085: JMX/JConsole Monitoring and Administration
    • TCP 8086: HTTP Administration

    Note: Wowza Server by default binds to TCP port 1935 for all forms of streaming. To configure other ports for streaming, see the next section.


    How to open additional ports for streaming


    To open additional ports for streaming, edit [install-dir]/conf/VHost.xml and add additional port numbers to the HostPortList/HostPort/Port comma separated list of ports. Be sure there are no applications or server software running on your server that also use the ports you wish to open. Below are the common ports used for the Wowza Server streaming protocols:

    • TCP 80: RTMPT, Smooth Streaming, Cupertino Streaming
    • TCP 443: RTMPS
    • TCP 554: RTSP


    Note: Wowza Server cannot share the same TCP ports with other applications.


    How to verify Wowza Media Server is running


    You can verify Wowza Media Server 3 is running by connecting to it using a a web browser. To do this, open a web browser and enter the following URL:

    http://[wowza-ip-address]:1935

    Where [wowza-ip-address] is the ip address of the server running Wowza Media Server. It should return the Wowza Server version number. If not, check to be sure the server is running and TCP port 1935 is open on your router, firewall and/or software firewall (iptables on Linux).


    A Quick Streaming Test


    By default the installer creates a simple Video On Demand (VOD) application which enables you to quickly test to see if the streaming server is running properly and able to serve content.

    Play using Adobe Flash player (RTMP)

    Double-click: [install-dir]/examples/SimpleVideoStreaming/client/simplevideostreaming.html

    enter the information below and click the Play button.
    Code:
    Server: rtmp://[wowza-address]/vod
Stream: mp4:sample.mp4
    The player will then commence playback of the sample video file.



    Installing Examples


    Once you have installed Wowza Media Server 3, you can install the example streaming applications by following these instructions:

    Windows:
    Select: Start Menu->Programs->Wowza Media Server [version]->Examples
    double-click installall.bat

    Mac OSX:
    Open folder: /Library/WowzaMediaServer/example
    double-click installall.command

    Linux:
    Open a command shell and enter the commands:
    Code:
    cd /usr/local/WowzaMediaServer/examples
./installall.sh
    Note: See the README.html at the root of each example folder for detailed information.


    Entering a New License Key


    License keys for all Wowza products, Wowza Media Server 3 and AddOns, are stored in [install-dir]/conf/Server.license.
    • %WMSCONFIG_HOME%\conf\Server.license - Windows
    • /Library/WowzaMediaServer/conf/Server.license - Mac OS X
    • /usr/local/WowzaMediaServer/conf/Server.license - Linux/Unix
    Monthly or Daily Edition subscribers will have a single license key.

    Perpetual Editions users may have more than one key to enable purchased AddOns.

    To change or add a license key, edit this file using a text editor (such as NotePad, TextEdit, TextWrangler or vi) and enter each new license key on a new line. Upon next launch of the standalone server, the new license will be in effect. The licenses are additive, so when adding additional licenses, retain the original license information in the file and add each new license key on its own new line. The order that the keys are listed is not important. The first and last five digits of the license key will be displayed in the console window.

    Example Server.license file for a Perpetual Edition user with a Wowza Media Server 3 license key, two Wowza Transcoder license keys and one Wowza nDVR license key.

    SVRP3-LaGpC-ZrTD9-F4Y3S-a9bR2-h5t3C
    TRN23-Ry6qe-4mT8J-yKj2W-4N5sH-2Td3a
    TRN23-y9Gj2-kneqT-2zjHp-GadzB-N6fwa
    DVRA3-k3r3R-nzxCB-ypjs5-Sk3y9-ahFdF


    Administration



    Logging


    The Wowza Media Server 3 log files are written to the directory [install-dir]/logs. To turn on debug logging (increase the amount of information written to the logs) edit [install-dir]/conf/log4j.properties and change the log level on the first line from INFO to DEBUG. Due to it's increased load on the server, debug logging should not be used in a production environment.


    Server Tuning


    By default the Wowza Media Server 3 is tuned for development. It is very important to tune Wowza Server if it is to be used in a production environment. For up to date tuning instructions, see the following forum thread:

    Article on General Tuning Instructions


    Management and Monitoring (JConsole and JMX)


    Wowza Media Server 3 uses Java Management Extensions (JMX) and JConsole for server management and monitoring. JMX is a protocol used for managing a Java-based server. JConsole is an application that ships with the Sun Java Developement Kit (JDK) that uses the JMX protocol to manage a Java-based server.


    Enable JMX in Wowza Server


    To enable the JMX interface we are going to modify the three highlighted settings below in the Server.xml configuration file. Open [install-dir]/conf/Server.xml and find these lines:

    Code:
    <Root>
    <Server>
        <JMXRemoteConfiguration>
            <Enable>false</Enable>
            <IpAddress>localhost</IpAddress>
             <RMIServerHostName>localhost</RMIServerHostName>
    Change the Enable setting to true and change IpAddress and RMIServerHostName to the IP address of the Wowza Server. If you are running Wowza Server locally leave it as localhost, but if it is a remote server, change it that server's IP address. You can use a domain name.

    Code:
    <Root>
    <Server>
        <JMXRemoteConfiguration>
            <Enable>true</Enable>
            <IpAddress>[server-ip-address]</IpAddress>
            <RMIServerHostName>[server-ip-address]</RMIServerHostName>
    If this server is behind a NAT (Network Address Translation) then the IpAddress setting should be the internal IP address (or localhost) and use RMIServerHostName to set the external IP, as below:

    Code:
    <Root>
    <Server>
        <JMXRemoteConfiguration>
            <Enable>true</Enable>
            <IpAddress>[internal-ip-address]</IpAddress> <!-- set to localhost or internal ip address if behind NAT -->
            <RMIServerHostName>[external-ip-address]</RMIServerHostName> <!-- set to external ip address or domain name if behind NAT -->
    Restart Wowza, then open the access log ([install-dir]/logs/wowzamediaserver_access.log) and check the startup lines. Look for JMX bind attempt followed by a service URL that looks like this:

    Code:
    service:jmx:rmi://localhost:8084/jndi/rmi://localhost:8085/jmxrmi

or:

service:jmx:rmi://[wowza-ip]:8084/jndi/rmi://[wowza-ip]:8085/jmxrmi
    Connecting to Wowza Server Using JConsole

    JConsole is included with the Sun JDK. Install the latest JDK, if you don't already have it, then find JConsole here: [java-install-dir]/bin/JConsole.exe

    If Wowza is installed on your PC or Mac, you can start JConsole from the Wowza Menu group with the JConsole Startup item.

    With JConsole open, click the Remote Process then copy the Service URL into the box and enter user name admin and password admin. Then click Connect button.

    When first connected you will see graphs for memory and cpu usage. Next click on MBean tab, then click the WowzaMediaServerPro node, which you can expand and drill down to all the attributes and operations available through JConsole and the JMX interface.

    Not all Wowza objects are included by default. Take a look at /conf/Server.xml /AdminInterface /ObjectList, and the comment above. The ObjectList defines what is available to monitor in JConsole. The comment above shows all the objects that are available. You can add Client and MediaStream, for examples, if you want to look at that level of detail in JConsole. You must restart Wowza after changes to Server.xml.