Cascading Mesh Replication Configuration
=========================================

This directory contains sample configuration files
for the Cascading Mesh Replication Configuration blog
post.

These configuration files are designed to be run on
the same host. They can easily be adapted to run on
separate hosts by adding host names to the InetAddr
entries in the replication destinations.

The instances in each tier are as follows:

IncomingMessages

 * Incoming-A
 * Incoming-B

LiveProdSubscriptions

 * Live-A
 * Live-B

DevUAT

 * Dev-A
 * Dev-B

ArchiveAudit

 * Arch-A
 * Arch-B

Suggestions for Testing
--------------------------

To test the mesh, create a publisher using an HAClient
that can fail over between Incoming-A (port 9001) and
Incoming-B (port 9002). This publisher should publish
JSON messages (on any topic name).

Create a subscriber using an HAClient that can fail
over between Arch-A (port 9301) and Arch-B (port 9302).

Try stopping and starting various AMPS instances in
the mesh, and validate that as long as at least
one instance in each tier is available, all
messages correctly reach the ArchiveAudit tier.
