Chapter 3. Configuration
This chapter deals with getting up and running and connected to the database.
3.1. Configuration Files
3.1.1. Config.ini
The Config.ini file contains configuration information for REPLICATION HOME, TRANSACTION LOG FILE, SHADOW TABLE, TRIGGER, SEQUENCE and INDEX prefixes. The details of each are given below. On linux systems, this and all other configuration files can be found in /etc/dbreplicator.
REPLICATIONHOMEThis is a path, that describes where the transaction logs, error logs and sync files are stored. The sync files are XML files that are created during all forms of replication (snapshot,synchronize,push,pull) and can become quite large, depending upon the size of your database or the amount of data in a particular synchronization session. All errors are also logged here, so be sure to place this on a partition with enough space to allow for large files.
The variable is set to 'Default' by default, and this will store all of these files in the user's home directory
TRANSACTIONDETAILSet to "true", this will list transactions in detail in the transaction log file. Set to "false"(the default), this will only list a summary of the number of updates, inserts and deletes during a session.
ShadowTablePrefixBy default set to "REP_SHADOW", this specifies the prefix used when creating the shadow tables. Don't change it after setting up the publication/subscription, as it will prevent the system from finding the shadow tables. You can change it before creating the publication/subscription, and it will be used when creating the shadow tables.
TR[UID]_PrefixThese three variables, TRU_Prefix, TRI_Prefix and TRD_Prefix specify the prefix to use when setting up the trigger names that are applied to the tables which are replicated. For instance, if you are replicating a customer table, the triggers by default will be named TRU_customer, TRI_customer and TRD_customer.
Seq_PrefixThe suffix to use when creating the sequence for the table sync id.
3.1.2. log4j.properties
This file is automatically created if not in the directory in which replictor is started. This file can be used to set the debug level of dbreplicator, which an be any of the following:
Warn: Displays those messages that indicate a potentially problematic situation for the administrator
Error: These events might allow the application to continue to run, but the administrator might like to know about them.
Fatal: Very severe problems that will most likely cause dbreplicator to abort (stop execution).
Debug: Fine-grained information regarding the running of dbreplicator
Info: Informational messages that highlight the process of dbreplicator at a high level.
Off: Turn off all but system crashes
All: Enable ALL logging facilities.
Format of this file is:
log4j.rootCategory=off
#log4j.rootCategory=DEBUG,A1
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%d{ABSOLUTE} %p [%c{i}] [%M %L] %m%n
This leaves all logging off by default, but simply uncommenting the second line and commenting the first turns it on. This logs all output to the console using the 'A1' appender with the specified format.
The console appender is the default, but logging can be enabled to file, database, smtp server and much more using this logging method. See the apache log4j project at http://logging.apache.org/log4j for more information.
3.1.3. Encodeconfig.ini
Special Character HandlingSpecial characters with ASCII value less than 32 are not parseable and can create problems for dbreplicator. This can be dealt with using the EncodeConfig.ini file. Each table has its own line, and the columns within that table that are to be treated specially are listed as comma-separated values after that table. All values are in CAPS.
