Converting an existing peer server to a Gateway server

Edit online

Before converting a peer server to a Gateway server, make sure the subtree is quiesced and there are no pending changes. The example provided here shows a replica subentry that is NOT configured as a Gateway server.

About this task

dn: ibm-replicaServerId=<serverid>,ibm-replicagroup=default,o=sandbox
objectclass: top
objectclass: ibm-replicaSubentry
ibm-replicaServerId: <serverid>
ibm-replicationServerIsMaster: TRUE
cn: <servername>

To convert this peer to a gateway, add the ibm-replicaGateway auxiliary object class to the required replica subentry in the DIT. The ibm-replicaGateway auxiliary object class is bold in the following example.

dn: ibm-replicaServerId=<serverid>,ibm-replicagroup=default,o=sandbox
	changetype: modify
	add: objectclass
	objectclass: ibm-replicaGateway

Where <servername> is the name of the server, and where <serverid> is a 37 character string assigned the first time a server is started. The server ID can be found by typing the following command at a command prompt:

idsldapsearch -p <port> -b "" -s base objectclass=*

For information about removing an auxiliary object class, see Deletion of an auxiliary object class.