The Server.xml file is located at the root level of the conf directory. Edits made in the Server.xml file affect the entire server unless they are overridden in another configuration file.

To see the element structure and default values in Server.xml, see the Server.xml file installed with Adobe Media Server in the RootInstall/conf/ directory.

Access

Container element.

The elements nested within the Access container configure the Access log settings. The Access logs are located in the RootInstall\logs directory.

Contained elements

ACCP

Container element.

The elements nested within the ACCP container configure the Admin Core Communication Protocol (ACCP). Adobe Media Administration Server and the active cores communicate over ACCP. This protocol is also used for collecting performance metrics and issuing administrative commands to Adobe Media Server cores.

The Adobe Media Administration Console connects to Adobe Media Administration Server, which in turn connects to Adobe Media Server.

Contained elements

ActiveProfile

Specifies the limits enforced by the server on each license key (set in the LicenseInfo element). Select a profile to determine bandwidth, connection, and other licensed limits.

See also

AdaptorName

Enable a registry core to activate a single AMSCore instance dedicated to handling services for Adobe Media Gateway. This AMSCore process comes to life on start-up and allows Adobe Media Gateway to register its services to Adobe Media Server. Enable this registry core only when using Adobe Media Gateway.

<Registry enabled="false"> 
    <!-- Adaptor to run registry core on --> 
    <AdaptorName>_defaultRoot_</AdaptorName> 
</Registry>

Note:

Adobe Media Gateway is discontinued as a part of Adobe Media Server, since AMS 5.0.7. Adobe Media Gateway is not a supported product now.

Admin

Container element.

The elements nested within the Admin container configure the RTMP (Real-Time Messaging Protocol) for the amsadmin process. RTMP is the protocol used for communication between Flash Player and Adobe Media Server.

Contained elements

AdminElem

Specifies the format used to display an element name in an HTTP command. The default value is false, which means the element name is displayed as <_x>; otherwise the element name is displayed as <elem name="x">.

The getActiveVHost() command lists only the active virtual hosts. The getActiveVHostStats()command allows administrators to query the statistics information for all active virtual hosts. To display <elem name="x"> instead of <_x> in the HTTP command, set the AdminElem element to true.

Example

 <AdminElem>true</AdminElem>

See also

AdminServer

Container element.

The elements nested within the AdminServer container configure Adobe Media Administration Server.

Contained elements

Allow

Specifies the administrator connections that are to be accepted. By default, a client can connect to Adobe Media Administration Server from any domain or IP address. This potential security risk can be managed by the Allow element. Permissible administrator connections are detailed as a comma-delimited list of host names, domain names, and full or partial IP addresses. The keyword all can also be used.

Example

 <Allow>x.foo.com, foo.com, 10.60.1.133, 10.60</Allow>

or

 <Allow>all</Allow>

See also

AllowAnyAACProfile

By default, the server does not stream any AAC audio profiles that are not supported by Flash Player 10. To override this behavior, set this value to true.

See also

AllowAnyAVCProfile

By default, the server does not stream any H.264 video profiles that are not supported by Flash Player 10. To override this behavior, set this value to true.

See also

AllowedVideoLag

The number of milliseconds the server holds audio messages in the recording buffer while waiting for a video message. This lag allows the server to sort timestamps before flushing the buffer to disk when video is delayed. The default value is 5.

Application

Container element.

The Enable element nested within the Application container enables the Application log file.

Contained elements

ApplicationGC

Specifies in minutes how often the server checks for and removes unused application instances. The default interval is 5 minutes, which is also the minimum value for this element. An application is considered idle if it has no clients connected for longer than the amount of time specified in MaxAppIdleTime in Application.xml.

AudioAutoBufferReadSize

The server caches F4V/MP4 video, audio, and other data in memory. Caching data allows the server to make fewer disk reads and to perform better. Each data type (audio, video, and other) has its own cache. You can tune the size of each cache, depending on the type of content you are delivering, to achieve better disk performance. For example, if you are delivering audio-only content, increase the AudioAutoBufferReadSize buffer, and decrease the VideoAutoBufferReadSize buffer.

The minimum size is 1024 bytes. The default value is 51200 bytes.

See also

AuthEvent

Container element. The Enable element nested within the AuthEvent container enables the logging of events from the Authorization plug-in.

Contained elements

AuthMessage

Container element. The Enable element nested within the AuthMessage container enables the logging of messages from the Authorization plug-in.

Contained elements

AutoCloseIdleClients

Container element. Determines whether or not to automatically close idle clients.

Set the enable attribute to true to close idle clients. If the enable attribute is omitted or set to false, the feature is disabled. The default value is false.

A client is active when it is sending or receiving data. Use AutoCloseIdleClients to specify how often the server should check for idle clients. When a client has been idle longer than the maximum idle time (60 seconds by default), the server sends a status message to the NetConnection object (the client). The server closes the client connection to the server and writes a message to the access log. The server also writes a message such as “Client x has been idle for y seconds” in the core and event logs.

To configure the closing of idle connections, you must enable the feature in the Server.xml file. Once you enable the feature in the Server.xml file, you can disable the feature for individual virtual hosts in the Vhost.xml files or for individual applications in Application.xml. The values defined in the Server.xml configuration file apply to all clients connected to the server, unless the values are defined in the Vhost.xml file. The Vhost.xml values override the Server.xml values. (Subsequently, the values defined in the Vhost.xml configuration file apply to all clients connected to the virtual host, unless values are defined in the Application.xml file. The Application.xml values override the Vhost.xml values.)

Example

 <AutoCloseIdleClients enable="false"> 
     <CheckInterval>60</CheckInterval> 
     <MaxIdleTime>600</MaxIdleTime> 
 </AutoCloseIdleClients>

Contained elements

Cache

Container element. Contains elements that configure the cache setting for SWF verification.

See also

CheckInterval

Specifies the interval, in seconds, at which the server checks for active client connections. The minimum and default value is 60 seconds.

A client is disconnected the first time the server checks for idle connections if the client has exceeded the MaxIdleTime value. A shorter interval results in more reliable disconnection times, but can also result in decreased server performance.

Example

 <CheckInterval>60</CheckInterval>

See also

Checkpoints

Enables logging checkpoint events. Checkpoint events log bytes periodically from the start to the end of an event. The following are available as checkpoint events: connect-continue, play-continue, and publish-continue.

This element contains the enable attribute which you can set to true or false. Set the enable attribute to true to turn on checkpoint events in logs. The default value is false.

You must enable checkpoint events at the server level in the Server.xml file. You can disable checkpoints at the vhost and application level in the Vhost.xml and Application.xml files. You can also override the logging interval at the vhost and application levels.

Contained elements

ConnectionTimeout

Flash Media Server 4.5

[adoberuntime]Flash Media Server 4.5[/adoberuntime]

The /RTMP/ConnectionTimeout element and /HTTP/ConnectionTimeout element specify how long to wait before timing out an outgoing connection, in milliseconds. The default is -1 which uses the OS timeout to block outgoing connections.

<ConnectionTimeout>-1</ConnectionTimeout>

Connector

Container element.

