dps 6.1 trouble

I configured a directory proxy 6.1 as root with command line on redhat

I am in trouble but can't find what was wrong in my process

all the following actions between ########## were successful

########## ########## ########## ########## ########## ########## ########## ########## ########## ##########

cd /opt/sun/dps6/bin

./dpadm create -D cn=proxyman -p 389 -P 636 /opt/sun/dps-xxxx

./dpadm start /opt/sun/dps-xxxx

./dpconf create-ldap-data-source -D cn=proxyman -h localhost -p 389 "LDAP xxxx SLX110" ldap01:60389

./dpconf create-ldap-data-source-pool -D cn=proxyman -h localhost -p 389 "Pool de connexion LDAP"

./dpconf attach-ldap-data-source -D cn=proxyman -h localhost -p 389 "Pool de connexion LDAP" "LDAP xxxx SLX110"

./dpconf create-ldap-data-view -D cn=proxyman -h localhost -p 389 "Vue par defaut" "Pool de connexion LDAP" dc=xxxx,dc=lan

./dpconf set-ldap-data-source-prop -D cn=proxyman -h localhost -p 389 "LDAP xxxx SLX110" is-enabled:true

./dpadm restart /opt/sun/dps-xxxx

./dpconf get-ldap-data-source-prop -D cn=proxyman -h localhost -p 389 "LDAP xxxx SLX110"

........................

bind-dn: none

bind-pwd: none

client-cred-mode: use-client-identity

connect-timeout: 10s

description: -

is-enabled : true

is-read-only: false

ldap-address: ldap01

ldap-port : 60389

ldaps-port : ldaps

monitoring-bind-timeout: 5s

monitoring-entry-dn: ""

monitoring-entry-timeout: 5s

monitoring-inactivity-timeout : 2m

monitoring-interval: 30s

monitoring-mode: proactive

monitoring-search-filter: (|(objectClass=*)(objectClass=ldapSubEntry))

num-bind-incr: 10

num-bind-init: 2

num-bind-limit: 1024

num-read-incr: 10

num-read-init: 2

num-read-limit: 1024

num-write-incr: 10

num-write-init: 2

num-write-limit: 1024

proxied-auth-use-v1: false

ssl-policy : never

use-tcp-no-delay: true

NOW,it's time to test

ldapsearch works perfectly targetting the LDAP server but fails targetting the proxy

cd /opt/sun/dsrk6/bin

./ldapsearch -1-h ldap1 -p 50389 -D cn=dirman -w - -s one -b "dc=xxxx,dc=lan" ou=* ou

xxxxxxxxxxxxxxxxxxxxx

########## ########## ########## ########## ########## ########## ########## ########## ########## ##########

./ldapsearch -1 -h ldap1 -p 389 -D cn=dirman -w - -s one -b "dc=xxxx,dc=lan" ou=* ou

ldap_simple_bind: Operations error

ldap_simple_bind: additional info: Unable to retrieve a backend BIND connection

Any idea on my mistake?

[2725 byte] By [Alban_for_SmartWavea] at [2007-11-27 9:34:00]
# 1

This is simple and yet I believe it should be documented properly as everyone falls in it the first time.

cn=dirman is not within the dc=xxx,dc=lan dataview. And is unknown by the proxy itself.

A default dataview is created and manages all suffixes, but it is not attached to any ldap source (as there is no default ldap source).

You must either create a data view for cn=dirman (or cn=directory manager for those who prefer the default), or attached the default dataview to the LDAP data source pool.

Regards,

Ludovic.

ludovicpa at 2007-7-12 22:57:04 > top of Java-index,Web & Directory Servers,Directory Servers...
# 2

it was the same with a user in the suffixe,

i created a data source, set in the dapa pool, set the default view and so on. still the same error 1

So I deleted all, recreate with the web DSCC and now it is ok.

enigma....

Regards

Thanks for your Help ludovic

Alban

Alban_for_SmartWavea at 2007-7-12 22:57:04 > top of Java-index,Web & Directory Servers,Directory Servers...