Using Web Administration

Edit online

You can use the instructions provided here to set up the gateway topology using Web Administration Tool.

About this task

Note: Before starting to set up your replication topology, make a backup copy of your original configuration file (ibmslapd.conf) and the key stash files (ibmslapddir.ksf and ibmslapdcfg.ksf) ibmslapd.conf file. You can use this backup copy to restore your original configuration if you encounter difficulties with replication. In addition you need to save the replication topology information stored in the directory. Use the idsdb2ldif utility to export the ibm-replicagroup=default subtree of the replicated subtree. For example, if you are changing the topology for the subtree o=sample, you need to export the subtree ibm-replicagroup=default,o=sample.
Attention: If restoring, you must restore to the same operating system as the operating system on which the failure occurred. If you don't restore to the same operating system, there might be errors.
To set up a gateway using the complex topology with peer replication from the previous scenario:
Figure 1. Initial peer-to-peer topology

The illustration shows two peer servers with two forwarding servers as consumers. Each forwarding server has two replica servers as its consumers.
  • Convert an existing peer server (peer1) to a Gateway server to create replication site1.
  • Create a new gateway server for replication site 2 and agreements with peer1.
  • Create the topology for replication site 2 (not illustrated in this example).
  • Copy the data from the master to all the machines in the topology.

Procedure

  1. Use the Web Administration Tool to log on to the master (server1).
  2. Expand the Replication management category in the navigation area and click Manage topology.
  3. Select the subtree that you want and click Show topology.
  4. To convert an existing server to a gateway server, click Manage gateway servers. Select server1 or its peer server5. For this example use server1 and click Make gateway.
  5. Click OK.Note: If the server you want to use as a gateway is not already a master, it must be a leaf replica with no subordinate replicas that you can first promote to be a master and then designate as a gateway.
  6. To create a new gateway server, Click Add server.
  7. Create the new server, server9 as a gateway server. See Adding a peer-master or gateway server for information about how to do that.
  8. The Create additional supplier agreements panel is displayed. Ensure that the supplier agreement boxes are checked for server1 only. Deselect the other agreements.
    Select Supplier Consumer
    ✓ server1 server9
    ✓ server9 server1
    server2 server9
    server9 server2
    server4 server9
    server9 server4
    server9 server5
    server5 server9
  9. Click Continue.
  10. Click OK.
  11. Add the appropriate credentials and consumer information.Note: In some cases the Select credentials panel will open asking for a credential that is located in a place other than cn=replication,cn=localhost. In such situations you must provide a credential object that is located in a place other than cn=replication,cn=localhost. Select the credentials the subtree is going to use from the existing sets of credentials or create new credentials. See Adding credentials.
  12. Click OK.
    The server roles are represented by icons in the Web Administration Tool. Your topology is now:
    • server1 (master-gateway for replication site1)
      • server2 (forwarder)
        • server3 (replica)
        • server6 (replica)
      • server4 (forwarder)
        • server7 (replica)
        • server8 (replica)
      • server5 (master)
      • server9 (master-gateway for replication site 2)
    • server5 (master)
      • server1 (master)
      • server2 (forwarder)
        • server3 (replica)
        • server6 (replica)
      • server4 (forwarder)
        • server7 (replica)
        • server8 (replica)
    • server9 (master-gatway)
      • server1 (master-gateway)
    Figure 2. A gateway topology with two replication sites

    The illustration shows two replications sites. One site has a gateway server and a peer server with two forwarding servers as consumers. Each forwarding server has two replica servers as its consumers. The second site contains a single gateway server that was originally a master server in the first replication site.
  13. Add servers to server9 to create the topology for replication site 2. Remember to deselect any agreement for the new servers to any servers outside of replication site 2.
  14. Repeat this process to create additional replication sites. Remember to create only one gateway server per replication site. However, each gateway server must be present in the topologies with agreements to the other gateway servers.
  15. When you have finished creating the topology, copy the data from server1 to the all the new servers in all the replication sites and if required, add the supplier credential information to all the new servers. See Copying data to the replica and Adding the supplier information to a replica for information about how to do that.