This chapter gives information on starting and stopping RealServer on both Windows NT and UNIX platforms, setting up MIME types, and explains the RealServer license method.
Instructions in this section describe how to start and stop RealServer running under Windows NT.
RealServer can be started manually or as a service. You can configure each service to use different configuration files.
Whether you start RealServer manually or as a service, if you start it without including a configuration file, RealServer uses the most recently used configuration settings.
You can start RealServer from the Start menu or from a command line.
On the Start menu, click Programs, then click Real, and finally click RealServer G2. This starts the rmserver.exe program. If this is the first time you have run RealServer, it loads the default configuration file.
 |
Additional Information |
|---|
| The configuration file is described in Chapter 4: Customizing RealServer Features. |
Move to the RealServer Bin directory and type the following at a command line:
rmserver ..\rmserver.cfg
To limit the amount of memory that RealServer G2 uses, start RealServer with the -m parameter:
rmserver ..\rmserver.cfg -m 32
where the number after -m can be any amount of memory in megabytes, 32 or greater. Each megabyte of RealServer memory accomodates 3 to 4 simultaneous connected users. To allow 200 users to connect, specify 50 megabytes of memory instead of 32. (This parameter is optional.)
RealServer on Windows NT can be run as a service. An option during setup configures this automatically. Instructions in this section describe how to add RealServer to the services list if you did not instruct setup to do so.
You can load different configuration files into different Windows NT registry keys, and connect them to different instances of RealServer running as separate services. Multiple services of RealServer can be useful if you want to switch between a production and a test configuration file, for example.
rmserver.exe -import[:key]configuration_file
key is the Registry key name you want to use. If you omit it, the default name Config is substituted.
configuration_file is the path and configuration file you want to import. For example, the following command:
rmserver.exe -import:Server1 ../rmserver.cfg
imports all the values in the rmserver.cfg file into the following key of the Windows NT registry:
HKEY_CLASSES_ROOT\Software\RealNetworks\RealMedia Server\6.0\Server1
 |
Note |
|---|
| You must supply the path to the configuration file. If RealServer cannot find the configuration file, it may not start. |
 |
Tip |
|---|
You can now start RealServer using this configuration
by typing the following at a command line: rmserver.exe registry:Server1
|
rmserver.exe -install[:ServiceName] "parameters"
ServiceName is the name that will appear in the Services dialog box. If you omit ServiceName, RMServer is substituted.
parameters is either the name of the configuration file, or the registry and key name, as entered in Step 2. The format of the registry and key name is registry:key. Any command line parameters, such as the -m switch, can be used.
|
|
Note |
|---|
The quotation marks surrounding parameters are
required.
|
The next time you start RealServer from the Services dialog box, it will use the settings specified in parameters, and will be configured to start automatically.
For example, the following command:
rmserver.exe -install:RMInternet "Server1"
installs RealServer with the service name "RMInternet" and uses the settings in the Server1 key.
At a command prompt, type the following:
rmserver.exe -remove[:ServiceName]
where ServiceName is the optional name of the service. If you omitted a service name when you installed the service, you can omit it here, and RealServer will use RMServer.
You can have configuration files with different names for different configurations of a single RealServer, or use different names for different RealServer installations.
You can load configuration files into separate registry keys. Then, run RealServer as a service, one for each configuration file you loaded.
rmserver.exe registry:key
key is name you want to use for the configuration. RealServer places the configuration information in HKEY_CLASSES_ROOT\Software\RealNetworks\RealMedia Server\6.0\Key.
In the example from Step 2 of "Setting Up RealServer as a Service", in which the configuration settings are loaded into the "Server1" key, the full key name would be HKEY_CLASSES_ROOT\Software\RealNetworks\RealMedia Server\6.0\Server1.
If RealServer was started from the Start menu or the command prompt, switch to the command window and press CTRL+C.
If RealServer was started as a service, stop RealServer through the Services control panel.
Instructions in this section describe how to start and stop RealServer running under UNIX.
Start RealServer initially with the default configuration file; later, you can create other configuration files and start RealServer using those.
Run the rmserver program. It is located in the bin subdirectory of the RealServer directory, and the configuration file (rmserver.cfg) is located in the main RealServer directory.
Move to the bin directory and type the following:
rmserver ../rmserver.cfg
If you do not start from the bin directory, RealServer cannot understand the relative paths in the configuration file.
You can run RealServer in the background by typing the following from the bin directory:
rmserver ../rmserver.cfg &
If you have other configuration files, you can substitute their names for rmserver.cfg and RealServer will use the settings in the file you name.
To limit the amount of memory that RealServer G2 uses, start RealServer with the -m parameter:
rmserver ../rmserver.cfg -m 32
where the number after -m can be any amount of memory in megabytes, 32 or greater. Each megabyte of RealServer memory accomodates 3 to 4 simultaneous connected users. To allow 200 users to connect, specify 50 megabytes of memory instead of 32. (This parameter is optional on FreeBSD and Linux.)
To stop RealServer under UNIX, first obtain the process identification number, and then issue the kill command with that process number. The process ID is stored in the rmserver.pid file, which is usually kept in the Logs directory. The PIDPath variable specifies this location.
You can perform both actions with one command. Move to the directory which contains the RealServer PID file, and type the following:
kill `cat pidfile`
where pidfile is the name of the RealServer PID file, as shown in the PIDPath variable. The usual name for this file is rmserver.pid.
RealServer works with any Web server that supports configurable MIME types. Make sure that your Web server has the RealNetworks MIME types defined.
In addition, RealServer serves its own HTML pages. To this end, be sure that RealServer has the correct MIME type information.
Refer to the instructions accompanying your Web server to define the following MIME types on your Web server:
audio/x-pn-realaudio (files with a .ra, .rm or .ram file extension)audio/x-pn-realaudio-plugin (files with a .rpm file extension)application/smil (files with a .smi or .smil extension)application/sdp (files with a .sdp extension)application/x-pn-realmedia (files with .rp, extension)text/html (files with a .html or .htm extension)image/gif (files with a .gif extension)image/jpg (files with a .jpg or .jpeg extension)
When you install RealServer, the MIME Types section is present in the configuration file. You need only examine this list if something happened in the meantime and you think the list might be complete. You can examine the MIME types section using the following instructions.
|
|
Additional Information |
|---|
| See "Customizing RealServer Features" for instructions on using RealSystem Administrator. |
You should only modify the list if you will be streaming a data type via HTTP that is not on the list.
Information about the license for your RealServer, including a list of enabled features, is stored in a file in a license directory. If you purchase additional features, these will be listed in additional files stored in the same directory. The license files are written in XML format.
The LicenseDirectory variable in the configuration file tells RealServer where to look for license information.
|
|
Additional Information |
|---|
| To learn how to modify RealServer settings, see "Customizing RealServer". |
You can read the file with RealSystem Administrator by clicking About in the left-hand frame. A second browser window appears, displaying the values for your license file. If you have multiple license files, RealServer will show the values for all of them at once.
You can also read the file with any text editor. However, if you have multiple files, you will need to read them individually and calculate any additive features (such as number of streams) yourself.
If the license file is invalid, RealServer will report an error message, add the error to the error log file, and will not start.
To upgrade your license so that you can use more of RealServer's features, contact RealNetworks or your reseller.
The following features are controlled by the license:
If your RealServer suddenly allows fewer connections or otherwise appears to be using minimum settings, either your license has expired or RealServer is unable to start using the settings you've selected. The table below lists the minimum settings present in every RealServer.
|
|
Note |
|---|
| Evaluation versions may have lower minimum values. |