Search

LOTUSCONNECTIONS.org

Wikipedia “Lotus Connections is often described as the leading product in enterprise social software market”

Currently I’m busy setting up Connections for a customer who is
active across the whole world.

Connections has to be set-up to use all LDAP domain servers in use, one
located in the North-America region, one located in the Asian Pacific
region and one located in Europe.

To give myself some more info about the request times looking
up users takes, I found these handy LDAP benchmark tools.

They will show you the time taken to lookup users in the LDAP.
Good info to know to see how much time it takes to lookup users located
in the LDAP domain server that’s located on the other end of the world.

This is one with a GUI, simple to use, not to advanced

http://www.novell.com/coolsolutions/tools/14046.html

Command line one, not simple in its usage, and for my taste to advanced .

http://www.mindcraft.com/directorymark/

Be sure to set these attributes in the directorymark config file

!FILE CONFIG.CON2
 SERVERNAME:10.19.20.100
 SERVERPORT:389
 CLIENTBASESCRIPTS:client1.script
 BINDDN:CN=WebSphereLCbind,CN=Users,DC=globalcorp,DC=net
 BINDPW:doyouneedtoknowthis
 STATDIR:Results\                          #  Be sure this dir exists.

 #For the first time running and to test if everything works out
 #I would suggest to change the following attribute as follows

 MAXRUNTIME:-1
 NUMCLIENTS:1
 THREADSPERCLIENT:1

 # and enable these two attributes to get as much detailed results as possible
 DEBUG:1
 VERBOSE: 1
!FILE

FILE client1.script
 bind_as_root
 ldap_search
 dc=ap,DC=globalcorp,DC=net
 LDAP_SCOPE_SUBTREE
 (&(sAMAccountName=dillm)(objectclass=user))
 ALL
 0
!FILE

Then running the directorymark.exe will give you a output similiar like below

C:\DirectoryMark1.3-Bin-Win2k>DirectoryMark.exe config.conf2

Running Script client1.script0
bind as root: ‘CN=WebSphereLCbind,CN=Users,DC=globalcorp,DC=net’, password ‘doyouneedtoknowit’
t00: ldap_search_st returned 0×00, time:     2 ms, numentries:  1, args: 3301328
, dc=ap,DC=leaseplancorp,DC=net, 2, (&(sAMAccountName=dillm)(objectclass=user)),
 NULL, 1
Thread 0, Done with transactions
thread 0 complete
all threads complete
all children completed

Finally discovered how I have to use the delete_employees.sh script.
Did some debugging of the profiles_tdi.xml file in the TDISOL
directory with TDI.

Found out that the file delete_employees.in had to contain the
following syntax.

FILE delete_employees.in
$dn:CN=Marco Ensing,OU=EOF,O=EOG.
uid:Marco Ensing
!FILE

( To delete multiple persons use a dot after every entry

$dn:CN=Marco Ensing,OU=EOF,O=EOG.
uid:Marco Ensing
.
$dn:CN=Pietje Puk,OU=EOF,O=EOG.
uid:Pietje Puk
)

FILE profiles_tdi.properties
delete_employees_simple_file=delete_employees.in
!FILE

Also found out how to use the sync_all_dns.sh command. Before I couldn’t
get this script to work properly. I got stuck when I wanted to delete people
from the profiles database, the sync command didn’t work for me and I didn’t
had a clue how to use the delete_employees.sh script.

If I wanted to add users to Profiles I had to use the collect_dns.sh and
populatie_from_dn_file.sh scripts.

To use the sync_all_dns.sh properly configure the parameters in the
file profiles_tdi.properties as follow.

FILE profiles_tdi.properties
sync_updates_show_summary_only=false
sync_updates_double_check=true
!FILE

Now the sync_all_dns.sh script will take care of deleting people in Profiles
which no longer exist in the LDAP directory. And it will add people, new
in the LDAP directory, to the Profiles database.

( We are using Domino 8.5 as our LDAP directory )