Chapte 5
Post-Installation Tasks for the Oracle Video Server

This chapter explains post-installation tasks for the Oracle Video Server (OVS).

Topics covered in this chapter are:

Installing the Online Documentation

To make OVS documentation more easily accessible, it is available online. There are two forms of online documentation:

HTML, which is readable by most HTML browsers.
Adobe(TM) Acrobat(TM) (PDF files), which are readable with the Adobe Acrobat Reader and when printed appear exactly like the printed version of the documentation.

This release includes Adobe Acrobat Reader to view the PDF documentation. To read the HTML documentation you must obtain a web browser which supports HTML 2.0 with additional support for tables.

The online documentation is installed on the OVS computer in the file $ORACLE_HOME/vs21/doc/ovsdoc.tar. Use these commands to install these files into $ORACLE_HOME/vs21/doc:

% cd $ORACLE_HOME/vs21/doc

% tar -xvf ovsdoc.tar

This creates two additional directories: $ORACLE_HOME/vs21/doc/html and
$ORACLE_HOME/vs21/doc/pdf and installs the HTML and PDF documentation files in those directories.

Obtaining a Web Browser

You can obtain a web browser that supports HTML 2.0 with additional support for tables from several FTP sites. Your organization may also have a site license for a particular browser vendor. For information on obtaining a web browser for your organization's use refer to your organizations computing services department.

Viewing the HTML Documentation on the Oracle Video Server

To view the documentation that is stored on your server from a browser running on that server open the local file:

file:///$ORACLE_HOME/vs21/doc/html/roadmap.html

If you wish, you can set up an HTTP server and make the documents available to other readers on your corporate intranet.

Installing Adobe Acrobat Reader for UNIX

The installation file for the Adobe Acrobat Reader for UNIX is located on the product distribution CD-ROM under/cdrom/ovsdoc/acroread. The file is named install.

Viewing the Adobe Acrobat PDF Files

To view the Adobe Acrobat PDF files, start the Acrobat Reader as described in the documentation provided with Adobe Acrobat and open the file:

$ORACLE_HOME/vs21/doc/pdf/roadmap.pdf

This will display the Oracle Video Server Documentation Roadmap from which you can navigate to all online OVS documentation.

For Further Information

For more information on the online documentation, refer to the Oracle Video Server Documentation Roadmap.

Assigning Video Pumps to Processors (For SMP Servers)

Perform the following task when running the OVS on multi-processor (SMP) Sun Solaris platforms.

Task 1: Assigning Root Privileges to the Video Pump

To function properly on a multi-processor Solaris platform, the video pump (vspump), must be given root privileges. This allows vspump to lock down its own processor so it can operate in real-time.

Assign these permissions to vspump:

# chmod +s ./vspump

# chown root ./vspump

Exit from the root account:
```
# exit

% 
```
Edit the shell script ovsstart, in the directory $ORACLE_HOME/vs21/admin, to include the -t option for vspump. Give this option to each video pump instance that will run on its own processor.

Example

This example shows the -t option added to the video pump in the ovsstart shell script:

vspump -a -S -o dUDP:127.0.0.1:5001 -m 10 -n 8192 -b 2.05 -r 1 -t

Task 2: Assigning a Video Pump to a Processor

To function properly on a multi-processor server platform, each video pump (vspump) must be allowed to lock down its own processor. This allows the video pump to operate in real-time. This should only be done on multi-processor servers.

Edit the shell script ovsstart, located in the $ORACLE_HOME/vs21/admin directory, to include the -y command line option of the video pump. This option accepts an argument for a processor to be dedicated to video pump usage. Processors are numbered starting with 0 (zero) and increasing up to the number of processors in the system. A four processor system numbers the processors 0, 1, 2, and 3.

Example 1

This example dedicates processor 1 of the server to the video pump with the -y option.

vspump -a -S -o dUDP:127.0.0.1:5001 -m 30 -n 8192 -b 2.05 -r 1 -y 1 -t

At least one processor must not be dedicated to a video pump, as to allow other parts of the system, such as the server's operating system and other OVS processes, to run. You can only use one instance of vspump per dedicated processor.

Example 2

This example starts three video pumps and assigns them to processors 1, 2, and 3. Note that this example assigns each video pump ten concurrent streams with the -m option. For optimum performance, divide the number of concurrent video streams evenly among video pumps. In this example 30 concurrent streams are required, so each video pump is assigned ten video streams.

