1. Use the dsconfig tool to create and configure a request processor.
    $ bin/dsconfig
  2. Specify the host name, connection method, port number, and bind DN as described in previous procedures.
  3. In the Directory Proxy Server main menu, enter the number associated with Request Processor configuration and select the option to create a new Request Processor.
  4. Select an existing request processor to use as a template for creating a new one or enter n to create one from scratch. In this example, we create a new proxying request processor from scratch. You will be required to choose an existing load balancing algorithm or create a new one to complete the create of the request processor. Below is the configuration of the proxying request processor after selection of the load balancing algorithm.
    Property                     Value(s)
    1)  description              -
    2)  enabled                  true
    3)  allowed-operation        abandon, add, bind, compare, delete,
                                 extended, modify, modify-dn, search
    4)  load-balancing-algorithm dc_example_dc_com-fewest-operations
    5)  transformation           -
    6)  referral-behavior        pass-through
    7)  supported-control        account-usable, assertion,
                                 get-effective-rights, get-server-id,
                                 intermediate-client, manage-dsa-it,
                                 matched-values, no-op, password-policy,
                                 permissive-modify, post-read, pre-read,
                                 real-attributes-only, retain-identity,
                                 subentries, subtree-delete,
    8)  supported-control-oid    -
    ?)  help
    f)  finish - create the new Proxying Request Processor
    d)  display the equivalent dsconfig arguments to create this object
    b)  back
    q)  quit
  5. Review the configuration properties of the new request processor. If you are satisfied, enter f to finish. For the request processor to be used, it must be associated with a subtree view.