Many companies use statistics from the access log to bill customers. If your programming includes live events or 24/7 programming, the events you use to calculate billing might not occur within a billing cycle. To solve this problem, you can enable checkpoint events. Checkpoint events log bytes periodically during an event. The following are available as checkpoint events: connect-continue, play-continue, and publish-continue.

You must specify each Administration API method that may be called over HTTP.

1. Open the RootInstall/conf/fms.ini file.

2. Set the USERS.HTTPCOMMAND_ALLOW parameter to a comma-delimited list of APIs, and restart the server. The default value is ping. For more information, see Users.xml file.

To play back streams and obtain data from shared objects, the Administration Console must make a special debugging connection to the server. By default, the server does not allow this connection.

1. Open the Application.xml file of the virtual host or application you want to configure.

2. Locate the following XML:

   <Debug> 
       <MaxPendingDebugConnections>50</MaxPendingDebugConnections> 
       <AllowDebugDefault>false</AllowDebugDefault> 
   </Debug> 
   

3. Set the AllowDebugDefault element to true.

   Note: Debug connections count against license limits.

4. Save and validate the file.

5. Restart the server.

IPv6 (Internet Protocol version 6) is a new version of Internet Protocol that supports 128-bit addresses. The current version of Internet Protocol, IPv4, supports 32-bit addresses. IPv6 alleviates the address shortage problem on the Internet. A system that only runs IPv6 can't communicate with a system that only runs IPv4.

Enclose numeric IPv6 addresses in URLs in brackets.

Wherever a numeric IPv6 address is used in a client-side script, server-side script, or in the server configuration files, enclose it in brackets:

rtmp://[fd5e:624b:4c18:ffff:0:5efe:10.133.128.108]:1935/streamtest 

You must specify the interface zone index for a link-local address:

rtmp://[fe80::204:23ff:fe14:da1c%4]:1935/streamtest

It’s a good idea to register the RTMP, RTMPS, and RTMPE protocols with a network services database and use a service name (or decimal port number, if necessary) in the server configuration files.

FMS detected IPv6 protocol stack! 
FMS config <NetworkingIPv6 enable=true> 
FMS running in IPv6 protocol stack mode! 
Host: fmsqewin2k3-02 IPv4: 10.133.192.42 IPv6: fe80::204:23ff:fe14:da1c%4 
Listener started ( _defaultRoot__? ) : 19350/v6 
Listener started ( _defaultRoot__? ) : 19350/v4 
Listener started ( _defaultRoot__? ) : 1935/v6 
Listener started ( _defaultRoot__? ) : 1935/v4

You can define properties for the server-side Application object in the server’s Application.xml configuration files. If you define properties in the default Application.xml file, the properties are available for all applications on a virtual host. If you define properties in an Application.xml file in an application folder, the properties are available only for that application.

To define a property, create an XML tag in the JSEngine section of the Application.xml file. The property name corresponds to the tag’s name, and the property value corresponds to the tag’s contents.

For example, the following XML fragment defines the properties user_name and dept_name, with the values jdoe and engineering, respectively:

<Application> 
    <JSEngine> 
            <config> 
                <user_name>jdoe</user_name> 
                <dept_name>engineering</dept_name> 
            </config> 
    </JSEngine> 
</Application>

To access the property in server-side code, use the syntax in either of these examples:

application.config.prop_name  
application.config["prop_name"]

For example, given the previous XML fragment, the following trace() statements are valid:

trace("I am " + application.config.user_name + " and I work in the " + application.config.dept_name + " department."); 
trace("I am " + application.config["user_name"] + " and I work in the " + application.config["dept_name"] + " department.");

The output from either statement would be as follows:

I am jdoe and I work in the engineering department.

You can also use environment variables and symbols you define in the substitution.xml file. For example, assume that the environment variable COMPUTERNAME is equal to jsmith01, and you have defined a symbol named DEPT in the substitution.xml file:

<Root> 
    <Symbols> 
        <DEPT>Engineering</DEPT> 
    </Symbols> 
</Root>

In addition, the following XML appears in the Application.xml file:

<Application> 
    <JSEngine> 
            <config> 
                <compName>${%COMPUTERNAME%}</compName> 
                <dept>${DEPT}</dept> 
            </config> 
    </JSEngine> 
</Application>

In a server-side script, the following trace statements are valid:

trace("My computer's name is: " + application.config.compName); 
trace("My department is: " + application.config.dept);

The output is as follows:

My computer's name is: jsmith01 
My department is: Engineering

The server can detect a client’s bandwidth in the core server code (called native bandwidth detection), or in a server-side script (called script-based bandwidth detection). Native bandwidth detection is faster than script-based because the core server code is written in C and C++. Also, with native bandwidth detection, if a client connects through edge servers, the outermost edge server detects the bandwidth, which results in more accurate data. Native bandwidth detection is enabled and configured by default.

The server detects bandwidth by sending a series of data chunks to the client, each larger than the last. If desired, you can configure the size of the data chunks, the rate at which they’re sent, and the amount of time the server sends data to the client. For more information about detecting bandwidth in an application, see the Developer Guide.

1. Locate the following code in the Application.xml file:

   ... 
       ... 
           <BandwidthDetection enabled="true"> 
               <MaxRate>-1</MaxRate> 
               <DataSize>16384</DataSize> 
               <MaxWait>2</MaxWait> 
           </BandwidthDetection> 
       ... 
   ...

   Note: To disable native bandwidth detection, set the enabled attribute to false and restart the server.

2. Edit the following elements.

   Element	Description
   BandwidthDetection	Set the enabled attribute to "true" or "false" to turn this feature on or off.
   MaxRate	The maximum rate in Kbps that the server sends data to the client. The default value is -1, which sends the data at whatever rate is necessary to measure bandwidth.
   DataSize	The amount of data in bytes that the server sends to the client. To detect the client’s bandwidth, the server attempts to send a series of random blocks of data to the client, each time sending this much more data. For example, x bytes are sent, followed by 2x bytes, followed by 3x bytes, and so on until MaxWait time has elapsed.
   MaxWait	The number of seconds the server sends data to the client. Increasing this number provides a more accurate bandwidth figure, but it also forces the client to wait longer.

3. Save and validate the Application.xml file.

4. Restart the server.