Dell DX6012S Installatie- en configuratiehandleiding - Pagina 12

Blader online of download pdf Installatie- en configuratiehandleiding voor {categorie_naam} Dell DX6012S. Dell DX6012S 43 pagina's. Rack installation instructions — static rails
Ook voor Dell DX6012S: Aanvullende handleiding (4 pagina's), Instructies voor installatie van hardware (2 pagina's), Gebruikershandleiding (46 pagina's), Installatie- en configuratiehandleiding (35 pagina's), Aan de slag handleiding (28 pagina's), Kennisgeving (28 pagina's), Kennisgeving (20 pagina's), Overzicht (19 pagina's), Configuratiehandleiding (9 pagina's), Configuratiehandleiding (9 pagina's), Release Release (8 pagina's), Configuratiehandleiding (7 pagina's), Release Release (6 pagina's), Release Release (5 pagina's), Release-opmerkingen (5 pagina's), Aan de slag handleiding (47 pagina's), Installatie (2 pagina's), Installatie rek (2 pagina's)

</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:

<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>

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>

</select>

</select>

</publish>

</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

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

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

</filter>

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

</filter>

Version 2.2

December 2010