Differences between revisions 2 and 4 (spanning 2 versions)
Revision 2 as of 2007-02-01 01:35:07
Size: 659
Editor: FayezMoussa
Comment:
Revision 4 as of 2007-02-01 02:10:09
Size: 1621
Editor: JessicaMayo
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
The point of this is to be able to force reporting programs to use an alternate copy of the data that will possibly be on a different server/drive. This will help with load balancing (hopefully) ^_^; The point of this is to be able to force reporting programs to use an alternate copy of the data that will possibly be on a different server/drive. This will help with load balancing (hopefully)
Line 7: Line 7:
We should ensure that putconts, putbucs and cc_lock return fatal errors if file was opened in $CCREPDIR. adm directory files should always open in $CCDIR, company directory files should conditionally open in $CCREPDIR
Line 9: Line 9:
We should ensure that putcont, putbuc and cc_lock return fatal errors if file was opened in $CCREPDIR.
Line 10: Line 11:

''' $CCREPDIR never used for files in adm '''

=== programs affected ===
Line 13: Line 18:
=== $CCREPDIR never used for files in adm === lstr programs should use $CCDIR by default, as for other programs (transaction entry, etc), but salstr and trlstr should probably use the reporting directory ($CCREPDIR).

=== other programs ===

We will benefit from having a deamon that tails dblog.dat and copies all changes from $CCDIR to $CCREPDIR for the company/companies specified. This will ensure that updates make it into the reporting company in a timely fashion.
This program will also have to be responsible for updating indexes in $CCREPDIR.
Ideally this program should be able to be run multiple times against multiple reporting copies.

Where the reporting directory is being used as a "live" backup of data for redundancy and failover, adm and any other directories will need to be copied on a periodic basis also, perhaps by a utility like rsync.

$CCREPDIR

Have some sort of flag that will identify if the program will use $CCREPDIR directory instead of $CCDIR directory.

The point of this is to be able to force reporting programs to use an alternate copy of the data that will possibly be on a different server/drive. This will help with load balancing (hopefully)

adm directory files should always open in $CCDIR, company directory files should conditionally open in $CCREPDIR

We should ensure that putcont, putbuc and cc_lock return fatal errors if file was opened in $CCREPDIR. However, must always allow putbucs into adm dir.

$CCREPDIR never used for files in adm

programs affected

Need to come up with list of rep programs that change data, as by default rep programs will now use $CCREPDIR.

lstr programs should use $CCDIR by default, as for other programs (transaction entry, etc), but salstr and trlstr should probably use the reporting directory ($CCREPDIR).

other programs

We will benefit from having a deamon that tails dblog.dat and copies all changes from $CCDIR to $CCREPDIR for the company/companies specified. This will ensure that updates make it into the reporting company in a timely fashion. This program will also have to be responsible for updating indexes in $CCREPDIR. Ideally this program should be able to be run multiple times against multiple reporting copies.

Where the reporting directory is being used as a "live" backup of data for redundancy and failover, adm and any other directories will need to be copied on a periodic basis also, perhaps by a utility like rsync.

CCRepDir (last edited 2013-09-18 06:09:34 by localhost)