Systems Administrator's Responsibilities:

Enterprise Replication adds the following responsibilities to the client's Enterprise Systems Administrator role:

  1. Replication Subscribers - The Replication Subscribers must be online on a regular basis to keep the Subscribers up to date. Where multiple subscribers exist, any inactive subscriber that is not updated on a regular basis will prevent the Purge Transaction Log (CC44) program from archiving transactions that have not been replicated to that subscriber. Consult with TECSYS Client Services about inactive or unnecessary Subscribers.

  2. Enterprise Subscriber System Clock Time - The systems administrator is responsible for ensuring that each Enterprise Subscriber system clock time is accurate.

  3. Replication Publishing - The Replication Server (RP10) must be run on a regular basis to keep the Subscribers up to date. RP10's Publish every # second until [time] on [date] option can be used to configure the replication process to run continuously.

  4. File System Capacity Planning - The Purge Transaction Log (CC44) program updates Replication Snapshots with each transaction from the live transaction log prior to archiving. The Replication Snapshot tables will grow in parallel to the live database tables. The system administrator is responsible for ensuring that sufficient space exists for the growth of Replication Snapshots. The Replication Snapshots directory (CC95/Options/Transaction Logging) is company-specific and supports UNC paths (from the server's context) to support file system balancing across multiple devices and servers.

  5. Replication Subscriber Transaction Log - Each time the Purge Transaction Log (CC44) program is started, it writes a Transaction Log command that the Replication Server (RP10) will transmit to all Subscribers instructing them to archive and purge their local live Transaction Log. The systems administrator is responsible for connecting to each subscriber system on a regular basis to remove the archive files from the Subscriber's archive directory (client\rpsnapshots). The files are named 00rptl.YYYYMMDD where YYYYMMDD is the system clock date of the transactions contained in the archive file. The most recently dated file in the directory should not be removed as it is possible that the live transaction log still contains transactions for that date. The files can be stored offline if an audit trail is required or deleted.

  6. Recode/Merge Process - Enterprise's Recode/Merge programs alter the unique record identifiers of Customers, Products, Vendors, Suppliers and General Ledger codes. Enterprise Transaction logging will capture the database changes that the recode/merge process generates. Enterprise Replication will transmit the database changes to the Subscribers – but it has no control over the data on a Subscriber system between the time Publisher's database is altered and the Subscriber is updated with those changes. The Enterprise Systems Administrator is responsible for scheduling service periods during which all Subscriber systems will be in "Service Mode" (e.g., for E-Commerce Subscribers, the Site Service Manager (EC20) should be enabled) before the recode/merge process is started and until the Replication Server (RP10) has replicated all recode/merge database changes to the Subscriber.

 
Back