7. Simple Proxy Deployments Using the Command Line Interface > Configuring Load Balancing 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
Configuring Distribution With the Command Line Interface
To Configure Simple Distribution
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 at least 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
The property client-cred-mode indicates the type of authentication used between the proxy and remote 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 LB-we1 \ --type load-balancing \ --set enabled:true
You only need one load balancing workflow element to route requests to either of the two back-end LDAP servers.
$ dsconfig -p 4444 -h localhost -D"cn=Directory Manager" -w password \ create-load-balancing-algorithm \ --element-name LB-we1 \ --type failover
The type of load balancing algorithm can be proportional, saturation or failover. The properties of the load balancing algorithm (weight, threshold, or priority) are defined with the load balancing routes, in the next step.
$ dsconfig -p 4444 -h localhost -D"cn=Directory Manager" -w password \ create-load-balancing-route \ --element-name LB-we1 \ --route-name LB-route1 \ --type failover \ --set workflow-element:proxy-we1 \ --set priority:1
Make sure that you specify the same type when defining the routes as you did when defining the load balancing algorithm.
For this use case, you will need two load balancing routes. Go through this step again, specifying a different priority for each route.
The properties in the example above set the priority for failover load balancing. If you use proportional or saturation load balancing, the properties will differ. For more information on the setting different load balancing types, see Modifying the Load Balancing Route Properties in Sun OpenDS Standard Edition 2.2 Administration Guide.
This workflow associates the load balancing workflow element with the specified base dn.
$ dsconfig -p 4444 -h localhost -D"cn=Directory Manager" -w password \ create-workflow \ --workflow-name LB-workflow1 \ --set enabled:true \ --set base-dn:dc=example,dc=com \ --set workflow-element:LB-we1
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:LB-workflow1 \ --set priority:1