The elements nested within the Connector container configure the connector subsystem. Adobe Media Server provides connectors that allow application scripts to connect to other Adobe Media Servers or HTTP servers.

Contained elements

Content

Enables operations in the current File plug‑in on content (streams or SWF files). The value of true enables the operation on the specified content type and false disables it.

This element contains the type attribute, which you can set to the following values:

  • Streams. Enables stream file operations. Enabled by default.

  • SWF. Enables operations on SWF files. Disabled by default. Enable if you plan to use the File plug‑in to retrieve SWF files for verification by the server.

This element is nested within the FilePlugin tag.

Example

<Content type="Streams">true</Content> 
<Content type="SWF">false</Content>

See also

Core

Container element.

The elements nested within the Core container configure the RTMP protocol for the AMSCore.exe process.

Contained elements

CoreExitDelay

Specifies how much wait time, in seconds, an idle core is given to exit on its own before it is removed from the server. The default wait time is 20 seconds.

Example

 <CoreExitDelay>60</CoreExitDelay>

See also

CoreGC

Specifies how often, in seconds, to check for and remove idle or unused cores. The default is 300 seconds.

Example

 <CoreGC>300</CoreGC>

See also

CoreTimeout

Specifies the timeout value, in seconds, for detecting unresponsive cores. The default timeout is 30 seconds. A value of 0 disables the timeout check.

Example

 <CoreTimeout>30</CoreTimeout>

See also

CPUMonitor

Specifies, in seconds, how often the server monitors CPU usage. The default interval is 1 second. The value cannot be set to less than 1 second.

Example

 <CPUMonitor>1</CPUMonitor>

See also

CrossDomainPath

Specifies an absolute path on the server to a cross-domain file. This element lets you specify a list of domains from which a client can access the server. The default value is *, which allows clients from all domains to access the server.

This element is nested within both the Server element and the AdminServer element. Use it for both edge and administration server requests.

Example

 <CrossDomainPath>C:/Security/config/files/ams/crossdomain.xml</CrossDomainPath>

Deny

Specifies administrator connections that should be ignored. The connections are specified as a comma-delimited list of host names, domain names, and full or partial IP addresses, or the keyword all.

Example

 <Deny>x.foo.com, foo.com, 10.60.1.133, 10.60</Deny>

or

 <Deny>all</Deny>

See also

Diagnostic

Container element.

The Enable element nested within the Diagnostic section enables the diagnostic log file.

Contained elements

DiffServ

Flash Media Server 3.5.2

[adoberuntime]Flash Media Server 3.5.2[/adoberuntime]

Use this element with the DiffServMask element to specify the DiffServ field for all sockets that connect to the RTMP listener (these include tunneling and HTTP proxy sockets). There is little use for this unless you have set up a DSCP domain. Also, some values may lead to errors, depending on your platform and your router configuration. For example, to set priority class 4, you might set DiffServ to 128 (top 3 bits set to 4) and set DiffServMask to 224 (top 3 bits on).

To verify that bits are set on a socket, call the Administration API getNetStreamStats() method. Each stream has a diffserv_bits field whose value is updated when you successfully set bits on a socket.

DiffServMask

Flash Media Server 3.5.2

[adoberuntime]Flash Media Server 3.5.2[/adoberuntime]

Use this element with the DiffServ element to specify the DiffServ field for all sockets that connect to the RTMP listener (these include tunneling and HTTP proxy sockets). There is little use for this unless you have set up a DSCP domain. Also, some values may lead to errors, depending on your platform and your router configuration. For example, to set priority class 4, you might set DiffServ to 128 (top 3 bits set to 4) and set DiffServMask to 224 (top 3 bits on).

Directory

Located in the Httpd container.

The directory containing the web server. The default value is Apache2.2.

DirLevelSWFScan

Specifies the number of levels of subfolders within a parent folder to scan for SWF files. The parent folder is specified in the SWFFolder element.

Specifying a positive value scans that number of subfolders. Specifying zero scans the parent folder and no subfolders. Specifying a negative value scans all subfolders. The default value is 1, which means that the server scans only one subfolder level.

See also

ECCP

Container element.

The elements nested within the ECCP container configure ECCP (Edge Server-Core Server Communication Protocol). Adobe Media Server edge processes and Adobe Media Server core processes use ECCP to migrate socket connections and to proxy connections that have not been migrated.

Contained elements

Edge

Container element.

The elements nested within the Edge container configure the RTMP protocol for the amsedge process.

Contained elements

Edge (ResourceLimits)

Container element.

The elements nested within the Edge container configure resources for the amsedge process.

Contained elements

EdgeCore

Container element.

The elements nested within the EdgeCore container control the IPC (interprocess communication) message queue used by edge and core processes to communicate with each other.

Contained elements

Enable

Server.xml uses Enable elements in the Logging container to enable or disable the Access, Diagnostic, Application, AuthEvent, AuthMessage,and FileIO logs. A value of true enables the logging process; false disables the logging process. The default value is true.

Example

 <Access> 
     <enable>true</Enable> 
 </Access>

See also

EnableAggMsgs (playback)

Located in the Playback container.

Aggregating messages increases server performance. The default value is true. Do not change this value if you want to achieve the highest possible server performance.

Note:

This setting applies to playback of MP4/F4V files only.

EnableAggMsgs (raw)

Specifies whether the RAW adaptor generates aggregate messages (true) or not (false). Aggregating messages improves server performance.

The default value is true.

Example

<EnableAggMsgs>true</EnableAggMsgs>

See also

EnableSystemLogging

Enables logging of high severity entries to the system log (true) or not (false).

The default value is true.

Example

<EnableSystemLogging>true</EnableSystemLogging>

FileCheckInterval

Located in the FLVCache container.

Specifies, in seconds, how often the server reloads the video segment in the cache when there is a file change. The default value is 120 seconds. The minimum value is 1 second. There is no maximum value. A very large number means the server does not refresh the cache even when there is a file change.

Example

 <FileCheckInterval>120</FileCheckInterval>

FileIO

Container element.

The Enable element nested within the FileIO container enables logging from the File plug‑in.

Contained elements

FilePlugin

Container element.

This element contains elements to configure file operations that are handled by the File plug‑in. Setting the enabled attribute to false disables the File plug‑in.

Contained elements

FLVCache

Container element.

Contains elements that control the size and features of the recorded media cache.

Contained elements

FLVCachePurge

Located in the ResourceLimits container.

Specifies how often, in minutes, to remove unused files from the cache. The default value is 60 minutes. The minimum value is 1 minute. If you specify a value of less than 1minute, the default value of 60 is used.

FLVCacheSize

Located in the ResourceLimits container.

Specifies the maximum size of the recorded media cache. The recorded media cache size is specified as a percentage of the total available RAM on the system. The default setting for the cache size is 10 (10%). The maximum setting is 100 (100%), in which case virtual memory will also be used.

Use this setting to configure the cache for optimal memory use. If you are receiving “cache full” events in the core log file or want to increase the chance that streams will find the information needed in the cache, increase the size of the cache. To minimize the amount of memory used in the server process, decrease the size of the cache.

Example

 <FLVCacheSize>10</FLVCacheSize>

FreeMemRatio

