50
FLASH
MEDIA
SERVER
4.5
CONFIGURATION
AND
ADMINISTRATION
Configuring the server
Last updated 11/28/2012
•
Vod application:
VOD_DIR
Mapping directories to network drives
By default, the server runs as System Account with no access to network drives. You can change the service user to a
user with network access privileges with a UNC path.
A Windows network-mapped drive is not valid when a user is logged out. If the server is running as a service and the
user is logged out, the mapped drive is removed as well. To run with the mapped drive, lock the server instead of
logging out. Using the UNC path is preferred when the server is running as a service.
1
Stop Flash Media Server and Flash Media Administration Server.
2
Make the changes to the configuration.
3
Check that the server user has appropriate access rights to map to the network drive (system account rights are
usually not sufficient.)
4
Restart Flash Media Server and Flash Media Administration Server.
Setting the location of recorded streams and shared objects
By default, all recorded streams for an application are stored in a streams folder in the application directory. Shared
objects are stored in a shared objects folder in the application directory.
Note:
Adobe strongly recommends that folders that store streams always contain only streams and no other application
files.
Use the
StorageDir
tag in the Application.xml file to specify a different location to store streams or shared objects.
You could do this for vod applications. For example, if you already have a collection of video files in a directory other
than the application directory, you can set the storage directory to that other directory instead of copying content to
the application directory.
When you specify a value for the
<storageDir>
element in the application-specific XML, that value is specific to the
application. Otherwise, when you specify a value in the virtual host-level Application.xml, the scope is extended to all
the applications on that virtual host.
Within the directory that you specify as the storage directory, you must create physical subdirectories for different
application instances. Flash Media Server sandboxes the content for each instance of an application.
Let’s say, for example, you set the storage directory to
C:\Content
for the
chatApp
application:
<storageDir>C:\Content</storageDir>
When a user connects to the
firstRoom
instance of the
chatApp
application and tries to play a stream, the server looks
for the stream in a subfolder
C:\Content\firstRoom
. Content for each instance is sandboxed from other instance of
the same application; a user who connects to the
secondRoom
instance would not be able to access the content in
C:\Content\firstRoom
.
If you do not want resources to be sandboxed by application and application instance, use virtual directories.