Dell DX6000 Manuel d'installation et de configuration - Page 11

Parcourez en ligne ou téléchargez le pdf Manuel d'installation et de configuration pour {nom_de_la_catégorie} Dell DX6000. Dell DX6000 43 pages. Rack installation instructions — static rails
Également pour Dell DX6000 : Manuel complémentaire (4 pages), Instructions pour l'installation du matériel (2 pages), Manuel de l'utilisateur (46 pages), Manuel d'installation et de configuration (35 pages), Manuel de démarrage (28 pages), Avis (28 pages), Avis (20 pages), Vue d'ensemble (19 pages), Manuel de configuration (9 pages), Manuel de configuration (9 pages), Note de mise à jour (8 pages), Manuel de référence (12 pages), Manuel de configuration (7 pages), Note de mise à jour (6 pages), Note de mise à jour (5 pages), Notes de mise à jour (5 pages), Instructions d'installation (2 pages), Instructions d'installation (2 pages)

The two optional DX Content Router services are designed and deployed as independent processes

running on a server. We discuss each of these services in more detail in the following sections.

3.1.2. Publisher Service

The Publisher service collects a comprehensive list of all the UUIDs stored in the cluster (as well as

those that have been deleted), filters those UUIDs, and publishes the resulting lists of UUIDs to one

or more remote Subscribers. The Publisher consists of several subcomponents:

1. Simple HTTP server

2. Attached data store

3. Filter Rules Engine

3.1.2.1. Filtering UUIDs for Publication

The Publisher traverses the list of UUIDs and evaluates one or more existence validations or simple

filter expressions against the values of certain headers in the metadata. A set of matching rules can

be configured by the administrator that will determine the topology of the intercluster network. These

rules are specified using an XML syntax, the full definition of which can be found below.

By way of an example, suppose we want to configure our local cluster to remotely replicate all

high and medium priority streams to a primary disaster recovery site, while all other streams get

replicated to a secondary DR site. The General XML rule structure to do this might look like this:

<rule-set>

</publish>

Version 2.2

December 2010