Replicator的功能

• 提供在J2EE服務(wù)器平臺(tái)上運(yùn)行的企業(yè)數(shù)據(jù)庫(kù)，J2EE/J2SE平臺(tái)上運(yùn)行的工作組數(shù)據(jù)庫(kù)與和J2SE/J2ME 平臺(tái)上的 Java－enabled移動(dòng)設(shè)備之間的數(shù)據(jù)同步功能。
• 獨(dú)立的同步平臺(tái)：100%的Java客戶(hù)與服務(wù)器組件。
• 由客戶(hù)端初始化同步進(jìn)程的數(shù)據(jù)庫(kù)到數(shù)據(jù)庫(kù)的同步雙向數(shù)據(jù)庫(kù)。
• 具有Publisher（服務(wù)器）和Subscriber（客戶(hù)）體系結(jié)構(gòu)的發(fā)布訂閱模型
• 無(wú)需安裝Daffodil DB
• Replicator工作模型
• 符合發(fā)布與訂閱

　　發(fā)布（由開(kāi)發(fā)者定義的一個(gè)或多個(gè)表的集合）和訂閱（Publisher上特定發(fā)布的一個(gè)子集）允許Publisher發(fā)布數(shù)據(jù)給一個(gè)或多個(gè)Subscribers，在那里Replication服務(wù)器在預(yù)定義的端口上扮演監(jiān)聽(tīng)者的角色并且Subscribers進(jìn)行周期性的數(shù)據(jù)同步請(qǐng)求操作。

Publisher:

• Publisher是Replicator同步網(wǎng)絡(luò)的基本構(gòu)建塊。每一個(gè)Publisher都構(gòu)成了服務(wù)器－客戶(hù)網(wǎng)絡(luò)的一部分并且被分配一個(gè)唯一的名稱(chēng)。名稱(chēng)同其他的儲(chǔ)存在Publisher數(shù)據(jù)庫(kù)中的數(shù)據(jù)也就是關(guān)于Publisher的所有相關(guān)信息一樣被存儲(chǔ)在數(shù)據(jù)庫(kù)中。

Subscriber:

• Subscribers可訂閱Publisher的發(fā)行物。
• Replicator Publisher和Replicator Subscriber負(fù)責(zé)管理數(shù)據(jù)穿過(guò)網(wǎng)絡(luò)時(shí)的同步。Subscribers和Publisher都可以由使用者的程序?qū)ο髮?shí)例來(lái)完成與數(shù)據(jù)同步有關(guān)的核心功能。Replication Server API提供調(diào)用Publisher和Subscriber的方法，這些方法能夠使Subscriber完成同步操作。

Replicator Features

• Data Synchronization between enterprise databases running on J2EE server platforms, workgroup databases running on J2EE/J2SE platforms and Java-enabled mobile devices running on J2SE/J2ME platforms
• Platform independent synchronization: 100% Java client and server components.
• Database-to-Database bidirectional data synchronization with client-side initiating the synchronization process.
• Publish and Subscribe model with a Publisher (Server) and Subscriber (Client) architecture.
• No need for Daffodil DB installation.
• Replicator working model

Conformation to Publication and Subscription

• The Publication ( collection of one or more tables defined by developers) and Subscription (a subset of a particular publication on a Publisher) allows a Publisher to publish data to one or more Subscribers where Replication server enacts the role of a listener on a pre-defined communication port and the Subscriber makes periodic requests for data synchronization operations.

Publisher

• Publishers are the basic building blocks of a Replicator's synchronization network . Each publisher forms part of a server-client network and is assigned a unique name. The name as well as the other concerned data of each publisher are stored in the publisher database i.e. all relevant information about the publishers, is stored in a database.

Subscriber

• Subscriber subscribes to Publisher's publications.
• Replicator Publisher and Replicator Subscriber are responsible for managing the synchronization of data across the network. Both the Publisher and Subscriber are objects instantiated by user applications and perform the core functions associated with the synchronization of data. The Replication Server API gives method calls to Publisher and Subscriber, which enable Subscriber to perform synchronization operations.