diff --git a/symmetric/src/docbook/administration.xml b/symmetric/src/docbook/administration.xml index 10a68ce89e..d97dd985ee 100644 --- a/symmetric/src/docbook/administration.xml +++ b/symmetric/src/docbook/administration.xml @@ -49,7 +49,7 @@ where source_table_name = 'price_changes'; SymmetricDS examines the current configuration, corresponding database triggers, and the underlying tables to determine if database triggers need created or updated. - The change activity is recorded on the table with a reason for the + The change activity is recorded on the table with a reason for the change. The following reasons for a change are possible: @@ -158,8 +158,8 @@ where source_table_name = 'price_changes';
Opening Registration - Node registration is the act of setting up a new node and - node security so that when the new node is brought online + Node registration is the act of setting up a new and + so that when the new node is brought online it is allowed to join the system. Nodes are only allowed to register if rows exist for the node and the registration_enabled flag is set to 1. If the auto.registration SymmetricDS property is set to true, then when a node attempts to register, if registration diff --git a/symmetric/src/docbook/advanced-configuration.xml b/symmetric/src/docbook/advanced-configuration.xml index d43a35aba3..64061b701a 100644 --- a/symmetric/src/docbook/advanced-configuration.xml +++ b/symmetric/src/docbook/advanced-configuration.xml @@ -14,11 +14,11 @@ After data is captured, the first event that occurs is the routing of the - captured data. Data is routed by the Route Job. It is a single background task that inserts into - data event and outgoing batch. The Route Job determines which nodes + captured . Data is routed by the Route Job. It is a single background task that inserts into + and . The Route Job determines which nodes data will be sent to, as well as how much data will be batched together for transport. When the start.route.job SymmetricDS property is set to true, the frequency that routing occurs is controlled by the job.routing.period.time.ms. Each time data is routed, the - data_ref table is updated with the id of the last contiguous data row to have been processed. This is done so the query to find + table is updated with the id of the last contiguous data row to have been processed. This is done so the query to find unrouted data is optimal. @@ -26,12 +26,14 @@ events are controlled by the Push and the Pull Jobs. When the start.pull.job SymmetricDS property is set to true, the frequency that data is pulled is controlled by the job.pull.period.time.ms. When the start.push.job SymmetricDS property is set to true, the frequency that data is pushed is controlled by the job.push.period.time.ms. Data is extracted by channel from the source database's - data table at an interval controlled by the extract_period_millis column on the channel table. The last_extract_time is - always recorded, by channel, on the node_channel_control table for the host node's id. When the Pull and Push Job run, if the extract period + table at an interval controlled by the extract_period_millis column on the + table. The last_extract_time is + always recorded, by channel, on the table for the host node's id. When the Pull and Push Job run, if the extract period has not passed according to the last extract time, then the channel will be skipped for this run. If the extract_period_millis is set to zero, data extraction will happen every time the jobs run. - SymmetricDS also provides the ability to configure windows of time when synchronization is allowed. This is done using the node group channel window + SymmetricDS also provides the ability to configure windows of time when synchronization is allowed. This is done using the + table. A list of allowed time windows can be specified for a node group and a channel. If one or more windows exist, then data will only be extracted and transported if the time of day falls within the window of time specified. The configured times are always for the target node's local time. If the start_time is greater than the end_time, then the window crosses over to the next day. @@ -39,13 +41,13 @@ All data loading may be disabled by setting the dataloader.enable property to false. This has the effect of not allowing incoming synchronizations, while allowing outgoing synchronizations. All data extractions may be disabled by setting the dataextractor.enable property to false. These properties can be controlled by inserting into the - root server's parameter table. These properties affect every channel with the exception of the 'config' channel. + root server's table. These properties affect every channel with the exception of the 'config' channel.
Multi-Tiered Synchronization - As shown previously, at times there may be + As shown previously, at times there may be scenarios where data needs to flow through multiple tiers of nodes that are organized in a tree-like network with each tier requiring a different subset of data. For example, you may have a system where the lowest tier may by a computer or device located in a store. Those devices @@ -76,13 +78,13 @@ When deploying a multi-tiered system it may be advantageous to have only one registration server, even though the parent node of a registering node could be any of a number of nodes in the system. In SymmetricDS the parent node is always the node that a child registers with. The - registration_redirect table allows a single node, usually the root server in the network, to + table allows a single node, usually the root server in the network, to redirect registering nodes to their true parents. It does so based on a mapping found in the table of the external id (registrant_external_id) to the parent's node id (registration_node_id). For example, if it is desired to have a series of regional servers that workstations at retail stores get assigned to based on their external_id, the store number, then - you might insert into registration_redirect the store number as the registrant_external_id and the node_id of + you might insert into the store number as the registrant_external_id and the node_id of the assigned region as the registration_node_id. When a workstation at the store registers, the root server send an HTTP redirect to the sync_url of the node that matches the registration_node_id. @@ -274,9 +276,9 @@ insert into sym_trigger_router (TRIGGER_ID,ROUTER_ID,INITIAL_LOAD_ORDER, ]]> To publish JMS messages during routing the same pattern is valid, with the exception that the extension point would be the XmlPublisherDataRouter and the router - would be configured by setting the router_type of a router to the Spring bean - name of the registered extension point. Of course, the router would need to be linked through trigger routers - to each trigger table that needs published. + would be configured by setting the router_type of a to the Spring bean + name of the registered extension point. Of course, the router would need to be linked through s + to each table that needs published.
@@ -287,19 +289,19 @@ insert into sym_trigger_router (TRIGGER_ID,ROUTER_ID,INITIAL_LOAD_ORDER, delete statements by the Purge Job. Only data that has been successfully synchronized will be purged. Purged tables include: - DATA + - DATA_EVENT + - OUTGOING_BATCH + - INCOMING_BATCH + - STATISTIC + The purge job is enabled by the start.purge.job SymmetricDS property. The job runs periodically according to the diff --git a/symmetric/src/docbook/basic-configuration.xml b/symmetric/src/docbook/basic-configuration.xml index f5e40b4b29..a5768f61f4 100644 --- a/symmetric/src/docbook/basic-configuration.xml +++ b/symmetric/src/docbook/basic-configuration.xml @@ -12,22 +12,22 @@ automatically (auto creation can be disabled). Basic configuration is described by inserting into the following tables: - Node Group - specify the tiers that exist in a topology + - specify the tiers that exist in a topology - Node Group Link - two nodes groups are linked together for synchronization + - two nodes groups are linked together for synchronization - Channel - grouping to control synchronizations + - grouping to control synchronizations - Trigger - specify tables, channels and conditions for which changes in the database should be captured + - specify tables, channels, and conditions for which changes in the database should be captured - Router - specify the node group link to be used for synchronization, along with other routing details + - specify the to be used for synchronization, along with other routing details - TriggerRouter - map routers to triggers + - map routers triggers During start up, triggers are verified against the database, and database triggers diff --git a/symmetric/src/main/torque/doc/docbook/table.vm b/symmetric/src/main/torque/doc/docbook/table.vm index 43bc3569ec..b5e110d52e 100644 --- a/symmetric/src/main/torque/doc/docbook/table.vm +++ b/symmetric/src/main/torque/doc/docbook/table.vm @@ -15,7 +15,7 @@ ## specific language governing permissions and limitations ## under the License. -
+
$table.Name.toUpperCase() $table.Description