|
Size: 2206
Comment:
|
Size: 6552
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| Sends data between two sites, usually a branch computer and the HO server. Polling consists of several programs working in unison to create, filter and process data to a store. The programs are controlled by commin. The parameters used with the programs are accessed/altered by comaad. | Sends data between two sites, usually a branch computer and the HO server. Polling consists of several programs working in unison to create, filter and process data to a store. The programs are controlled by {{{commin}}}. The parameters used with the programs are accessed/altered by {{{comaad}}} and {{{pollcont}}} |
| Line 4: | Line 4: |
| Polling consists of four actions: * Generate - Creation of polling files from the transaction and file maintenance files * Process - Reading data from polling files and using them to update the transaction and file maintenance files * Distribute - Taking data from one polling file and copying it to another polling file. Data is not actually leaving the computer, just copied from one folder to another * Send/Retrieve - Sending or retrieving files across the LAN/Internet The folder structure employed by polling * /u/cc/<COMPANY>/ - You should know what this does !! * <BRANCH>/ - Folder that represents the polling location <BRANCH> * send/ - Zip files waiting to be sent to the other computer * receive/ - Zip files received from the other computer * stuffed/ - Files that were downloaded, but the zip file was corrupted (aka "stuffed") * reports/ - Not quite sure what this is used for == The general process of polling is: == 1. Check for any newly received polling packages 1. Unzip the packages 1. Distribute the downloaded data to the other polling locations 1. Process the data distributed to the local polling location 1. Generate polling files that represent the latest changes made on the current host 1. Distribute the changes to the other polling locations 1. Retrieve the latest files from the store computers 1. Send the newly created polling files to the stores (in the form of a ZIP archive) 1. For each polling location, 1. Unzip the packages 1. Distribute newly downloaded data to all other polling locations 1. Process the data distributed to the local polling location == Polling programs == * commin - Performs all of the polling logic. ie. What files to send, what files to retrieve, what files go where, etc. * comaad - Adjust the location specific parameters used by commin and the various programs commin calls * pollcont - Adjust global polling settings |
|
| Line 5: | Line 36: |
| 1. Transaction or File Maintenance record is created/altered | |
| Line 7: | Line 37: |
| 1. File is filtered for certain transaction/record types | 1. File is filtered and converted into a polling file. Filtering is determined by parameters set in Generate Options of the local host's polling record 1. Polling file is filtered for certain transaction/record types before sending to peer. Filtering is determined by parameters set in the Distribute Options of the PEER's polling record |
| Line 9: | Line 40: |
| 1. Peer filters file for certain transaction/record types | 1. Peer filters file for certain transaction/record types. Filtering is determined by the Process Options in the local host's polling record |
| Line 11: | Line 42: |
| == Polling File Maintenance Records == | == File Maintenance Records == |
| Line 14: | Line 45: |
| 1. {{{XXaad}}} creates entry(s) in log.dat 1. {{{logmin}}} reads entries from log.dat and only outputs certain record types into slog.dat. Effectively, {{{logmin}}} acts as a filter. 1. slog.dat is sent to the other location 1. On the other end, {{{logmin}}} reads certain entries from slog.dat and outputs it to another file 1. On the other end, {{{XXaad}}} processes output file and applies changes. |
1. {{{XXaad}}} creates entry(s) in log.dat. 1. {{{logmin}}} reads entries from log.dat and only outputs certain record types into slog.dat. {{{logmin}}} simply acts as a filter. 1. {{{logmin}}} reads entries from slog.dat and only outputs certain record types into rslog.dat. 1. rslog.dat is sent to the other location 1. On the other computer, {{{logmin}}} reads certain entries from rslog.dat and outputs it to slog.dat 1. On the other computer, {{{XXaad}}} processes slog.dat and applies changes. |
| Line 25: | Line 57: |
| 1. On other computer, {{{reclstr}}} converts sendtrn.dat to daycomm.dat, which just a structurally the same as daytrn.dat | 1. On other computer, {{{reclstr}}} converts sendtrn.dat to daycomm.dat, which just structurally the same as daytrn.dat |
| Line 27: | Line 59: |
| == Debtor Balances == 1. {{{sdbrep}}} reads entries from debtr.dat and dumps closing balance into debbal.dat 1. debbal.dat is sent to the other computer 1. On the other computer, {{{rdbmin}}} reads in debbal.dat and updates the closing balances for debtors == Stock Counts == 1. {{{spost}}} or {{{stpost}}} places updated stock counts into stcount.dat in accordance to the option in {{{pollcont}}} 1. {{{sscrep}}} reads in stcount.dat, filters the stock counts and outputs to rstcount.dat 1. rstcount.dat is sent to the other computer 1. On the other computer, {{{rscmin}}} reads in stcount.dat and updates the stock counts in the stock file == Order Deletions and Completions == 1. {{{XXeat}}} adds entry in log.dat to denote that a Quote, Customer Order or Purchase Order has been completed 1. {{{logmin}}} reads entries from log.dat and only outputs certain record types into slog.dat. {{{logmin}}} simply acts as a filter. 1. {{{logmin}}} reads entries from slog.dat and only outputs certain record types into rslog.dat. 1. rslog.dat is sent to the other location 1. On the other end, {{{logmin}}} reads certain entries from slog.dat and outputs it to another file 1. On the other end, {{{oqdel}}} (which is {{{sieat}}}, but renamed) deletes the completed/deleted quotes and customer orders from tran.dat 1. On the other end, {{{podel}}} (which is {{{steat}}}, but renamed) deletes the completed purchase orders from tran.dat == Tenders == 1. {{{XXeat}}} adds entry in daytend.dat 1. {{{stendmin}}} reads daytend.dat, performs some record pointer conversions and outputs to sendtend.dat 1. {{{stendmin}}} reads sendtend.dat, filters the tenders and outputs to rsendtend.dat 1. rsendtend.dat is sent to the other computer 1. On the other computer, {{{stendmin}}} reads rsendtend.dat, filters the tenders and outputs to stendtend.dat 1. On the other computer, {{{stendmin}}} reads in sendtend.dat and updates tender.dat |
Polling
Sends data between two sites, usually a branch computer and the HO server. Polling consists of several programs working in unison to create, filter and process data to a store. The programs are controlled by commin. The parameters used with the programs are accessed/altered by comaad and pollcont
Polling consists of four actions:
- Generate - Creation of polling files from the transaction and file maintenance files
- Process - Reading data from polling files and using them to update the transaction and file maintenance files
- Distribute - Taking data from one polling file and copying it to another polling file. Data is not actually leaving the computer, just copied from one folder to another
- Send/Retrieve - Sending or retrieving files across the LAN/Internet
The folder structure employed by polling
/u/cc/<COMPANY>/ - You should know what this does !!
<BRANCH>/ - Folder that represents the polling location <BRANCH>
- send/ - Zip files waiting to be sent to the other computer
- receive/ - Zip files received from the other computer
- stuffed/ - Files that were downloaded, but the zip file was corrupted (aka "stuffed")
- reports/ - Not quite sure what this is used for
The general process of polling is:
- Check for any newly received polling packages
- Unzip the packages
- Distribute the downloaded data to the other polling locations
- Process the data distributed to the local polling location
- Generate polling files that represent the latest changes made on the current host
- Distribute the changes to the other polling locations
- Retrieve the latest files from the store computers
- Send the newly created polling files to the stores (in the form of a ZIP archive)
- For each polling location,
- Unzip the packages
- Distribute newly downloaded data to all other polling locations
- Process the data distributed to the local polling location
Polling programs
- commin - Performs all of the polling logic. ie. What files to send, what files to retrieve, what files go where, etc.
- comaad - Adjust the location specific parameters used by commin and the various programs commin calls
- pollcont - Adjust global polling settings
General Polling Process
- Transaction or File Maintenance record changes are saved to a file
- File is filtered and converted into a polling file. Filtering is determined by parameters set in Generate Options of the local host's polling record
- Polling file is filtered for certain transaction/record types before sending to peer. Filtering is determined by parameters set in the Distribute Options of the PEER's polling record
- File is sent to peer
- Peer filters file for certain transaction/record types. Filtering is determined by the Process Options in the local host's polling record
- Peer adds transaction/record changes into it's own database
File Maintenance Records
When a new file maintenance record is added, a copy of the record (along with some extra information) will be placed in the "logfile" (log.dat). When you delete a record, an entry in the logfile will also be created. Altering a file maintenance record will create two entries in log.dat. One will be a snapshot of the record before the change and the other will be a copy of the record after the change.
XXaad creates entry(s) in log.dat.
logmin reads entries from log.dat and only outputs certain record types into slog.dat. logmin simply acts as a filter.
logmin reads entries from slog.dat and only outputs certain record types into rslog.dat.
- rslog.dat is sent to the other location
On the other computer, logmin reads certain entries from rslog.dat and outputs it to slog.dat
On the other computer, XXaad processes slog.dat and applies changes.
Transactions
XXeat creates an entry in daytrn.dat
sen2post copies the entries from daytrn.dat, adds a bit of extra information and outputs it to sendtrn.dat
sendpost reads sendtrn.dat and outputs certain transactions to rsndtrn.dat
- rsndtrn.dat is sent to other computer
On other computer, sendpost reads in rsndtrn.dat, filters transactions and outputs to sendtrn.dat
On other computer, reclstr converts sendtrn.dat to daycomm.dat, which just structurally the same as daytrn.dat
On other computer, XXpost will now add transactions to its transaction history file
Debtor Balances
sdbrep reads entries from debtr.dat and dumps closing balance into debbal.dat
- debbal.dat is sent to the other computer
On the other computer, rdbmin reads in debbal.dat and updates the closing balances for debtors
Stock Counts
spost or stpost places updated stock counts into stcount.dat in accordance to the option in pollcont
sscrep reads in stcount.dat, filters the stock counts and outputs to rstcount.dat
- rstcount.dat is sent to the other computer
On the other computer, rscmin reads in stcount.dat and updates the stock counts in the stock file
Order Deletions and Completions
XXeat adds entry in log.dat to denote that a Quote, Customer Order or Purchase Order has been completed
logmin reads entries from log.dat and only outputs certain record types into slog.dat. logmin simply acts as a filter.
logmin reads entries from slog.dat and only outputs certain record types into rslog.dat.
- rslog.dat is sent to the other location
On the other end, logmin reads certain entries from slog.dat and outputs it to another file
On the other end, oqdel (which is sieat, but renamed) deletes the completed/deleted quotes and customer orders from tran.dat
On the other end, podel (which is steat, but renamed) deletes the completed purchase orders from tran.dat
Tenders
XXeat adds entry in daytend.dat
stendmin reads daytend.dat, performs some record pointer conversions and outputs to sendtend.dat
stendmin reads sendtend.dat, filters the tenders and outputs to rsendtend.dat
- rsendtend.dat is sent to the other computer
On the other computer, stendmin reads rsendtend.dat, filters the tenders and outputs to stendtend.dat
On the other computer, stendmin reads in sendtend.dat and updates tender.dat