If you chose the default directory in the installer, the Flash Media Server installation directory is located at /opt/macromedia/fms/.
The Flash Media Server directory contains these items:
The fmsmaster file is the server application.
The fmsadmin file is the server's administration controller. When administrators connect to the server with the management console, they are actually connected to the service, which communicates with the server to perform administration tasks.
The License.htm file contains the text of the Flash Media Server license agreement.
The Readme.htm file contains late-breaking information and notes about Flash Media Server.
The tcSrvMsg file is a component of the server.
The conf directory contains the server's hierarchy of XML configuration files and the fms.ini file.
The applications directory is the directory in which you create registered application directories for your media applications. For example, you could create a my_app subdirectory in the applications directory and put your server-side application files for the my_app application in that subdirectory. At installation time, the location of the applications directory is written to the AppsDir tag in the Vhost.xml configuration file.
The fms2_console.swf file (located in the applications directory) can be used to open the Flash Media Server management console.
The scriptlib directory contains the ASC files for the web services. At installation time, the location of the scriptlib directory is written to the ScriptLibPath tag in the Application.xml file.
As soon as the server is started, a logs directory that contains all of the various types of logs is created in the root.
The FMSCore.exe file is the executable where Flash Media Server applications run. The way the server is configured determines how many applications run on a single FMSCore. All script execution and streaming takes place from this location.
The FMSEdge.exe file monitors for connections to Flash Media Server and passes connections to a FMSCore process. There can be more than one instance of FMSEdge running on the system.
The adminserver script is used to start, stop, and restart the FMSAdmin server directly. This script is also used to set up fmsadmin correctly.
The docs folder contains Flash Media Server documentation in PDF format.
The far tool is a command-line compiler utility that lets you package all server-side scripts into one archive file.
The fms script packages the combination of calling adminserver and server at the same time.
The fmsconfig and fmsini files are used by the Flash Media installer in the installation process. They can be disregarded.
The fmsmgr script starts and stops the server. It also checks on status and other actions, such as controlling autostart status.
The installFMS script installs Flash Media Server.
The uninstallFMS script removes an installation of Flash Media Server.
The modules folder contains modules stored as individual libraries for Flash Media Server to load and operate with. For example, modules are used to log, authenticate, and communicate.
Comments
Axx
said on
Dec 6, 2006
at
1:58 AM :
You should be able to change the license profile in the licenses folder. It works with windows, but how can you do this in Linux?
blakbro2k
said on
Jun 25, 2007
at
7:17 PM :
I'll try to answer the best that i can since i hate it when people know but don't share. While i was looking through the linux files i saw that in the fms.ini file, there is a section as follows:
# Active Profile in use with serial key licensing # For example: # SERVER.ACTIVE_PROFILE = 150.pro # SERVER.ACTIVE_PROFILE = 150.pro
# License key for Flash Media Server # For example: # SERVER.LICENSEINFO = FMD200-XXXXX-XXXXX-XXXXX # SERVER.LICENSEINFO =
i believe that this is where you put your license information. im developing so i have not tried it yet.
Comments
Axx said on Dec 6, 2006 at 1:58 AM : blakbro2k said on Jun 25, 2007 at 7:17 PM :