Located in the MessageCache, SmallMemPool, LargeMemPool, and SegmentsPool containers.

Specifies the maximum percentage of total memory that the total pool size may occupy. The range of this setting is from 0 (0%) to 1 (100%). The default setting is 0.5 (50%).

Example

 <FreeMemRatio>0.5</FreeMemRatio>

FreeRatio

Located in the MessageCache, SmallMemPool, LargeMemPool, and SegmentsPool containers.

Specifies the percentage of the message cache to be consumed by the free list on a per‑thread basis. The range of this setting is from 0 (0%) to 1 (100%). The default setting is 0.125 (12.5%).

When more free memory is available to a thread than the specified ratio, the freed memory returns to the global pool.

Example

 <FreeRatio>0.125</FreeRatio>

GCInterval

Located in the HandleCache container.

Specifies in minutes how often to remove idle handles. The default is 60 minutes.

Example

 <GCInterval>60</GCInterval>

GID

Located in the Process containers.

Specifies the group ID of the process. If you do not specify a UID or GID, the server or Administration Server runs as root. This element is applicable to Adobe Media Server running on Linux systems only.

See also

GlobalQueue

Container element.

The elements nested within the GlobalQueue container control the IPC message queue used by all processes to communicate with each other.

Contained elements

GlobalRatio

Located in the MessageCache, SmallMemPool, LargeMemPool, and SegmentsPool containers.

Specifies the percentage of the message cache to be consumed by the free list on a global basis. When more free memory is available to a thread than the specified ratio, the freed memory returns to the operating system.

The range of this setting is from 0 (0%) to 1 (100%). The default setting is 0.4 (40%).

Example

 <GlobalRatio>0.4</GlobalRatio>

HandleCache

Container element.

Contains elements that configure how to cache handles used for HTTP requests. This section is used for connections to Flash Remoting.

Contained elements

HeapSize

Specifies the maximum size, in kilobytes, of the shared memory heap used for an IPC (interprocess communication) message queue. The default value for this element varies according to its container.

Container

Default Value

Description

EdgeCore

1024

If the maximum size of this element is not specified, the value is 100 KB.

GlobalQueue

2048

Services

2048

Example

 <EdgeCore>  
     <HeapSize>1024</HeapSize>  
 </EdgeCore>

See also

HostPort

Specifies the IP address and port number that Adobe Media Administration Server binds to. The default is to bind to any available IP on port 1111. Only one port number may be specified in this element.

The Administration Service is separate from Adobe Media Server. When administrators connect to the server with the Administration Console, they are connecting to Adobe Media Administration Server, which in turn connects to Adobe Media Server.

Example

 <HostPort>ip:port</HostPort>

See also

HTTP

Container element.

The elements nested within the HTTP container configure the HTTP connector used to connect to Flash Remoting.

The following reference table gives the default values for all thread configurations.

Default Value

Description

0

Allocates the default number of threads.

>0

Allocates the exact number of threads specified.

-1

Allocates 1xN threads, where N is the number of processors available in the computer.

-2

Allocates 2xN threads, where N is the number of processors available in the computer. For example, suppose you have a quad-core computer, where applications see 4 local processors. If you specify a value of -2, the HTTP connector can use up to 8 threads.

Contained elements

Httpd

Specifies how the built-in webserver is stopped and started. By default the enabled attribute is set to "${SERVER.HTTPD_ENABLED}". By default, the SERVER.HTTPD_ENABLED variable is set to true in the ams.ini file. When enabled is set to true, Adobe Media Server starts and stops the web server automatically. Adobe Media Server uses the settings in the Directory, Program, Options, and Service elements to execute the following command lines:

$Directory/$Program -d $Directory $Options -k start 
$Directory/$Program -d $Directory $Options -k stop

Note:

The value of $Directory can be absolute or relative to $AMSROOT.

On Windows only, Service specifies the name used to install the webserver as an NT service. If a value for Service is present, -n $Service is appended to both commands. Linux ignores this section of the command.

Contained elements

IdleTime

Located in the HandleCache container.

Specifies the amount of time to wait before releasing cached handles. If no HTTP requests have been made to the host for the length of time specified, some cached handles are cleared. The default wait time is 10 minutes.

Example

 <IdleTime>10</IdleTime

IpcHostPort

The interface and port the server listens on internally for connections from the amscore process to the Administration Server. The default value is localhost:11110.

IPCQueues

Container element.

The elements nested within the IPCQueues container configure the IPC queues. Adobe Media Server uses IPC queues to send messages from one core to another or from one process to another, such as master to core, or core to edge.

Unlike protocols, queues are used for short or one-time messages that may have more than one target.

Contained elements

LargeMemPool

Container element.

The elements nested within the LargeMemPool container configure the large memory pool, which caches large chunks of memory within the server to increase the performance of large allocations.

Contained elements

LicenseInfo

The license number. By default, this value is a parameter in the ams.ini file:

<LicenseInfo>${SERVER.LICENSEINFO}</LicenseInfo>

Note:

Serial numbers that are added manually (that is, added by editing those files directly) to either ams.ini or the LicenseInfo tag of Server.xml file cannot be removed using the Administration Console. Only serial numbers that are added using the Administration Console can be deleted using the Administration Console.

Example

 <LicenseInfo>${SERVER.LICENSEINFO}</LicenseInfo>

LicenseInfoEx

Contains license keys added using the Administration Console.

Localhost

Specifies the IP loopback address.

The server must reference itself locally. The IP loopback address is usually the default localhost address. With more than one network interface, localhost can map to an erroneous interface. The server uses the default loopback address as the local loopback.

LockoutLimit

The maximum number of login failures before a user is prevented from logging into the admin server. If this value is reached, the admin server must be restarted before that user can log in again.

The default value is 300.

Example

<LockoutLimit>300</LockoutLimit>

See also

LogInLimits

Container element.

Configures the number of failed admin login attempts that are allowed, and the amount of recovery time required before the admin can attempt to log in again.

Contained Elements

See also

LogInterval

Specifies how often to log a checkpoint, in seconds. This value should be larger than the value for CheckInterval. If the value is smaller, the server logs a checkpoint every check interval. The default value is 3600 seconds (60 minutes).

See also

Logging

Container element.

The elements nested within the Logging container configure general logging properties for the server. Set the configuration properties of the individual log files in the Logger.xml file.

Log files are written in English. Field names in the log file are in English. Some content within the log file, however, may be in another language, depending on the filename and the operating system. For example, in the access.log file, the columns x-sname and x-suri-stem show the name of the stream. If the name of the recorded stream is in a language other than English, the name is written in the log file in that language, even if the server is running on an English-language operating system.

Contained elements

Mask

A three-digit octal value used by the Linux umask (user permissions mask) command to set a file creation mask. The user must enter the mask in a three-digit octal format.

The default setting for this element is 017 in octal.

This element is applicable to Adobe Media Server running on Linux systems only. This element controls who has read/write access to shared object and stream files on the server. All Adobe Media Server object files, such as stream files or shared object files, are created on the server side with permission 0666. This key is used by umask to set the file creation mask. By default, the creation mask is set to 017 in octal. Therefore, all Adobe Media Server object files are created with permission 0666 & ~017 = 0660 = rw-rw----.

