Streaming Media Supplement sa2150 and sa2250

71
Chapter 7 Configuring Media-IXT for RealNetworks
Configuring live passthrough in a reverse proxy deployment
In a reverse proxy deployment, live passthrough has the same requirement as proxy caching of on-demand
content: each origin RealServer for which Media-IXT provides reverse proxy must have its own RTSP rule in
the remap.config file.
See “Configuring reverse proxy caching for RealNetworks” on page 66.
Configuring hierarchical live splitting for RealNetworks
The RealProxy component of Media-IXT splits a single live stream from the origin RealServer into multiple
live streams to client RealPlayers. Media-IXT does not log live requests, because RealProxy bypasses Media-
IXT entirely for live requests.
To configure Media-IXT for hierarchical live splitting of RealNetworks, just configure Media-IXT for
hierarchical proxy caching. See “Configuring hierarchical proxy caching for RealNetworks” on page 68. If
your deployment involves reverse proxy, also see “Configuring reverse proxy caching for RealNetworks” on
page 66.
Hierarchical live splitting in a forward proxy deployment requires no special configuration, unless you need to
use TCP rather than UDP as the underlying transport protocol for live splitting.
Another special case is live splitting using multicast between Media-IXT and RealPlayer clients. See “About
using multicast between Media-IXT and RealPlayer clients” on page 27.
Configuring selective caching for RealNetworks
Using selective caching, you specify criteria to determine whether to proxy certain content or not, and whether
to cache certain content or not.
When content is not proxyable, Media-IXT denies the client connection, with an appropriate message to the
client (if possible).
When content is not cacheable, Media-IXT goes into passthrough mode and proxies, but does not cache, the
content.
See the HP Cache Server Appliance Administrator Guide for more information about selective caching.
Two configuration files control selective caching:
• cache.config controls cacheability
• filter.config controls proxyability
You must edit cache.config and filter.config manually, adding selective caching rules to the files.
You can, optionally, add an RNI or QT tag to any selective caching rule. This permits you to apply one rule to
QuickTime content and another for RealNetworks content. The format for the tag is to add tag= to the end of
the rule, followed by the tag value of RNI or QT. See the HP Cache Server Appliance Administrator Guide for
details how rules are applied in situations where there is no tag added to a rule, or when conflicting rules apply
to the same request.
The kinds of selective caching rules you can write for RealNetworks and QuickTime differ from those you can
write for WMT. For RealNetworks and QuickTime, always use hostnames (in Fully Qualified Domain Name
form), not IP addresses, in selective caching rules.
After you modify the cache.config or filter.config, tell Media-IXT to re-read its configuration files.
From Media-IXT’s bin directory, run the command:
./traffic_line -x
This section provides an overview of selective caching with an emphasis on RealNetworks-specific issues that
do not appear in the HP Cache Server Appliance Administrator Guide.