Home » Dell Manuals » Servers » Dell DX6004S » Manual Viewer

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

Content Distribution

Add to My Manuals
Save this manual to your list of manuals

Page 7 highlights

Below is a figure showing multiple primary clusters rolling up to one DR cluster. In order to distinguish the streams in Primary Cluster 1 from those in Primary Cluster 2, metadata needs to be stored with each stream identifying, at a minimum, the cluster of origin. 2.4. Content Distribution An alternative use for DX Content Router replication infrastructure is to roll up or distribute content within an organization or between cooperating organizations. With a little forethought and planning when storing descriptive metadata with each stream, a very sophisticated data distribution and storage infrastructure can be created. Because you have the ability to create your own rules, a dynamic pool of data can be created and moved around with relative ease. In the example below we use a combination of mirrored and one-way replication to create a network of clusters with distinctly different data sets. The only two identical clusters are the Central Repository in Singapore and the DR Cluster in Utah. This same model could be used for roll up of major functional areas, such as Financial, Legal, Engineering, HR, etc. Copyright © 2010 Caringo, Inc. All rights reserved 3 Version 2.2 December 2010

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

Match case Limit results 1 per page

Version 2.2

December 2010

Below is a figure showing multiple primary clusters rolling up to one DR cluster. In order to

distinguish the streams in Primary Cluster 1 from those in Primary Cluster 2, metadata needs to be

stored with each stream identifying, at a minimum, the cluster of origin.

2.4. Content Distribution

An alternative use for DX Content Router replication infrastructure is to roll up or distribute content

within an organization or between cooperating organizations. With a little forethought and planning

when storing descriptive metadata with each stream, a very sophisticated data distribution and

storage infrastructure can be created. Because you have the ability to create your own rules, a

dynamic pool of data can be created and moved around with relative ease.

In the example below we use a combination of mirrored and one-way replication to create a

network of clusters with distinctly different data sets. The only two identical clusters are the Central

Repository in Singapore and the DR Cluster in Utah. This same model could be used for roll up of

major functional areas, such as Financial, Legal, Engineering, HR, etc.