The owner and the users who belong to the same group as the owner get read/write permission to the files. If the mask is set to 022, the file created is assigned permission 0666 & ~022 = 0644 = rw-r--r--.

Master

Container element.

The elements nested within the Master container configure the resource limits for the master server.

Contained elements

MaxAge

Located in the MessageCache, SmallMemPool, LargeMemPool, and SegmentsPool containers.

This element defines the maximum reuse count before the cache unit is freed. The default count is 1,000,000.

Example

 <MaxAge>1000000</MaxAge>

MaxAggMsgSize (playback)

The maximum size of an aggregate message, in kilobytes. The default value is 64.

Note:

This setting applies to playback of MP4/F4V files only.

See also

MaxAggMsgSize (raw)

The maximum size of an aggregate message, in bytes. You can use any positive integer.

The default value is 65536.

Example

<MaxAggMsgSize>65536</MaxAggMsgSize>

See also

MaxAudioSampleDescriptions

Located in the Recording container.

Each change in codec for a content type has a sample description. For example, two different audio codecs each have their own sample description. The server allocates space for sample descriptions when it creates a file. If the codec type changes more than the number of available descriptions, the server stops recording. However, adding too many descriptions takes up unnecessary space for every file that the server records.

The default value is 20.

Note:

This setting applies to recording MP4/F4V files only.

MaxCacheSize

Located in the MessageCache, SmallMemPool, LargeMemPool, and SegmentsPool containers.

This element defines the maximum size of the cache in megabytes. The default is 100 MB.

Example

 <MaxCacheSize>100</MaxCacheSize>

MaxCacheUnits

Located in the MessageCache, SmallMemPool, LargeMemPool, and SegmentsPool containers.

This element defines the maximum number of free units in the cache. Keep in mind that the number of free units may be less than maximum if the value of the MaxCacheSize limit is reached.

The default is 4096 units.

Example

 <MaxCacheUnits>4096</MaxCacheUnits>

MaxConnectionQueueSize

Located in the HTTP container.

Specifies the maximum number of connection requests that can be pending. Connection requests are rejected if this limit is exceeded.

The default number of pending requests is 1000. To use the default, specify -1.

Example

 <MaxConnectionQueueSize>-1</MaxConnectionQueueSize>

MaxConnectionRate

Located in the RTMP (Protocol) and Edge containers.

Specifies the maximum number of incoming connections per second that the server’s socket listener accepts. You can set a fractional maximum connection rate, such as 12.5. A value of 0 or -1 disables the feature.

This is a global setting for all socket listeners. If the element is set to 10 connections per second, each listener has a limit of 10 connections per second. If there are three listeners and the MaxConnectionRate is set to 10, the server imposes a maximum total combined rate of 30 connections per second. The socket listeners are configured in the Adaptor.xml configuration file using the HostPort element under the HostPortList container element.

Connections requested at a rate above the value specified in this element remain in the TCP/IP socket queue and are silently discarded by the operating system whenever the queue becomes too long.

Example

 <MaxConnectionRate>100</MaxConnectionRate>

MaxConnectionThreads

Located in the HTTP and RTMP (Connector)containers.

Specifies the maximum number of threads used to process connection requests. For HTTP, the default number is 10. To use the default, specify 0. For RTMP, the default number is 5. To use the default, specify 0. If the server is taking a long time to process connections, raise the value of HTTP/MaxConnectionThreads to 20.

MaxDataSampleDescriptions

Located in the Recording container.

Each change in codec for a content type has a sample description. For example, two different data encoding formats each have their own sample description. The server allocates space for sample descriptions when it creates a file. If the encoding format type changes more than the number of available descriptions, the server stops recording. However, adding too many descriptions takes up unnecessary space for every file that the server records. The default value is 10.

Note:

This setting applies to recording MP4/F4V files only.

MaxELSTEntries

Located in the Recording container.

The maximum number of ELST entries in a recording. The server uses ELST entries when there are gaps in content. Gaps occur during an append to the file or when video, audio, or data content ends while other such content continues. If more gaps or appends occur than the value specified in the MaxELSTEntries tag, recording ends. However, setting this value too high takes up unnecessary space in each recorded file. The default value is 100.

Note:

This setting applies to recording MP4/F4V files only.

MaxEventQueueThreads

Located in the Edge (ResourceLimits) container.

The maximum number of threads per scheduler queue. The default value is -2.

MaxFailures

The maximum number of login attempts a user can have before having to wait to be allowed again. The wait time is defined by the RecoveryTime element.

The default value is 3. If the number of failed login attempts equals the value of LockoutLimit, the admin server must be restarted before that user can attempt to log in again.

Example

<MaxFailures>3</MaxFailures>

See also

MaxFlushSize

Located in the RecBuffer container.

The maximum number of kilobytes to accumulate before flushing the recording buffer. The default value is 256. The minimum value is 32.

MaxFlushTime

Located in the RecBuffer container.

The maximum number of seconds to wait before flushing the recording buffer. The default value is 5. The minimum value is 1.

MaxIdleTime

Located in the AutoCloseIdleClients container.

Specifies the maximum idle time allowed, in seconds, before a client is disconnected. The default value is 3600 seconds (60 minutes). If you set a value of 60 or less, the server uses 1200 seconds (20 minutes).

A low value may cause unneeded disconnections. When you configure this element, consider the type of applications running on the server. For example, if you have an application with which users watch short video clips, a user might leave the window to idle out.

MaxInitDelay

The maximum number of seconds that is used to process SWF files. The default value is 5 seconds. This element is used in the verification of SWF files.

Example

<MaxInitDelay>5</MaxInitDelay>

See also

MaxIOThreads

Located in the RTMP (Connector), Edge, Core, Admin, ECCP, and ACCP containers.

Specifies the maximum number of threads that can be created for I/O processing.

Use the following information to configure all I/O and connection threads processing:

  • A value of 0 allocates the default number of threads (10).

  • A value greater than 0 allocates the exact number of threads specified.

  • A value less than 0 ties the number of connection threads to the number (N) of processors, as follows:

    • -1 means 1 x N threads.

    • -2 means 2 x N threads, and so on.

Adobe Media Server can receive connections through various protocols. The default value for this element varies according to which container protocol it is nested within.

Container

Default Value

Description

ACCP

10

Use 0 for the default value.

Admin

10

Use 0 for the default value.

Core

10

Use 0 for the default value.

ECCP

10

Use 0 for the default value.

Edge

10

Use 0 for the default value.

RTMP

32

Use -1 for the default value.

Example

 <RTMP> 
     <MaxIOThreads>32</MaxIOThreads> 
 </RTMP>

MaxKeyframeCacheSize

Located in the FLVCache container.

Specifies the maximum number of keyframes in the cache for each recorded media file. The default value is 2000 keyframes.

When enhanced seeking is enabled, the server generates keyframes that are saved in the cache. (For more information, see EnhancedSeek in the Application.xml file.) If you lower MaxKeyframeCacheSize, the cache uses less memory. If an application uses many large recorded media files, you may want to lower this number.

Example

 <MaxKeyframeCacheSize>0</MaxKeyframeCacheSize>

