Oracle
Video Server Administrator's Guide: UNIX Release 2.1.7.3 A42271_4 |
|
This chapter tells you how to operate the Oracle Video Server (OVS). It covers:
Follow these steps to start the OVS and Oracle Media Net (OMN) components:
% cd $ORACLE_HOME/vs21/admin
% ./ovsstart
Refer to The Start-up Script section later in this chapter to see a typically used sample start-up script.
Oracle strongly recommends starting the OVS processes with the supplied scripts. If you need to modify your configuration parameters from those created at installation, create a backup copy of the script ovsstart and modify the parameters in the script.
To stop the OVS:
% cd $ORACLE_HOME/vs21/admin
% ./ovsstop
In this section, we examine a sample OVS start-up script (ovsstart) to better explain the processes used by the OVS. Start-up scripts can vary from system to system, so do not be concerned if the start-up script created for your system does not exactly match the sample provided here.
Should you need to change the values used by a particular OVS component (such as the number of video streams provided by the video pump) you should modify the start-up script to start the component with the required values. For more information on the OVS components, and the command line options accepted by each component, refer to Chapter 7, "Oracle Video Server Components Reference."
The OMN address server (mnaddrsrv) maps Media Net addresses to corresponding physical addresses. When a server process starts, it obtains its Media Net address from the address server.
echo -n "starting address server ..... " $ORACLE_HOME/bin/mnaddrsrv & sleep 1
The OMN name server (mnrpcnmsrv) maps the names of server processes to their Media Net addresses. When a server process is started, it registers its name and Media Net address with the name server. Before a client can send a message to the server, the client first contacts the name server to find the server's Media Net address.
echo -n "starting name server ...... " $ORACLE_HOME/bin/mnrpcnmsrv & sleep 1
The OMN process server (mnprocsrv) receives service requests from clients that are intended for the stream service (vsstrmsrv) and the video content manager (vscontinf), and routes the messages to the appropriate process to service the requests. If multiple instances of vsstrmsrv or vscontinf are running, mnprocsrv will route the requests to an available instance to provide for scalability.
echo -n "starting process server ...... " $ORACLE_HOME/bin/mnprocsrv & sleep 1
The OMN logger process (mnlogsrv) writes system and trace messages to the logfile mzlog. Use the logfile for troubleshooting OVS processes. The logging level, specified with the -l option, is the default logging level of 6, which logs messages of normal significance and above. The logfile (mzlog) that messages are written to is specified with the -f option.
echo -n "starting logger .... " $ORACLE_HOME/bin/mnlogsrv -l 6 -m $ORACLE_HOME/vs21/mesg/mzlm.dat \ -f $ORACLE_HOME/vs21/log/mzlog & sleep 1
The connection service (mnocs) maps physical addresses of client
devices to physical downstream addresses on the server computer. When using
the OVS in a corporate LAN environment, the connection service uses the
-a command-line option, which dynamically chooses downstream managers
for clients.
echo -n "starting connection service ....... " $ORACLE_HOME/bin/mnocs -a & sleep 1
The media data store process (mdsdirsrv) manages files in the MDS volume and controls access to those files. This example uses the -W command line option, which mounts all MDS volumes specified in the voltab file in read-write mode, allowing new files to be written to the MDS volume while clients access files for playback.
echo -n "starting media data store ....... " $ORACLE_HOME/bin/mdsdirsrv -W -f $ORACLE_HOME/vs21/admin/voltab & sleep 1
The stream service (vsstrmsrv) handles requests for content files from clients accessing the server. When the stream service receives a request for a specific content file, it reads a tag file associated with the requested file in the Oracle Media Data Store (MDS). The stream service then coordinates delivery of the content with a video pump.
echo -n "starting stream service ....... " $ORACLE_HOME/bin/vsstrmsrv & sleep 1
The video pump (vspump) reads files from the Oracle Media Data
Store and sends the video data to a client over the network. This example
uses the
-y option to specify that one video pump be started on processor
2 and another on processor 3. Each video pump supports 10 video streams
(specified with the -m option) using a maximum bit rate of 2.05
Mbps (specified with the -b option). Note that the buffer size specified
with -n is set to 8192 bytes (8K). When using the OVS in a corporate
LAN environment, 8K is the only supported packet size.
echo -n "starting video pump ....... " $ORACLE_HOME/bin/vspump -a -S -o dUDP:127.0.0.1:5000 -m 10 -n 8192 -b 2.05 -y 2 -t& sleep 1 echo -n "starting video pump ....... " $ORACLE_HOME/bin/vspump -a -S -o dUDP:127.0.0.1:5000 -m 10 -n 8192 -b 2.05 -y 3 -t& sleep 1
The video content manager (vscontinf) allows a client device to query an MDS volume for a listing of available files.
echo -n "starting stream info server....... " $ORACLE_HOME/bin/vscontinf &
|
Copyright © 1997 Oracle Corporation. All Rights Reserved. |
|