The RealSystem ad serving feature uses SMIL to lay out clips and ads. You have the greatest flexibility when you set up your own SMIL file as described in "SMIL Files with Ad Content". However, RealServer can automatically generate a SMIL file that includes an ad when a single media clip is requested. If your site hosts a large number of RealVideo clips, for example, you can simply post the clips and have RealServer automatically generate the SMIL file and get the ad for you.
Automatic SMIL generation works only with RealServer's general ad serving feature, not with rotating banner ads. It allows for just one ad per requested clip. It lets you define banner ads or ads that appear before the clip. It also lets you define whether ads appear above, below, left of, right of, or in front of clips. The following sections explain how to set up automatic SMIL generation. You can edit the RealServer configuration file manually or use the Web-based RealSystem Administrator.
|
|
Note |
|---|
| The Web-based RealServer Administrator interface is not described in this document. |
The following figure illustrates automatic SMIL generation:
/smilgen/banner/, that indicates the clip requires a SMIL file that includes an ad. For example, the request URL may look like this:
<a href="http://realserver.company.com/ramgen/adtag/sports/smilgen/banner/content/video.rm">
This example URL contains these components:
The SMIL generation mount point (/smilgen/banner/) simply follows the ad serving mount point (/adgen/sports/) in the request URL.
|
|
Note |
|---|
| For more on the ad serving mount points, see "General Ad Serving". |
/smilgen/banner/ mount point causes RealServer to uses its SMIL generation plug-in to create a SMIL file for the requested clip. The RealServer configuration file defines this mount point and associates it with the SMIL generation plug-in.
/smilgen/banner/ mount point, the SMIL generation plug-in creates SMIL mark-up that lays out and times the ad and requested clip. The configuration file associates the /smilgen/banner/ mount point with layout and timing attributes. For example, it might define a banner ad 468 pixels wide by 60 pixels high that appears above the clip as it plays.
The configuration file may have additional mount points such as /smilgen/lead_in/ or /smilgen/banner_below/. Each mount point defines a different ad scenario. This lets you support any number of ad types through automatic SMIL generation.
<RealAdInsert/> tag, to the tag handler plug-in.
<RealAdInsert/> tag to contain an ad URL.
|
|
Additional Information |
|---|
| For more on the ad insertion process, see "General Ad Serving". |
You can edit the RealServer configuration file, typically named rmserver.cfg, with any text editor. After editing the file, restart RealServer to put the new parameters into effect. Before editing the configuration file, make sure you understand the file's XML-based syntax.
|
|
Additional Information |
|---|
| See the configuration file appendixes in RealServer Administration Guide. |
You set up each SMIL generation mount point within the configuration file's FSMount section. Each mount point is defined between <List Name="FSMount"> and that tag's corresponding </List> tag. The following example shows two mount points defined for banner ads and lead-in ads respectively:
<List Name="FSMount">
<!-- SMIL generation plug-in for banner ads -->
<List Name="Banner SMIL Generation">
<Var ShortName="pn-smilgen"/>
<Var MountPoint="/smilgen/banner/"/>
<Var BaseMountPoint="/"/>
<Var AdType="Banner"/>
<Var Layout="AdTop"/>
<Var AdWidth="468"/>
<Var AdHeight="60"/>
<Var OuterPadding="5"/>
<Var InnerPadding="10"/>
<Var BGColor="black"/>
</List>
<!-- SMIL generation plug-in for lead-in ads -->
<List Name="Lead-in SMIL Generation">
<Var ShortName="pn-smilgen"/>
<Var MountPoint="/smilgen/leadin/"/>
<Var BaseMountPoint="/"/>
<Var AdType="Leadin"/>
<Var Layout="AdCenter"/>
<Var AdWidth="200"/>
<Var AdHeight="200"/>
<Var OuterPadding="5"/>
<Var BGColor="red"/>
<Var EnablePlaylist="True"/>
</List>
</List>
The user-defined list name ("Banner SMIL Generation" and "Lead-in SMIL Generation" in the examples above) should identify the purpose of the mount point.
RealServer identifies which plug-in to use through this encoded short name. Use the predefined SMIL generation plug-in short name: pn-smilgen.
The mount point defines the URL component that causes RealServer to pass the requested file to the SMIL generation plug-in. Define the mount point between forward slashes, such as /smilgen/banner/. The mount point cannot include spaces. The mount point follows the tag handler mount point in request URLs such as this:
<a href="http://realserver.company.com/ramgen/adtag/sports/smilgen/banner/video.rm">
When this URL is requested, RealServer turns the file over to the SMIL generation plug-in based on the /smilgen/banner/ mount point.
The SMIL generation mount point must be relative to the tag handler plug-in's BaseMountPoint variable. For example, if the tag handler has this base mount point:
<Var BaseMountPoint="/local/"/>
the SMIL generation plug-in has a mount point like this:
<Var MountPoint="/local/smilgen/banner/"/>
Or if the tag handler has this base mount point:
<Var BaseMountPoint="/"/>
the SMIL generation plug-in uses a mount point like this:
<Var MountPoint="/smilgen/banner/"/>
The base mount point represents the actual file system mount point RealServer uses to find the requested file. For example, this variable:
<Var BaseMountPoint="/"/>
means RealServer uses the file system plug-in associated with the mount point "/" to locate the requested file. The value "/" typically indicates RealServer's default file system plug-in that locates unsecured files on local disks. So for this request:
<a href="http://realserver.company.com/ramgen/adtag/sports/smilgen/banner/video.rm">
RealServer locates the file with a UNIX path such as the following, depending on the directory path associated with the "/" mount point in the configuration file:
/realserver/content/start.smil
On Win32, the path may look like this:
G:\realserver\content\start.smil
If RealServer contains secure content, allowance is verified only on the initial request URL, not when RealServer accesses the actual file. This can create a security hole if the base mount point is "/" and secure content resides below this directory level. To prevent this, make the base mount point a directory, such as /local/, that does not lead to secure content.
This variable determines the type of ad used. It can have one of these values:
Banner |
Banner ad that appears alongside main clip. The Layout variable value should be AdTop, AdBottom, AdLeft, or AdRight. Banner is the default value that applies if you do not specify the AdType value. |
Leadin |
Ad appears before the requested clip begins playback. This ad is usually a rich media ad, such as RealVideo or RealFlash. The Layout variable valueis typically AdCenter. |
|
|
Additional Information |
|---|
| See also "Rich Media Ads". |
This variable determines the ad's location relative to the requested clip. It can have one of the following values:
AdTop |
Ad appears above the requested clip. The ad and clip are centered horizontally within the RealPlayer window. |
AdBottom |
Ad appears below the requested clip. The ad and clip are centered horizontally within the RealPlayer window. AdBottom is the default value that applies if you do not specify the Layout value. |
AdCenter |
Ad appears centered and in front of the requested clip. The ad and clip are thus centered both horizontally and vertically. In this case, the ad's AdType variable should be Leadin. |
AdLeft |
Ad appears to the left of the requested clip. The ad and clip are centered vertically within the RealPlayer window. |
AdRight |
Ad appears to the right of the requested clip. The ad and clip are centered vertically within the RealPlayer window. |
Here is an example used with a standard banner ad that appears above the requested clip:
<Var Layout="AdTop"/>
This variable must be set to the pixel width of the ad that will be used. The SMIL generation plug-in lays out the SMIL file with this value. The default value is the standard banner width of 468 pixels. The following example shows the width set to 200 pixels:
<Var AdWidth="200"/>
Set this variable to the pixel height of the ad that will be used. The default value is the standard banner height of 60 pixels. The following example shows the height set to 50 pixels:
<Var AdHeight="50"/>
The OuterPadding variable determines how many pixels of space the SMIL generation plug-in adds between the contents and the RealPlayer border. You can use any positive integer value. The default is 5 pixels. This example adds 20 pixels of outer padding:
<Var OuterPadding="20"/>
This variable determines the distance in pixels between the ad and the clip. It is ignored if the ad appears in front of the clip. You can use any positive integer value. The default is 5 pixels. This example adds 10 pixels of space between ad and clip:
<Var InnerPadding="10"/>
Suppose a banner ad appears above the clip and is wider than the clip. If the ad is 200 pixels wide, an outer padding value of 5 makes the RealPlayer window 210 pixels wide. The height of this window is the height of the ad, plus the height of the clip, plus the InnerPadding value, plus 10 pixels (5 pixels of outer padding at top and bottom).
This variable determines the background color for the RealPlayer window. Empty space around the ad and clip appear in this color. The default is black. To specify a color value, use any RGB hexadecimal value (#RRGGBB) supported by HTML, or one of the following predefined color names, listed here with their corresponding hexadecimal values:
The following example makes the background color black:
<Var BGColor="black"/>
The EnablePlaylist variable, which is False by default, determines whether the viewer has access to the RealPlayer playlist during a lead-in ad. It has no effect on banner ads. You can set this variable to True to allow the viewer to skip the lead-in ad clip:
<Var EnablePlaylist="True"/>