vspump -a -S -o dUDP:127.0.0.1:5001 -m 10 -n 8192 -b 2.05 -r 1 -y 1 -t
vspump -a -S -o dUDP:127.0.0.1:5022 -m 10 -n 8192 -b 2.05 -r 1 -y 2 -t
vspump -a -S -o dUDP:127.0.0.1:5300 -m 10 -n 8192 -b 2.05 -r 1 -y 3 -t

For Further Information

For more information on the video pump and its usage, refer to vspump in Chapter 7, "Oracle Video Server Components Reference" of the Oracle Video Server Administrator's Guide.

Loading Sample Content into the Oracle Media Data Store

Oracle provides sample video files for you to use when setting up the OVS. These files are MPEG-1 encoded with a bit rate of 1.536 Mbps. If you do not yet have MPEG-1 encoded video, use these files to test your OVS installation once you have installed both the OVS and Oracle Video Client (OVC) software.

Note

You must encode your video prior to loading it into the MDS; the OVS does not encode video content.

Follow these steps to load the MDS with sample content. For more information loading and preparing content for playback, refer to Chapter 4, "Preparing and Loading Content" in the Oracle Video Server Administrator's Guide.

Start OVS with the script ovsstart located in $ORACLE_HOME/vs21/admin:
```
% cd $ORACLE_HOME/vs21/admin

% ./ovsstart
```

Note

Under normal circumstances, always use the ovsstart script to start OVS.

Change to the directory $ORACLE_HOME/vs21/demo/content created during the installation process:
```
% cd $ORACLE_HOME/vs21/demo/content
```

This directory contains the sample video content provided by Oracle, assuming the sample content was installed during OVS installation.

Use the mdsdir utility with the -f option to verify that you can contact the MDS volume. This lists the free space available in the MDS volume:
```
% mdsdir -f /mds/video

Volume /mds/video (rw): 0 matches 

2500 MB's of free space in 1 fragment(s) 

largest free block is 2500 MB's
```

Note that the volume name used in this example is video, the default MDS volume name supplied by the Oracle Installer. Use the volume name which you specified during installation.

Copy the sample content files to the MDS volume with the mdscopy utility:
```
% mdscopy oracle1.mpg /mds/video/oracle1.mpg
```

Use mdsdir with the -b option to list the files in the MDS volume:

% mdsdir -b /mds/video

Volume /mds/video (rw): 2 matches 

14854692 Feb  1 14:15:26 rw oracle1.mpg 

14854692 Feb  1 14:17:32 rw oracle2.mpg

etc...

Before you can play a video content file, you must create a tag file for it. Tag files are used to store information about content files. Tag the content files using the vstag utility as shown:
```
% vstag /mds/video/oracle1.mpg /mds/video/oracle1.mpi
```

Note that this example explicitly states the MDS volume in which to place the completed tag files (/mds/video/oracle1.mpi). vstag requires that the full MDS path of the output file be explicitly stated.

Use mdsdir with the -b option to list the files in the MDS volume:

% mdsdir -b /mds/video

Volume /mds/video (rw): 2 matches 

14854692 Feb  1 14:15:26 rw oracle1.mpg 

      10236 Feb  1 14:21:12 rw oracle1.mpi

etc...

Use the vstagprint utility with the -s option to look at the header of the tag file oracle1.mpi. The tag file can provide information such as: the bit rate the video is encoded at, the size of the file, and playback length of the file in milliseconds.

% vstagprint -s /mds/video/oracle1.mpi 

Tag file version: 3.4 

Current code is version 3.4, back-compatible to version 3.4 

magic=aabbccdd (should be aabbccdd) 

file describes content for: 

1 member files: 

# 1. format=MPEG 1     transport=None     flags=1 

file="/mds/video/oracle1.mpg" Size = 14854692 

bitrate=1536000 bits/second 

elapsed length=77368 milliseconds 

presentation rate=1000 

frames/sec(* 1000)=29970 

203 tags in tag file. 

audio PID/stream = 0/0 video PID/stream = 0/0 

width: 352, height: 240, pel aspect ratio (* 10000): 10950 

Tags begin at offset 0 after header.

Copy the remaining sample content files to your MDS volume and tag them.

The MDS volume now has video content loaded and tagged for use.

If you intend to operate your OVS as a non-real-time system; that is, a system which does not guarantee the delivery of video to several clients at once with a certain quality of service, you can skip the section Enabling Real-Time Video Delivery and either shut down OVS (see Stopping the Oracle Video Server ), or stream video to a client to see if the system performs properly.

