Configuration instance of LDAP Advanced replication on z/OS

LDAP guarantees the synchronization of data on multiple servers through the replication mechanism. The LDAP server on z/OS supports two forms of Replication, basic Replication and Advanced Replication.

Basic replication provides the most basic data synchronization service, which supports only the Master-replica and basic peer-peer two topologies, and the smallest unit of synchronization is a complete back end (backend). By contrast, Advanced replication provides a more flexible data synchronization mechanism, where the granularity of synchronization can be subdivided into one subtree in a specific backend, and a combination of multiple topologies is supported to meet the need for more complex data redundancy.

Currently, the LDAP server on z/OS supports the following topologies applied to advanced replication, master-replica,forwarding (cascading), Peer-peer, and Gateway. Also, these topologies can be combined to meet more complex synchronization requirements.

This article will mainly introduce the configuration method of advanced replication based on Master-forwarder-replica topology, i.e. cascading mode. The following figure is a typical master-forwarder-replica topology where Master is the provider of data (Supplier) and the source of data synchronization, replica is the ultimate data receiver and consumer (Consumer), Forwarder, as a relay node on the transfer chain, also plays both roles.

Fig. 1 Typical Master-forwarder-replica topological structure

In view of the large number of nodes involved in the structure shown above and the cumbersome configuration, this paper introduces the advanced replication configuration process under the simplest cascading structure, that is, only Master,forwarder and replica are only one. Among them, Server1 as master, listening on port 391,server2 as forwarder and listening on port 392, while serving as replica Server3 listening Port 393. Each configuration file looks like this, noting that you must define the CDBM backend and turn on the useadvancedreplication option:

Master.conf

----------------------------------------------------------------------------------------------------

Admindn "Cn=admin1"

Listen ldap://:391

Logfile/home/suimgwk/ldap/tmp/active1.log

Schemapath/home/suimgwk/ldap/mine/lib/arepl/schema1

Servercompatlevel 7

Database ldbm GLDBLD31/GLDBLD64

Suffix "o=myldbm"

Databasedirectory/home/suimgwk/ldap/mine/lib/arepl/ldbm1

Database cdbm gldbcd31/gldbcd64 cdbm

Databasedirectory/home/suimgwk/ldap/mine/lib/arepl/cdbm1

Useadvancedreplication on

----------------------------------------------------------------------------------------------------

Forwarder.conf

----------------------------------------------------------------------------------------------------

Admindn "Cn=admin2"

Listen ldap://:392

Logfile/home/suimgwk/ldap/tmp/active2.log

Schemapath/home/suimgwk/ldap/mine/lib/arepl/schema2

Servercompatlevel 7

Database ldbm GLDBLD31/GLDBLD64

Suffix "o=myldbm"

Databasedirectory/home/suimgwk/ldap/mine/lib/arepl/ldbm2

Database cdbm gldbcd31/gldbcd64 cdbm

Databasedirectory/home/suimgwk/ldap/mine/lib/arepl/cdbm2

Useadvancedreplication on

----------------------------------------------------------------------------------------------------

Replica.conf

----------------------------------------------------------------------------------------------------