MaxNumberOfRequests

Specifies the maximum number of pending requests to the File plug‑in. The default value is 0, which allows unlimited requests.

If the plug‑in does not respond to a request from the server, the number of pending requests increases up to the value of MaxNumberofRequests. Once MaxNumberofRequests is reached, subsequent requests are rejected.

By default, Adobe Media Server does not count the number of requests made to the File plug‑in or responses returned from the File plug‑in. If necessary, you can use this value to identify problems with the File plug‑in. Adobe generally recommends keeping the default value of 0.

MaxQueueSize

Located in the GlobalQueue, EdgeCore, Services containers.

Specifies the maximum number of pending IPC messages in the queue. When messages are sent to a process that is not running, the message can be put in a pending queue for the process. When the process starts again, it picks up the messages. Use the MaxQueueSize element to limit the number of messages left in the pending queue. Limiting messages saves shared memory if the process never starts. The value is specified in kilobytes. The default size is 100 KB.

MaxSampleSize

The maximum allowable size of a sample in an F4V/MP4 file, in kilobytes. You can increase this value up to 4GB if a file has larger samples. The default value is 16777216 (16 MB).

See also

MaxSize (FLVCache)

Located in the FLVCache container.

Specifies the maximum size of the recorded media cache in megabytes. The default value is 500 MB. This value shares memory with the running process and has a limit of 2 GB in Windows and 3 GB in Linux on 32-bit configurations. On 64-bit configurations, the file memory available to the process is only limited by the amount of RAM.

The size of the cache limits the number of unique streams the server can publish. To increase the probability that a requested stream will be located in the recorded media cache, increase the value of MaxSize. To decrease the amount of memory the server process uses, decrease the value of MaxSize. Note that increasing the file cache size to too large of a size can cause substantially deteriorated system performance.

MaxSize (HandleCache)

Located in the HandleCache container.

Specifies the maximum number of handles to cache. The minimum value is 0, which means that no handles are cached. There is no maximum value; it can be the maximum number of handles that the operating system can support. The default value is 100 handles.

Example

 <MaxSize>100</MaxSize>

MaxSize (RecBuffer)

Located in the RecBuffer container.

Specifies the maximum size to which the buffer can grow before messages are committed to file. The default value is 200 and the minimum value is 0. The higher the value, the longer the data will be held in the buffer before written to disk.

When you add DVR functionality to an application, the size of the recording buffer affects the play-while-record experience. A shorter buffer decreases latency between real-time and playback, but hurts performance.

Example

 <MaxSize>5120</MaxSize>

MaxTimestampSkew

Located in the RecBuffer container.

Specifies the maximum gap in milliseconds between two adjacent messages when comparing the message timestamps with the real time. The server logs a warning when the timestamps between two adjacent messages are bigger than the difference in real time plus the value set here for MaxTimestampSkew. This element is disabled by default. To enable the element, set the value to a positive number.

Example

 <MaxTimestampSkew>2</MaxTimestampSkew>

MaxTracks

Located in the Playback container.

The maximum number of tracks allowed in a file. While only one video, audio, and data track may be played, files with up to this many tracks can be parsed. More than this amount is a file error. The default value is 64.

MaxUnitSize

Located in the MessageCache, SmallMemPool, LargeMemPool, and SegmentsPool containers.

Specifies the maximum size, in kilobytes, of a memory chunk allowed in a memory pool. The default size is 16 KB.

Adobe Media Server has several memory pools (distinct from the recorded media cache) that hold memory in chunks. This setting ensures that chunks larger than MaxUnitSize are released to system memory instead of being held in the pool so that large memory chunks are available.

For example, if this tag is under the MessageCache tag, the server doesn’t cache any messages greater than MaxUnitSize.

Example

 <MessageCache> 
     <MaxUnitSize>16</MaxUnitSize> 
 </MessageCache>

MaxUrlLength

Defines the maximum allowed RTMP and SWF file URL lengths, in bytes. Most modern browsers support up to 64KB URLs. The default value is 32KB. The maximum allowable value is 1000KB.

Use this element to restrict the URL lengths of incoming requests. To restrict the length of outbound NetConnection URLs from SSAS, use the MaxUrlLength element in the Application.xml file.

Example

<MaxUrlLength>65536</MaxUrlLength>

See also

MaxVideoSampleDescriptions

Located in the Recording container.

Each change in codec for a content type has a sample description. For example, two different video codecs each have their own sample description. The server allocates space for sample descriptions when it creates a file. If the codec type changes more than the number of available descriptions, the server stops recording. However, adding too many descriptions takes up unnecessary space for every file that the records. The default value is 10.

Note:

This setting applies to recording MP4/F4V files only.

MessageCache

Container element.

The elements nested within the MessageCache container control how the message cache holds onto messages used by the system running Adobe Media Server and keeps them in memory for reuse instead of returning them and requesting them from the operating system.

Messages are the essential communication units of Adobe Media Server. Recycling them improves the server’s performance.

Contained elements

MinConnectionThreads

Located in the HTTP and RTMP (Connector) containers.

Specifies the minimum number of threads in the pool for I/O operations. The default is 1 multiplied by the number of processors. To use the default, specify the value 0.

Example

 <MinConnectionThreads>0</MinConnectionThreads>

MinEventQueueThreads

Located in the Edge (ResourceLimits) container.

The minimum number of threads per scheduler queue. The default value is 2.

MinGoodVersion

Located in the SWFVerification container.

Specifies the minimum accepted version of SWF verification feature that the server allows. The default value of 0 accepts current and all future versions.

Example

 <MinGoodVersion>0</MinGoodVersion>

MinIOThreads

Located in the RTMP (Connector), Edge, Core, Admin, ECCP, and ACCP containers.

The element specifies the minimum number of threads that can be created for I/O operations.

Adobe Media Server can receive connections through various protocols. The default value for this element varies according to which container protocol it is nested within.

Container

Default Value

Description

ACCP

2X number of processors

Use 0 for the default value.

Admin

2X number of processors

Use 0 for the default value.

Core

2X number of processors

Use 0 for the default value.

ECCP

2X number of processors

Use 0 for the default value.

Edge

2X number of processors

Use 0 for the default value.

RTMP

2X number of processors

Use -1 for the default value.

Example

 <ECCP>  
     <MinIOThreads>0</MinIOThreads>  
 </ECCP>

Mp4

Container element.

The Mp4 elements configure how the server plays and records MP4, F4V, MOV, and other MP4 file types.

Contained elements

MsgPoolGC

Specifies how often the server checks for content in and removes content from the global message pool.

The default interval for checking and removing content is 60 seconds.

NetworkingIPv6

Enables or disables Internet Protocol version 6 (IPv6). This is an empty tag.

The operating system network stack should be configured to support IPv6, if desired. Adobe Media Server automatically detects the operating system configuration; this element can force Adobe Media Server to use IPv4 even if IPv6 is available.

Example

 <NetworkingIPv6 enable="false" />

NumCRThreads

Located in the RTMP (Connector) container.

Specifies the number of completion routine threads in Windows 32-bit systems for edge server I/O processing.

Example

 <NumCRThreads>0</NumCRThreads>

NumSchedQueues

