From 99576f296765436c845acaf70e4058f8912aaad9 Mon Sep 17 00:00:00 2001 From: eegeek Date: Tue, 31 Jul 2012 14:41:35 +0000 Subject: [PATCH] 0000724 - Extensive edits to the Quick Start Tutorial, including a column match filter for routing to specific stores. --- symmetric-assemble/src/docbook/tutorial.xml | 6 ++++-- symmetric-server/src/main/deploy/samples/insert_sample.sql | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/symmetric-assemble/src/docbook/tutorial.xml b/symmetric-assemble/src/docbook/tutorial.xml index 9d18f8ae80..1f685d065d 100644 --- a/symmetric-assemble/src/docbook/tutorial.xml +++ b/symmetric-assemble/src/docbook/tutorial.xml @@ -3,8 +3,7 @@ xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:html="http://www.w3.org/1999/xhtml"> Quick Start Tutorial Now that an overview of SymmetricDS has been presented, a quick working example of SymmetricDS is in order. - This section contains a hands-on tutorial that demonstrates how to synchronize two databases with a similar schema between two nodes of SymmetricDS, each configured as - a SymmetricDS engine deployed in a single instance of SymmetricDS. This example models a retail business that has a + This section contains a hands-on tutorial that demonstrates how to synchronize two databases with a similar schema between two nodes of SymmetricDS. This example models a retail business that has a central office database (which we'll call the "root" or "corp" database) and multiple retail store databases (which we'll call the "client" or "store" database). For the tutorial, we will have only one "client" or store node, as shown in , although by the end of the tutorial you could extend the example and configure a second store, if desired. @@ -21,6 +20,9 @@ + For this tutorial, we will simplify setup slightly by having both nodes run as engines inside a single SymmetricDS instance on one server instead of two. In practice, however, in this two-tier retail example + the two nodes would likely run on completely separate servers and therefore in separate instances, not as two engines within a single instnce. + The root engine (also sometimes called the 'server' engine) captures item data changes for the client, such as item number, description, and prices by store. The client engine (a store) captures sale transaction data changes for the root, such as time of sale and items sold. The pricing information is sent diff --git a/symmetric-server/src/main/deploy/samples/insert_sample.sql b/symmetric-server/src/main/deploy/samples/insert_sample.sql index 78d9ef28e5..436823f49a 100644 --- a/symmetric-server/src/main/deploy/samples/insert_sample.sql +++ b/symmetric-server/src/main/deploy/samples/insert_sample.sql @@ -92,7 +92,7 @@ insert into sym_router values('store_2_corp', 'store', 'corp', 'default',current_timestamp, current_timestamp); insert into sym_router -(router_id,source_node_group_id,target_node_group_id,router_type,create_time,last_update_time) +(router_id,source_node_group_id,target_node_group_id,router_type,router_expression,create_time,last_update_time) values('corp_2_one_store', 'corp', 'store', 'column','STORE_ID=:EXTERNAL_ID OLD_STORE_ID=:EXTERNAL_ID',current_timestamp, current_timestamp); --