Difference between revisions of "Recital Replication Text Installation"
Yvonnemilne (Talk | contribs) |
Yvonnemilne (Talk | contribs) |
||
| Line 1: | Line 1: | ||
{{YLM remove peer to peer}} | {{YLM remove peer to peer}} | ||
== Replication Type == | == Replication Type == | ||
| − | The first thing you must specify is what type of Replication Service you will be running on each server | + | The first thing you must specify is what type of Replication Service you will be running on each server. |
| − | [1] '''Slave''' - Select this type if this system will be a slave subscriber | + | [1] '''Slave''' - Select this type if this system will be a slave subscriber. There can be many slave subscribers but updates will only be performed from data published by the replication service. |
| − | [2] '''Master''' - Select this type if this system will be the master publisher | + | [2] '''Master''' - Select this type if this system will be the master publisher. There can be only one master publisher and only updates on this system will be published for replication. |
| − | + | ||
| − | + | ||
| Line 35: | Line 33: | ||
<code>Publication ID [1] :</code> | <code>Publication ID [1] :</code> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Modifying installed values == | == Modifying installed values == | ||
You can modify the values configured during installation by the following ways; | You can modify the values configured during installation by the following ways; | ||
| − | |||
=== dbinstall rrs === | === dbinstall rrs === | ||
| Line 124: | Line 91: | ||
== Replication Database == | == Replication Database == | ||
| − | During the installation process a database called ''replication'' will be created. A table called queue will also be created in the replication database | + | During the installation process a database called ''replication'' will be created. A table called queue will also be created in the replication database. |
Revision as of 15:23, 11 March 2010
Template:YLM remove peer to peer
Contents
Replication Type
The first thing you must specify is what type of Replication Service you will be running on each server.
[1] Slave - Select this type if this system will be a slave subscriber. There can be many slave subscribers but updates will only be performed from data published by the replication service.
[2] Master - Select this type if this system will be the master publisher. There can be only one master publisher and only updates on this system will be published for replication.
Please choose an option [1] :
Slave
Publisher
Specify the node name or IP Address of the Publisher that this slave will subscribe to. This should be the system that the Master replication service was installed on.
Publisher [localhost] :
Delay
Specify the delay time in seconds that the service will pause between checking with the publication service.
Delay [60] :
Master
Publication ID
The publication ID is a unique number that is used to differentiate each system in the replication service. For a master publisher it should be set to a value of 1. This ID should not be changed once the replication service has been started on the system.
Publication ID [1] :
Modifying installed values
You can modify the values configured during installation by the following ways;
dbinstall rrs
Executing this command at the operating system prompt will allow you to reconfigure the replication service.
Configuration files
You can edit the configuration files and change the values manually. The following table contains all the variables defined during the installation process. The configuration file are stored in the conf directory which is in the root recital installation directory.
| Variable Name | Default Value | Configuration File |
|---|---|---|
| DB_PUBLICATIONID | 0 | recital.conf |
| DB_REPDIR | replication | recital.conf |
| DB_REPLOG | TRUE | recital.conf |
| DB_REPTYPE | slave | recital.conf |
| DB_PUBLISHER | localhost | recital.conf |
| DB_REPDELAY | 60 | recital.conf |
| DB_PEERS | localhost | recital.conf |
DB_REPDIR
The variable DB_REPDIR is set to path that the replication database is located by default. This path is used to store temporary files used by the replication service. Each Recital user and all replication service must have the permission to create and delete files from this directory.
For better performance this directory can be configured as an in-memory file system
DB_REPLOG
The variable DB_REPLOG is used to enable or disable logging on the replication services. A value of TRUE will enable logging and a value of FALSE will disable logging. By default log files will be stored in the log and/or debug directory located under to root recital installation directory.
Replication Database
During the installation process a database called replication will be created. A table called queue will also be created in the replication database.
| Table Name | Replication Type | Service |
|---|---|---|
| queue | All | All |
| subscribers | Master Salve | Publisher |
| peers | Peer to Peer | Master publisher |
| pub_queue | Peer to Peer | Master publisher |
| conflict_queue | Peer to Peer | Master publisher |
