Dell DX6004S DX Content Router Setup and Configuration Guide - Page 12

Copyright © 2010 Caringo, Inc.

All rights reserved

8

Version 2.2

December 2010

</rule-set>

The example above is a good starting point, but it, alone, will not perform the filtering required for

this example. In order to select the PrimaryDR cluster as the destination of some of the locally

stored streams, we want to find all streams whose content metadata contains a header called

"DX Storage-priority" whose value starts with either a "1", a "2" or one of the words "high" or

"medium". Note that the header name is not case sensitive but the actual header value with a match

expression

is

case sensitive. Here is a

select

rule that uses a filter with a

matches

() expression that

would accomplish this:

<select name="PrimaryDR">

<filter header="<storageProduct/>-priority">

matches('\s*[12].*|\s*[Hh]igh.*|\s*[Mm]edium.*')

</filter>

</select>

A

select

clause specifies a pattern for a single set of data to be retrieved by the Subscriber process

by name. The

select

can contain zero or more

filter

clauses. If there are multiple

filter

clauses,

then all of them must match a stream’s metadata before the stream is published. As in HTTP, the

order of headers within the metadata is not significant. If there are multiple headers in the stream

metadata with the given header-name, then any of them can match the given pattern in order for the

select to execute. If there are no

filter

clauses, then the select matches any and every stream, as in

the following:

<select name="SecondaryDR">

</select>

The root tag for a set of DX Content Router rules is called

rule-set

, which can contain one or more

publish

tags as shown above. The example rule set below will replicate all high and medium priority

streams to the PrimaryDR cluster and all others to the SecondaryDR cluster. It will also also send

all streams whose Content-Disposition header does not contain a file name ending with ".tmp" to the

Backup cluster.

<rule-set>

<publish>

<select name="PrimaryDR">

<filter header="<storageProduct/>-priority">

matches('\s*[12].*|\s*[Hh]igh.*|\s*[Mm]edium.*')

</filter>

</select>

<select name="SecondaryDR">

</select>

</publish>

<publish>

<select name="Backup">

<filter header="content-disposition">

not matches('.*filename\s*\=.*\.tmp.*')

</filter>

</select>

</publish>

</rule-set>

Notice that a

rule-set

can contain multiple

publish

clauses, and each

publish

clause can contain

multiple

select

clauses. The Filter Rules Engine evaluates all content elements for each publish

Section	Page
Content Router Setup and Configuration Guide	1
Table of Contents	3
Chapter 1. Introduction to DX Content Router	5
1.1. Overview of DX Content Router	5
1.2. About this Document	5
1.2.1. Audience	5
1.2.2. Scope	5
Chapter 2. Replication Topologies	6
2.1. Disaster Recovery	6
2.2. Mirrored Clusters	6
2.3. Multi-Site Disaster Recovery	6
2.4. Content Distribution	7
Chapter 3. DX Content Router Services	8
3.1. Basic Architecture	8
3.1.1. Structure of a DX Content Router Node	9
3.1.2. Publisher Service	11
3.1.2.1. Filtering UUIDs for Publication	11
3.1.2.2. Rules	13
3.1.3. Replicator Service	14
Chapter 4. Installation	15
4.1. Requirements	15
4.1.1. Operating System	15
4.1.2. 3rd Party Package Pre-requisites	15
4.1.3. Network	15
4.1.3.1. Required Communications	15
4.1.3.2. Bandwidth Requirements	15
4.1.3.3. Recommended Infrastructure	16
4.1.3.4. IP Address Configuration	16
4.2. Installing and Configuring DX Content Router Services	17
4.2.1. Installing Services	17
4.2.2. Configuring Services and Rules	17
4.3. Upgrading DX Content Router	18
4.3.1. Upgrading from 1.x	18
4.3.2. Upgrading from 2.x	18
4.4. Removing DX Content Router	18
Chapter 5. Running and Managing DX Content Router	19
5.1. Starting DX Content Router Services	19
5.2. Publisher and Replicator Shutdown	19
5.3. Customizing the Standard Rule Sets	19
5.3.1. Publish all streams on a single channel	19
5.3.2. Publish all streams on two separate channels	20
5.3.3. Publish streams with header ‘someHeaderName’ on one channel and all others except text files to a second	20
5.3.4. Complex Content Metadata Analysis	20
5.3.4.1. Filter Clause	20
5.3.4.2. Exists Clause	21
5.3.4.3. NotExists Clause	22
5.3.4.4. All Clauses	22
5.4. Using the Publisher Console	22
5.4.1. Publisher Console layout:	23
5.5. HTTP Status Reporting for Publisher and Replicator	25
5.5.1. Publisher Response	25
5.5.2. Replicator Response	26
5.5.3. Request for Source Cluster IP Addresses	27
Chapter 6. Support for Content Restoration and Fail-Over	28
6.1. Administrative Disaster Recovery	28
6.2. Content Mirroring	28
6.3. Application-Assisted Fail-Over	28
Appendix A. Content Metadata	29
A.1. System Metadata	29
A.2. Content File Server Metadata	29
A.2.1. Custom Metadata	29
Appendix B. DX Content Router Configuration	30
B.1. Publisher Configuration	30
B.2. Replicator Configuration	34
Appendix C. Enumerator API	38
C.1. Enumerator Types	38
C.2. Enumerator Start	38
C.2.1. Enumerator Start Query Arguments	39
C.2.2. Enumerator Start Response	39
C.3. Enumerator Next	40
C.3.1. Enumerator Next Query Arguments	40
C.3.2. Enumerator Next Response	41
C.4. Enumerator End	41
C.4.1. End Response	41
C.5. Enumerator Timeout	42

Dell DX6004S DX Content Router Setup and Configuration Guide - Page 12

<publish&gt

Page 12 highlights