Located in the Edge (ResourceLimits) container.

The number of scheduler queues. The default value is 1.

Options

Located in the Httpd container.

Specifies additional switches for the command-line argument that starts and stops the web server.

Order

Located in the AdminServer container.

Specifies the order in which to evaluate the Allow and Deny elements.

Example

To process the request if not in <Deny> or in <Allow>, set:

 <Order>Deny,Allow</Order>

To process the request if in <Allow> and not in <Deny>, set:

 <Order>Allow, Deny</Order>

OtherAutoBufferReadSize

Located in the Playback container.

The server caches F4V/MP4 video, audio, and other data in memory. Caching data allows the server to make fewer disk reads and to perform better. Each data type (audio, video, and other) has its own cache. You can tune the size of each cache, depending on the type of content you are delivering, to achieve better disk performance.

The minimum size is 1024 bytes. The default value is 1024 bytes.

Playback

Container element.

The Playback elements configure how the server plays back MP4, F4V, MOV, and other MP4 file types.

Contained elements

Plugins

Container element.

The elements nested within the Plugins element configure plug‑ins.

Contained elements

Process

Container element.

There are 2 Process elements, one for Adobe Media Server and one for Adobe Media Administration Server. The elements nested within the Process element contain the UID and GID elements for all server processes. The elements are applicable to servers running on Linux systems only. For security reasons, on Linux, all the server processes switch from root to the UID and GID. If you do not specify a value for UID and GID, the server runs as root.

Contained elements

ProcVMSizeMonitorInterval

The monitoring interval for process virtual memory use, in seconds. The default value is 60.

ProcVMSizeNominal

The log notification threshold for reverting to a nominal process virtual memory use, in megabytes, after the ProcVMSizeWarn threshold has been triggered. The default value is 1600.

ProcVMSizeWarn

The log warning threshold for high process virtual memory use, in megabytes. The default value is 1800.

Program

Located in the Httpd container.

The location of the executable file for the web server. The default value is bin/httpd.

Protocol

Container element.

Adobe Media Server receives connections through various protocols. The elements in this container configure those protocols and how the connection requests are received.

To set the values of all I/O and connection threads processing, follow these guidelines:

  • A value of 0 allocates the default number of threads (10).

  • A value greater than 0 allocates the exact number of threads specified.

  • A value less than 0 ties the number of connection threads to the number (N) of processors:

    • -1 means 1 x N threads

    • -2 means 2 x N threads, etc.

Contained elements

PublicIP

Specifies that if the system has more than two network ports, use this element to create a public IP address.

Raw

Contains elements that control the RAW adaptor.

Adobe Media Server supports a RAW (Record and Watch) file format that records media into configurable chunks that can be streamed to any version of Flash Player. The RAW file format enables you to serve long-length, multi-bitrate DVR streams without running into performance issues. Use the RAW file format to record and play back all streams that Adobe Media Server supports, including H.264 video, data-only, audio-only, and so on.The RAW file format is a server feature; any version of Flash Player can publish or play a RAW stream. However, multi-bitrate stream support (also called dynamic streaming) requires Flash Player 10 and higher.

Container element.

Note:

The RAW file format is internal to Adobe Media Server. At this time, you cannot edit these files with third-party tools or convert the files to FLV format or MP4 format.

Availability

Flash Media Server 4

Contained elements

See also

ReadBufferSize

The size of the largest I/O read buffers that the server uses, in kilobytes. Larger buffers provide better performance for some use cases. However, larger buffers use more memory. The default value is 4096.

RecBuffer

Container element.

Contains elements that configure the buffer for recording.

When you add DVR functionality to an application, the size of the recording buffer affects the play-while-record experience. A shorter buffer decreases latency between real-time and playback, but hurts performance.

Contained elements

Recording

Container element.

The Recording elements configure how the server records F4V/MP4 file types.

Contained elements

RecordsNumber

The number of records in the log queue. If an attempt to open the log fails and the number of records in the queue is greater than or equal to this number, the core process is shut down.The default value of -1 allows an unlimited number of records.

RecoveryTime

The time to wait, in seconds, before allowing another login attempt after a user has reached the value of MaxFailures.

The default value is 30 seconds.

If the number of failed login attempts equals the value of LockoutLimit, the admin server must be restarted before that user can attempt to log in again.

Example

<RecoveryTime>30</RecoveryTime>

See also

Registry

Flash Media Server 4.5

[adoberuntime]Flash Media Server 4.5[/adoberuntime]

Enable a registry core to activate a single AMSCore instance dedicated to handling services for Adobe Media Gateway. This AMSCore process comes to life on start-up and allows Adobe Media Gateway to register its services to Adobe Media Server. Enable this registry core only when using Adobe Media Gateway.

<Registry enabled="false"> 
    <!-- Adaptor to run registry core on --> 
    <AdaptorName>_defaultRoot_</AdaptorName> 
</Registry>

Note:

Adobe Media Gateway is discontinued as a part of Adobe Media Server, since AMS 5.0.7. Adobe Media Gateway is not a supported product now.

ResourceLimits

Container element.

The elements nested within the ResourceLimits container specify the maximum resource limits for the server, including the HTTP and RTMP protocols.

Contained elements

RetryNumber

Number of times to retry opening a log file. Relevant when opening a log file fails. The default value is 0.

RetrySleep

Number of milliseconds the server waits before retrying to open a log file. Relevant when opening a log file fails. The default value is 100 ms.

Root

Container element.

The Root element is a container for all the other elements in the Server.xml file.

RTMP (AdminServer)

Container element.

This container holds elements that configure which versions of RTMP can be used to connect to the Administration Server. RTMP is the protocol used for communication between Flash Player and Adobe Media Server.

Contained elements

RTMP (Connector)

Container element.

This container holds the elements that configure RTMP (Real-Time Messaging Protocol) for communication between Flash Remoting and Adobe Media Server.

The following reference table lists the default values for all thread configurations.

Default Value

Description

0

Allocates the default number of threads (10).

>0

Allocates the exact number of threads specified.

<0

Associates the default value with the number (N) of processors.

-1

Allocates 1xN threads.

-2

Allocates 2xN threads.

Contained elements

RTMP (Protocol)

Container element.

This container holds the elements that configure RTMP (Real-Time Messaging Protocol). RTMP is the protocol used for communication between Flash Player and Adobe Media Server.

Contained elements

RTMPE

Located in the RTMP container.

Specifies whether Encrypted Real-Time Messaging Protocol (RTMPE) can be used to connect to the Administration Server. (RTMPE also covers RTMPTE.) The default value is true. Setting this element to false prohibits RTMPE and RTMPTE from being used.

Scope

Located in the Logging container.

This element determines whether to write a separate log file for each virtual host or to write one log file for the server.

The value for this element is server or vhost. The default is server, which enables logging for all processes on the server.

Security

Description

Container element.

The elements in this section configure server security.

Contained elements

Availability

Flash Media Server 4

SegmentsPool

Container element.

The elements in this section configure how the segments pool caches segments of video files within Adobe Media Server to increase performance of video streaming and keep frequently used video files in memory.

Contained elements

Server

Container element.

The elements nested within the Server element contains the elements that configure the server.

