Difference between revisions of "Recital Replication Graphical Installation"

From Recital Documentation Wiki
Jump to: navigation, search
 
(20 intermediate revisions by 2 users not shown)
Line 5: Line 5:
  
  
−
The first thing you must specify is what type of Replication Service you will be running on each server. You may install the same types on different servers depending of which type of replication service you are configuring, MSR or PPR.  
+
The first thing you must specify is what type of Replication Service you will be running on each server.
  
−
* '''Slave''' - Select this type if this system will be a slave subscriber in a MSR configuration. There can be many slave subscribers but updates will only be performed from data published by the replication service.
+
* '''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.
−
* '''Master''' - Select this type if this system will be the master publisher in a MSR configuration. There can be only one master publisher and only updates on this system will be published for replication.
+
* '''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.
−
* '''Peer''' - Select this type if you are setting up a PPR configuration. In a PPR configuration all systems must be set to this type. This system will be able to publish all updates and subscribe to published updates from other systems.
+
  
  
 
== Slave ==
 
== Slave ==
 +
  
 
[[Image:RRS_Install_Replication_Slave_Options.jpg]]
 
[[Image:RRS_Install_Replication_Slave_Options.jpg]]
Line 24: Line 24:
  
 
== Master  ==
 
== Master  ==
 +
  
 
[[Image:RRS_Install_Replication_Master_Publication_ID.jpg]]
 
[[Image:RRS_Install_Replication_Master_Publication_ID.jpg]]
Line 30: Line 31:
 
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.
 
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.
  
−
 
−
== Peer ==
 
−
 
−
[[Image:RRS_Install_Replication_Peer_Options.jpg]]
 
−
 
−
=== Publication ID ===
 
−
The publication ID is a unique number that is used to differentiate each system in the replication service. The value must be set to a value greater than 1 and must not be the same as any other publication ID. This ID should not be changed once the replication service has been started on the system.
 
−
 
−
 
−
=== Publisher ===
 
−
Specify the node name or IP Address of the Publisher that you want to subscribe with. You can specify the node name or IP Address of the system you are currently installing on. Doing this will make this system the master publisher and you will need to provide a list of peers.
 
−
 
−
 
−
=== Delay ===
 
−
Specify the delay time in seconds that the service will pause between checking with the publication service. If you have specified this system as the publisher, then it will also be used by the publication service.
 
−
 
−
[[Image:RRS_Install_Replication_Peers.jpg]]
 
−
 
−
=== Replication Peers ===
 
−
This option will be displayed if you have specified that this system will also be the publisher. Please specify a comma separated list of the node names or IP Addresses of the Peers that will be published. You can specify the system you are installing on if you wish to publish it.
 
  
 
== Modifying installed values ==
 
== Modifying installed values ==
Line 60: Line 41:
 
=== Configuration files ===
 
=== 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.
 
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.
 +
  
 
{| class="bordered"  
 
{| class="bordered"  
Line 78: Line 60:
 
| DB_REPLOG
 
| DB_REPLOG
 
| TRUE
 
| TRUE
−
| dbservice.conf
+
| recital.conf
 
|-
 
|-
 
| DB_REPTYPE
 
| DB_REPTYPE
 
| slave
 
| slave
−
| dbservice.conf
+
| recital.conf
 
|-
 
|-
 
| DB_PUBLISHER
 
| DB_PUBLISHER
 
| localhost
 
| localhost
−
| dbservice.conf
+
| recital.conf
 
|-
 
|-
 
| DB_REPDELAY
 
| DB_REPDELAY
 
| 60
 
| 60
−
| dbservice.conf
+
| recital.conf
 
|-
 
|-
−
| DB_PEERS
 
−
| localhost
 
−
| dbservice.conf
 
 
|}
 
|}
 
<br>
 
<br>
−
 
−
=== 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 [http://www.recitalsoftware.com/index.php?option=com_content&view=article&id=274:howto-setup-in-memory-file-system-for-temporary-files&catid=51:blog-recital&Itemid=59 in-memory file system]
 
  
 
=== DB_REPLOG ===
 
=== 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.
 
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 ==
 
== 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. If this system is the master publisher in a peer to peer configuration additional tables describe below will be created.
+
During the installation process a database called ''replication'' will be created. A table called ''queue'' will also be created in the replication database. If this system is the master publisher a table called ''subscribers'' will be created.
−
 
+
−
{| class="bordered"
+
−
|+ Replication Tables
+
−
|-
+
−
! Table Name
+
−
! Replication Type
+
−
! Service
+
−
|-
+
−
| queue
+
−
| All
+
−
| All
+
−
 
+
−
|-
+
−
| peers
+
−
| Peer to Peer
+
−
| Master publisher
+
−
 
+
−
|-
+
−
| pub_queue
+
−
| Peer to Peer
+
−
| Master publisher
+
−
 
+
−
|-
+
−
| conflict_queue
+
−
| Peer to Peer
+
−
| Master publisher
+
−
 
+
−
|}
+
−
 
+
−
<br>
+
  
 
[[Category:RRS Installation]]
 
[[Category:RRS Installation]]

Latest revision as of 14:41, 8 June 2010

Replication Type

RRS Install Replication Type.gif


The first thing you must specify is what type of Replication Service you will be running on each server.

  • 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.
  • 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.


Slave

RRS Install Replication Slave Options.jpg

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.

Delay

Specify the delay time in seconds that the service will pause between checking with the publication service.


Master

RRS Install Replication Master Publication ID.jpg

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.


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.


Configuration variables
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_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. If this system is the master publisher a table called subscribers will be created.

Retrieved from "https://www.recitalsoftware.com/wiki/index.php?title=Recital_Replication_Graphical_Installation&oldid=14680"