7. Simple Proxy Deployments Using the Command Line Interface > Configuring Distribution With the Command Line Interface |
1. Overview of Sun OpenDS Standard Edition
2. Overview of the Directory Server
3. Overview of the Proxy Server
4. Building Blocks of the Proxy Server
5. Example Deployments Using the Directory Server
6. Example Deployments Using the Proxy Server
7. Simple Proxy Deployments Using the Command Line Interface
Configuring Load Balancing With the Command Line Interface
To Configure Simple Load Balancing
Configuring Distribution With the Command Line Interface
Configuring Distribution and Load Balancing
$ dsconfig -p 4444 -h localhost -D"cn=Directory Manager" -w password \ create-extension \ --extension-name proxy_extension1 \ --type ldap-server \ --set enabled:true \ --set remote-ldap-server-address:DS1_hostname \ --set remote-ldap-server-port:2389
The LDAP server extension is a link to the back-end LDAP server. For this use case, you will need two back-end LDAP server instances. Go through this step again, making sure to use a different LDAP hostname and port.
$ dsconfig -p 4444 -h localhost -D"cn=Directory Manager" -w password \ create-workflow-element \ --element-name proxy-we1 \ --type proxy-ldap\ --set enabled:true \ --set client-cred-mode:use-client-identity \ --set ldap-server-extension:proxy_extension1
You will need at least two remote LDAP servers for a distribution architecture. Go through this step again. The LDAP server extension name should be the same as those created in step 1.
The property client-cred-mode indicates the type of authentication used between the proxy and back-end LDAP server. The client credential mode can be: use-client-identity, use-specific-identity, or use-proxy-auth.
$ dsconfig -p 4444 -h localhost -D"cn=Directory Manager" -w password \ create-workflow-element \ --element-name distrib-we \ --type distribution \ --set base-dn:dc=example,dc=com \ --set enabled:true
$ dsconfig -p 4444 -h localhost -D"cn=Directory Manager" -w password \ create-distribution-algorithm \ --element-name distrib-we \ --type numeric \ --set distribution-attribute:uid
The type of distribution algorithm can be numeric, lexicographic, or by DN pattern match. The properties of the algorithm are defined when you create the distribution partitions, in the next step.
$ dsconfig -p 4444 -h localhost -D"cn=Directory Manager" -w password \ create-distribution-partition \ --element-name distrib-we \ --partition-name distrib-part1\ --type numeric \ --set lower-bound:0 \ --set upper-bound:1000 \ --set partition-id:1 \ --set workflow-element:proxy-we1
For this use case, you will need to create two partitions. Make sure that the partition ID and the partition name are unique for each workflow element. You must specify the same type when defining the partitions as you did when defining the load balancing algorithm.
Note - The upper boundary indicated is exclusive. This means that if you indicate 1000 as the upper boundary, the partition will only include values from 0 to 999, inclusive.
This workflow associates the distribution workflow element with the distribution partition.
$ dsconfig -p 4444 -h localhost -D"cn=Directory Manager" -w password \ create-workflow \ --workflow-name distrib-workflow \ --set enabled:true \ --set base-dn:dc=example,dc=com \ --set workflow-element:distrib-we
The network group handles all the requests between the client and the proxy.
$ dsconfig -p 4444 -h localhost -D"cn=Directory Manager" -w password \ create-network-group \ --group-name network-group1 \ --set enabled:true \ --set workflow:distrib-workflow \ --set priority:1