Contained elements

ServerDomain

Specifies the host name (with the domain) of the server computer. The server uses this value to set the hostname in the referrer header tag when making a net connection to a remote server. If this element is empty the hostname field is empty in referrer header. For security purposes, some application servers require this information as a part of incoming connection requests. If this element is not set, the host name field is not supplied in the referrer header.

Example

 <ServerDomain>mydomain.global.mycompany.com</ServerDomain>

Service

Located in the Httpd container.

On Windows only, specifies the name used to install the webserver as an NT service.

Services

Container element.

The elements in this section control the IPC message queue used by the edge and core processes to communicate with each other.

Contained elements

SmallMemPool

Container element.

The elements in this section configure the small memory pool, which saves small chunks of memory in the server to increase performance of small allocations.

Contained elements

SocketGC

Located in the AdminServer and ResourceLimits containers.

Specifies how often, in seconds, the server checks for and removes inactive sockets. The default value is 60 seconds.

Example

 <SocketGC>60</SocketGC>

SocketOverflowBuckets

Located in the Edge, Core, Admin, ECCP, ACCP containers.

Specifies the number of overflow buckets if all slots in the socket table are in use.

The default number of buckets is 16; specify -1 to use the default number of buckets.

Example

 <Admin>  
     <SocketOverflowBuckets>-1</SocketOverflowBuckets>  
 </Admin>

SocketRcvBuff

The size of the client socket receive buffer, in bytes. The default value is 0, which tells the server to use the operating system default values.

You should explicitly set this value only if you have a very high bandwidth connection that requires a large socket buffer. Setting a high value significantly increases the amount of memory used by each client. It is recommended that you do not explicitly set this value.

SocketSndBuf

The size of the client socket send buffer, in bytes. The default value is 0, which tells the server to use the operating system default values.

You should explicitly set this value only if you have a very high bandwidth connection that requires a large socket buffer. Setting a high value significantly increases the amount of memory used by each client. It is recommended that you do not explicitly set this value.

SocketTableSize

Located in the Edge, Core, Admin, ECCP, ACCP containers.

Specifies the size of the direct-access socket table for quick look-up. The default size is 200. Use -1 for the default value.

Example

 <Admin>  
     <SocketTableSize>-1</SocketTableSize>  
 </Admin>

SSL

Container element.

The SSL elements in Server.xml configure the server to act as an SSL-enabled client by securing the outgoing connections.

Contained elements

SSLCACertificateFile

Located in the SSLClientCtx container.

Specifies the name of a file that contains one or more CA (Certificate Authority) digital certificates in PEM (Privacy Enhanced Mail) encryption format.

SSLCACertificatePath

Located in the SSLClientCtx container.

Specifies the name of a directory containing CA certificates. Each file in the directory must contain only a single CA certificate. File names must be the hash with “0” as the file extension.

For Win32 only: If this element is empty, attempts are made to find CA certificates in the certs directory located at the same level as the conf directory. The Windows certificate store can be imported into this directory by running AMSMaster - console - initialize from the command line.

SSLCipherSuite

Located in the SSLClientCtx container.

Specifies the suite of encryption ciphers that the server uses to secure communications.

This element is a colon-delimited list of encryption resources, such as a key-exchange algorithm, authentication method, encryption method, digest type, or one of a selected number of aliases for common groupings. Each item in the cipher list specifies the inclusion or exclusion of an algorithm or cipher. In addition, there are special keywords and prefixes. For example, the keyword ALL specifies all ciphers, and the prefix ! removes the cipher from the list.

The default cipher list instructs the server to accept all ciphers, but block those using anonymous Diffie-Hellman authentication, block low-strength ciphers, block export ciphers, block MD5 hashing, and sort ciphers by strength from highest to lowest level of encryption.

Note:

Contact Adobe Support before changing the default settings.

The cipher list consists of one or more cipher strings separated by colons. Commas or spaces are also acceptable separators, but colons are normally used.

The string of ciphers can take several different forms.

  • It can consist of a single cipher suite, such as RC4-SHA.

  • It can represent a list of cipher suites containing a certain algorithm, or cipher suites of a certain type.

    For example, SHA1 represents all cipher suites using the digest algorithm SHA1, and SSLv3 represents all SSL v3 algorithms.

  • Lists of cipher suites can be combined in a single cipher string using the + character as a logical and operation.

    For example, SHA1+DES represents all cipher suites containing the SHA1 and DES algorithms.

  • Each cipher string can be optionally preceded by the characters !, -, or +.

  • If ! is used, then the ciphers are permanently deleted from the list. The ciphers deleted can never reappear in the list even if they are explicitly stated.

  • If - is used, then the ciphers are deleted from the list, but some or all of the ciphers can be added again later.

  • If + is used, then the ciphers are moved to the end of the list. This option doesn't add any new ciphers—it just moves matching existing ones.

  • If none of these characters is present, then the string is just interpreted as a list of ciphers to be appended to the current preference list.

  • If the list includes any ciphers already present, the server does not evaluate them.

  • The cipher string @STRENGTH sorts the current cipher list in order of the length of the encryption algorithm key.

The components can be combined with the appropriate prefixes to create a list of ciphers, including only those ciphers the server is prepared to accept, in the order of preference.

Example

This cipher string instructs the server to accept all ciphers except those using anonymous or ephemeral Diffie-Hellman key exchange.

 <SSLCipherSuite>ALL:!ADH:!EDH</SSLCipherSuite>

These cipher strings instruct the server to accept only RSA key exchange and refuse export or null encryption. The server evaluates both strings as equivalent.

 <SSLCipherSuite>RSA:!NULL!EXP</SSLCipherSuite> 
 <SSLCipherSuite>RSA:LOW:MEDIUM:HIGH</SSLCipherSuite>

This cipher list instructs the server to accept all ciphers but place them in order of decreasing strength. This sequencing allows clients to negotiate for the strongest cipher that both they and the server can accept.

 <SSLCipherSuite>ALL:+HIGH:+MEDIUM:+LOW:+EXP:+NULL</SSLCipherSuite>

This string instructs the server to accept only high- and medium-strength encryption, with the high being preferred, and reject export-strength versions.

 <SSLCipherSuite>ALL:+HIGH:!LOW:!EXP:!NULL</SSLCipherSuite>

This string instructs the server to accept all ciphers but to order them so that SSLv2 ciphers come after SSLv3 ciphers.

 <SSLCipherSuite>ALL:+SSLv2</SSLCipherSuite>

The following is the complete list of components that the server can evaluate.

Key exchange algorithm

Description

kRSA

Key exchange

kDHr

Diffie-Hellman key exchange with RSA key

kDHd

Diffie-Hellman key exchange with DSA key

RSA

Ephemeral Diffie-Hellman key exchange

DH

RSA key exchange

EDH

Ephemeral Diffie-Hellman key exchange

ADH

Anonymous Diffie-Hellman key exchange

Authentication methods

Description

aNULL

No authentication

aRSA

RSA authentication

aDSS

DSS authentication

aDH

Diffie-Hellman authentication

Encryption methods

Description

eNULL

No encoding

DES

DES encoding

3DES

Triple-DES encoding