Enabling Real-Time Video Delivery

The installation process creates a non-real-time Oracle Media Data Store (MDS) volume. A non-real-time MDS volume does not deny client requests, regardless of the load placed on the MDS volume. While this mode is useful for loading video content into an MDS volume, it does not allow for consistent quality of service when delivering video to client devices.

To create a real-time MDS volume, where access to the volume is limited to a predefined maximum to ensure quality of service, you must obtain the maxbw value. The maxbw value specifies the maximum rate at which all OVS components can together read and/or write to an MDS volume.

Create a Real-Time Oracle Media Data Store

Follow these steps to obtain the correct maxbw value for your MDS volume and mount the MDS volume in real-time mode.

If the OVS components are not yet running, start them with the script ovsstart, located in the directory
$ORACLE_HOME/vs21/admin:
```
% cd $ORACLE_HOME/vs21/admin

% ./ovsstart
```
Use the mdsvstat utility with the -a command line option to determine the maxbw of the MDS volume. Use the -f command line option to locate the voltab file used to define MDS volume being queried, followed by the name of the MDS volume you used during software installation. This example queries the volume video for its maxbw value:
```
% mdsvstat -a -f $ORACLE_HOME/vs21/admin/voltab video

Recommended maxbw setting for volume video is: 55 Mbps
```

For more information on mdsvstat refer to the "Media Data Store Utilities" chapter of the Oracle Video Server Utilities User's Guide (online only).

Make a copy of the voltab file located in the directory $ORACLE_HOME/vs21/admin and name it voltab_nonrealtime.
```
% cp voltab voltab_nonrealtime
```

This gives you volume definitions for both a real-time and a non-real-time MDS volume. When you are operating the OVS for strictly administrative functions (such as loading and tagging video content) you should use the non-real-time file. This will allocate more bandwidth to utilities such as mdscopy and vstag.

Execute the script ovsstop located in the directory $ORACLE_HOME/vs21/admin:
```
% ./ovsstop
```

Note

You should always use the script ovsstop to shut down OVS.

Edit the voltab file to include the maxbw value.

video maxbw=55,striped,width=32k,raidsize=4 \

spares=/dev/rdsk/c{3}t{3}d0s6 /dev/rdsk/c{0-3}t{0-3}d0s6

Caution

The above example shows the voltab file divided across two lines. When editing a voltab entry it should all be on one line. The only division of lines should occur when the text editor you use wraps from one line to the next. Do not place a hard return in a voltab entry.

You can now start OVS with the start-up script ovsstart using the modified voltab file. The MDS volume will be mounted in real-time mode.

Verify that the MDS volume is mounted in real-time mode using the mdsdir utility with the -c command line option. This will display the total available bandwidth of the volume.
```
% mdsdir -c

Volume /mds/video (rw): 55 out of 55 Mbps available 
```

The output produced by -c should state the bandwidth available from the MDS volume. In this example 55 Mbps of bandwidth is available from the MDS volume video.

Your installation of OVS is now complete. If you have not yet done so, install the Oracle Video Client (OVC), and test your OVS system. Refer to the Oracle Video Client Software Guide for information on installing and operating the Oracle Video Client. Refer to the Oracle Video Server Administrator's Guide for information on operating OVS. If you will not use the OVS immediately, you may stop it.

Stopping the Oracle Video Server

Follow these steps to stop OVS.

Change to the directory $ORACLE_HOME/vs21/admin:
```
% cd $ORACLE_HOME/vs21/admin
```
Execute the shell script ovsstop:
```
% ./ovsstop
```

This will stop the OVS processes. You should always use ovsstop to shut down the OVS.

Chapte 5 Post-Installation Tasks for the Oracle Video Server

Installing the Online Documentation

Obtaining a Web Browser

Viewing the HTML Documentation on the Oracle Video Server

Installing Adobe Acrobat Reader for UNIX

Viewing the Adobe Acrobat PDF Files

For Further Information

Assigning Video Pumps to Processors (For SMP Servers)

Task 1: Assigning Root Privileges to the Video Pump

Example

Task 2: Assigning a Video Pump to a Processor

Example 1

Example 2

For Further Information

Loading Sample Content into the Oracle Media Data Store

Note

Note

Enabling Real-Time Video Delivery

Create a Real-Time Oracle Media Data Store

Note

Caution

Stopping the Oracle Video Server

Chapte 5
Post-Installation Tasks for the Oracle Video Server