status of replication, including updates in progress, current changes sequence numbers, and the lag between when a change is made on the supplier and when that change is sent to the consumer.

Monitoring replication is set up using a simple configuration file which specifies which server to monitor and what supplier and consumer replicas to include in the status page.

When trying to monitor replication status through Admin Express, remember two things:

The Replication Status page is only available for supplier servers. (It can be opened for other types of replicas; there's just no information available and has the message The server is not a master or it has no replication agreement.)

The configuration file must be in a directory that is accessible to Admin Server, and the file must be readable by the Admin Server user. By default, the user is nobody.

The user is set in the console.conf file. To check the user, use the grep command to return the value:

grep \^User /etc/opt/dirsrv/admin-serv/console.conf

The configuration file should be readable by the Admin Server user and no other users, so consider resetting the permissions on the file:

chmod 0400 filenameTo view in-progress status of replication in Admin Express:

1.Create a configuration file. The configuration file lists all the servers to monitor for replication, giving their host name, port, the bind credentials to use, and optional settings for aliases and time lag colors.

#Configuration File for Monitoring Replication Via Admin Express

[connection] Required. Gives the server host, port, supplier bind DN, and password. host1.example.com:389:cn=replication manager:mypassword host2.example.com:3891:cn=replication manager:altpassword

[alias] Optional. Gives a friendly-name alias to the servers and consumers.

M1 = host1.example.com:389

M2 = host2.example.com:3891

C1 = host3.example.com:3892

C2 = host4.example.com:3890

[color] Optional. Sets the color for the time lag boxes. 0 = #ccffcc

5 = #FFFFCC

60 = #FFCCCC

The configuration file must be in a directory that is accessible to the Admin Server, and the file must be readable by the Admin Server user. By default, the user is nobody.

The user is set in the console.conf file. To check the user, use the grep command to return the value:

grep \^User /etc/opt/dirsrv/admin-serv/console.conf

The configuration file should be readable by the Admin Server user and no other users, so consider resetting the permissions on the file:

chmod 0400 filename

2.In the Admin Server web page, click the Admin Express link, and log in.3.Click the Replication Status link by the supplier server name.

4.Type the path to the configuration file in the Configuration file field. Also, set the refresh rate, which is how frequently the replication status page updates; the default is 300 seconds.

3.1 Managing servers in Admin Express 35