Replication formula working if user initiates replication manually from server to server?

HCL Domino Domino Forum
1

Hello

The situation is like this:

A replica is located on two servers: Server A and server B. On server A, status of documents within the replica will be changed. As long as documents have status e.g. “draft”, they are not replicated to server B (which is correct and is performed in the way that server B does not have access to documents with status “draft” on the replica on server A. Pull-push is enabled between both servers, initiated by server A).

Now, there is the need that responsible persons initiate a replication manually (means, right-clicking on the replica-icon on the Notes client, choose “replicate”, select server B, and then “OK”) because of documents changed to status e.g. “published” needs to be available on the replica of server B immediately, at precise point in time (and so can not be performed by the scheduled replication).

This results in that documents of the replica of server A with status “draft” are replicated to server B, too, which isn´t good.

We are thinking about implementing a replication formula within the replica of server B which will perform that no documents with stauts “draft” will be received from the replica on server A.

Now the questions: does this replication formula takes effect when users will replicate manually (as described above), too?

Thx

Mike

2

Subject: Replication formula working if user initiates replication manually from server to server?

Mike

The issue here is that when the users use their client to replicate the databases between the servers it uses their creditials. It will also cause extra network traffic because it comes from server B to their client & then up to server A

But to answer your question

  1. If you change the replication formula on Server B to not accept “draft” documents from Any Server, that should work for the clients

  2. It might be better to have something smarter which will allow the submission of a server taks to replicate the databases at server level.

  3. Another posibility to have reader fields or hide when, and in there you can set hide when Status = Draft & @Username = Server B that why no matter who replicates with server B it will not see the draft docs

I hope this helps, if not I am sure someone else with think of other ways