RC4

RC4 encoding

RC2

RC2 encoding

IDEA

IDEA encoding

NULL

No encryption

EXP

All export ciphers (40-bit encryption)

LOW

Low-strength ciphers (no export, DES)

MEDIUM

128-bit encryption

HIGH

Triple-DES encoding

Digest types

Description

MD5

MD5 hash function

SHA1

SHA1 hash function

SHA

SHA hash function

Additional aliases

Description

All

All ciphers

SSLv2

All SSL version 2.0 ciphers

SSLv3

All SSL version 3.0 ciphers

DSS

All ciphers using DSS authentication

SSLClientCtx

Container element.

Configures the server to act as an SSL-enabled client by securing the outgoing connections.

Contained elements

SSLRandomSeed

Located in the SSL container.

Specifies the number of bytes of entropy to use for seeding the PRNG. You cannot specify anything less than 8 bytes, and the default is 16. Entropy is a measure of randomness. The more entropy, the more random numbers from the PRNG will be.

Example

 <SSLRandomSeed>16</SSLRandomSeed>

SSLSessionCacheGC

Located in the SSL container.

Specifies how often to check for and remove expired sessions from the server-side session cache.

Example

 <SSLSessionCacheGC>5</SSLSessionCacheGC>

SSLVerifyCertificate

Located in the SSLClientCtx container.

Specifies whether the certificate returned by the server should be verified. Certificate verification is enabled by default. To disable certificate verification, specify false.

Note:

Disabling certificate verification can result in security problems.

Example

 <SSLVerifyCertificate>true</SSLVerifyCertificate>

SSLVerifyDepth

Located in the SSLClientCtx container.

Specifies the maximum depth of the certificate chain to accept. If a self-signed root certificate cannot be found within this depth, certificate verification fails. The default value is 9.

Example

 <SSLVerifyDepth>9</SSLVerifyDepth>

StreamAdaptors

Specifies which library to load for a particular stream, based on the stream’s prefix. This effectively defines a whitelist of libraries that can be loaded by the server for each stream type.

When you play a stream, you specify a prefix. The prefix indicates what kind of stream it is. The following example shows a prefix that indicates that the stream is of type MP3:play("mp3:mystream.mp3");Note that the the prefix does not necessarily match the file type. For example, for MP4, you can specify the following:play("mp4:mystream.f4v");

In this case, MP4 is the encoding, not the file type. So you can use mp4:mystream.mov, mp4:mystream.mp4, and so on.

To specify a library for a particular stream, add a sub-element with the following syntax:<prefix lib="library_name"/>

Supported streams are:

  • FLV (processed by the library specified by the flv sub-element)

  • F4F (processed by the library specified by the f4f sub-element)

  • ID3 (processed by the library specified by the id3 sub-element)

  • MP3 (processed by the library specified by the mp3 sub-element)

  • MP4 (processed by the library specified by the mp4 sub-element)

  • RAW (processed by the library specified by the raw sub-element)

For FLV streams, you do not specify the prefix or the extension; for example:play("mystream");

In this case, the adaptor that you define for the FLV file does not match the prefix (because there is none). The library defined by the flv sub-element is matched by Adobe Media Server internally to determine which library to use to process the stream.

play("mp3:mystream.mp3");
play("mp4:mystream.f4v");
<prefix lib="library_name"/>
play("mystream");

Example

<flv lib="libflv"/> 
<f4f lib="libf4f"/> 
<mp3 lib="libmp3"/> 
<mp4 lib="libmp4"/> 
<raw lib="libraw"/> 
<id3 lib="libid3"/>

See also

StreamLogLevel

Controls log levels for all stream adaptors (FLV, MP4, and RAW). Possible values are verbose, warning, and error.

The default value is warning.

Example

<StreamLogLevel>warning</StreamLogLevel>

See Also

Streams

Container element.

The Streams elements configure how the server plays and records MP4, F4V, MOV, and other MP4 file types.

Contained elements

SWFFolder

Located in the SWFVerification container.

Specifies a folder containing SWF files that are verified to connect to any application on this server. Use a semicolon to separate multiple directories.

Example

The following example allows SWF files from either the C or the D directory to be authenticated:

 <SWFFolder>C:\SWFs;D:\SWFs</SWFFolder>

SWFVerification

Container element.

Contains elements that configure how SWF files connecting to an application are verified.

Contained elements

TerminatingCharacters

Located in the Logging container.

Specifies the final characters of each log entry in log files. The default is CRLF (carriage return and line feed).

Example

 <TerminatingCharacters>CRLF</TerminatingCharacters>

ThreadPoolGC

Located in the ResourceLimits container.

Specifies in minutes how often Adobe Media Server checks for and removes unused I/O threads.

The default time is 20 minutes. You cannot specify less than 20 minutes.

Example

 <ThreadPoolGC>25</ThreadPoolGC>

Time

Located in the Logging container.

Specifies the time field in a log file.

The time field in a log file can be specified either as UMT (GMT) or local time. The default setting is local.

Example

 <Time>local</Time>

TrimSize

Located in the HandleCache container.

Specifies a percentage of cached handles to remove. Can be specified as a number between 0 and 1, representing 0% to 100%. The default value is 0.2 (20%).

Example

 <TrimSize>0.2</TrimSize>

TTL

Located in the Cache container.

Specifies in minutes how long each SWF file remains in the SWF verification data cache. The default value is 1440 minutes (24 hours).

UID

Located in the Process containers.

This element contains the server process user ID.

If you do not specify a UID or GID, the server or Administration Server runs as root. This element is applicable to Adobe Media Server running on Linux systems only.

See also

UpdateInterval

Specifies how often thread statistics are collected. The default value is every 1024 messages.

Example

 <UpdateInterval>1024</UpdateInterval>

UpdateInterval (Cache)

Located in the Cache container.

Specifies the maximum time in minutes to wait for the server to scan the SWF folders for updates when there is a miss in the cache. The default value is 5 minutes.

UserDefined

Container element.

Define elements within the UserDefined element to store data that File plug‑ins and Authorization plug‑ins can retrieve.

VirtualDirectoryForFile

Enables virtual directory mappings for File objects. The default is disabled.

If you map File objects in the Application.xml file but don’t have the feature enabled in the Server.xml file, you'll see the following message in the log:"Virtual directories for file objects is not supported due to the Server level security setting."

To avoid this log message, enable VirtualDirectoryForFile. For more information, see Enable virtual directory mappings for server-side File objects.

"Virtual directories for file objects is not supported due to the Server level security setting."

Example

<VirtualDirectoryForFile enable="false"></VirtualDirectoryForFile>

See also

Availability

Flash Media Server 4

VideoAutoBufferReadSize

Located in the Playback container.

The server caches F4V/MP4 video, audio, and other data in memory. Caching data allows the server to make fewer disk reads and to perform better. Each data type (audio, video, and other) has its own cache. You can tune the size of each cache, depending on the type of content you are delivering, to achieve better disk performance. For example, if you are delivering audio-only content, increase the AudioAutoBufferReadSize buffer, and decrease the VideoAutoBufferReadSize buffer.

The minimum size is 1024 bytes. The default value is 153600 bytes.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy