Tasks Performed by RP10:

Once the Replication Server (RP10) is started, it will cycle the specified Subscriber or All Subscribers (depending on the setting in RP10), and will skip any Subscriber that is not flagged as Active in Maintain Replication Subscribers (RP01) or has Service Locked due to a failure.

When a Subscriber is selected for publishing, the Replication Server performs the following tasks:

  1. Lock the Subscriber.

  2. Connect to the Subscriber using the addressing information on file in RP01 to confirm that it is online. If a connection to the Subscriber cannot be established within three attempts, or if communication fails at any point once publishing has started, the Replication Server will skip the Subscriber until the next publishing cycle.

  3. Request the status of the Subscriber.

  4. Verify that the Publisher and Subscriber are in sync with each other. If one or the other has failed and is recovered from backup media, the Replication Server detects that they are no longer in sync and issues a service lock to the Subscriber. For an E-Commerce Replicated Web Site, a service lock will result in the web site being put on Site Service Mode (EC20). If the Replication Server determines that it was the Publisher that was restored then it will request from the Subscriber any transactions that have not sent to the publisher. The Subscriber will be deactivated and service locked; the Subscriber will have to be re-created. Contact TECSYS SMB Support for recovery options before starting the Replication Server.

  5. Import transactions from the Subscriber. As transactions are imported, the Publishing Log will be updated periodically with a running total of the number of insert, update and delete transactions that have been received as well as the time stamp of the last transaction. Once all transactions have been imported from the Subscriber, the Publishing Log will be updated with the total number of insert, update and delete transactions that were imported from the Subscriber.

  6. Export transactions to the Subscriber. If the Replication Server is configured to 'Publish Once', then exporting will continue until all transactions awaiting export to the Subscriber when the publishing cycle started will be exported. If the Replication Server is configured to 'Publish every # seconds Until [time] on [date]' then a maximum of 5,000 transactions will be exported during a single publishing cycle.

    • After 5,000 transactions are exported, RP10 pauses to import any transactions from the Subscriber that have just come in. When the import is complete, the Replication Server resumes exporting transactions.

    As transactions are exported, the Publishing Log will be updated periodically with a running total of the number of insert, update and delete transactions that have been exported so far, as well as the time stamp of the last transaction. The time stamp of the last transaction exported can be used to gauge how up-to-date the subscriber is in comparison to new transactions created on the Publisher. Once all transactions have been exported, the Publishing Log will be updated with the total number of insert, update and delete transactions that were exported to the Subscriber.

  7. Unlock the Subscriber.

Once these tasks have been completed, the Replication Server with either continue with the next Subscriber, wait until the next publishing start time, or stop.

 
Back