Select Copy Access Control List to copy the list from the source server to the destination server

9. Click on OK.

10.Enter your password, if prompted, and click on OK.

The database will then be replicated to the spoke server where it can be added to the workspace by using File -> Database -> Open..., selecting the replica database, and then clicking on the Add Icon on the Open Database screen to add the icon to the workspace. Then click on Done.

If you have Stack Replica Icons selected from the View pull-down menu on the Notes Workspace and you open the replicated version that is on the hub server’s Workspace, Lotus Notes will stack that icon onto the local server icon. (This will only work if you click on the replicated version.)

Clicking on the downward arrow that’s present on the icon itself will enable you to select which version of the database you want to work with.

The prerequisites for replication are now in place:

1. Connection document on one of the servers 2. Authorization for creating replicas

3. Creating the new replica

The databases(s) can now be replicated according to the schedule in the Connection document. To replicate outside of this schedule or to force unscheduled replication, you can select File -> Replication -> Replicate....

5.4 Selective Replication

Selective replication formulas establish a set of criteria for a replicated document.

For example, a replication formula can instruct the server to replicate only documents from a certain person, about a certain topic, or in a particular view or folder.

Database managers with authority to create replicas on other servers can centrally administer those replicas. (See 5.3.3, “Required Authorizations in Server Document” on page 133.)

It is important to remember that database managers of replicas on other servers can at any time bypass any replication settings that were defined centrally.

There are three steps that need to be completed for centralized replica administration. They are:

1. Select a destination/source server combination.

2. Specify the documents a replica can receive.

3. Select the database features that replicas can receive.

Each one of these three points is discussed here:

1. Select a destination/source server combination:

a. Right-click on the Database icon, and select Replication Settings.

b. On the Replication Setting screen, click on the Advanced icon. A dialog box similar to the one in Figure 118 will be displayed.

c. In the When computer field, enter the name of the server where the replica will be. If you can't find the server that you want from the pull-down for this field, click on the Computer icon on the far right-hand side of the field. From the Servers screen that appears, either type or select the name of the server you want. Click on OK to return to the Replication Settings dialog box.

d. In the Receives from field, either select the source server from the pull-down, or click on the computer icon on the far right-hand side to either select or type the name of the server that you want.

Make sure that you have the source and destination servers specified in the correct order. The When computer server is the one which will receive the new replica and, perhaps, a subset of the information. The Receives from server is the one which stores the entire contents of the database, and it is also the server from which all other replicas of this database are administered.

Figure 118 shows the advanced settings for a new replica of a database that will be created on the destination server, noteserv/ibm and

administered centrally from the source server, itsosmp/itso.

See step 2 on page 138 for information on how to Replicate a subset of documents and how to Select by formula.

See step 3 on page 139 for information on the Replicate incoming section of the dialog box.

Figure 118. Advanced Settings for Replication

e. Select Fields to select the specific fields that the replica will receive. Click on the Define button to select whether you want to replicate All Fields or Custom. If Custom is selected, you can choose a subset of fields to replicate. See Figure 119 for an example of the list of fields you can choose to selectively replicate.

Figure 119. Replicate Selected Fields

Specify the documents that a replica can receive.

There are three main reasons why you may want to define only a subset of documents to be replicated:

• To save disk space on destination servers

• To save on time (and, therefore, cost) associated with replicating a database

• To meet the requirement for making certain views and folders available at the destination server

2. To define a subset of documents, follow the steps below:

a. Right-click on the Database icon, and select Replication Settings....

b. On the Replication Settings screen, click on the Advanced icon and check Replicate a subset of documents.

c. If you want the destination server to receive only certain folders and/or views, then select the ones that apply from the list that is displayed. The If defining fields to replicate for the Public Name & Address book, you can select a third option - Minimal Address Book - which will send the smallest possible set of fields required to send Lotus Notes mail. This option is particularly useful for mobile Lotus Notes users.

Note

specification for the subset of documents is only applicable to the

destination/source server combination selected in the Replication Settings dialog box.

d. A replication formula is similar in concept to a view formula. You may use replication formulas to determine which documents a replica receives.

Check Select by formula, having first checked Replicate a subset of documents.

You can then enter the formula that defines the subset of documents in the formula window (see Figure 120).

Note: The specification for the subset of documents is only applicable to the destination/source server combination selected in the Replication Settings dialog box.

Figure 120. Selecting a Subset of Documents by Formula

The formula shown in the formula window of Figure 120 will only allow documents with the string "Red Book" in the Subject field of the database to be replicated.

You cannot use @DbLookup, @UserName, @Environment, or @Now in a replication formula.

Using @IsResponseDoc in a replication formula causes all response documents in a database to replicate, not just those that meet the selection criteria. To avoid this, use @AllChildren or @AllDescendants instead.

3. Select the database features that replicas can receive.

It is possible to tailor the following replication features:

c. Select Replication formula to allow a replica to receive the selected replication settings.

Note: Steps a, b and c above are only relevant when the source server has Manager or Designer access to the replica as specified in the ACL of the replica database.

d. Deselect Access control list (ACL) to prevent a replica from receiving changes made to the ACL. This is only relevant if the source server has Manager access to the replica.

e. Select Deletions to allow a replica to act on deleted documents.

Documents will not be deleted from the replica database if:

1) Do not send deletions made in this replica to other replicas is