LOTUSCONNECTIONS.org

  Somewhere last week I configured AWstats for our
Connections environment to figure out what the usage is and to see
what our  busiest usage period is.

Because we use cronolog to rotate our access.log file on our IHS
server, every day get it’s own directory and access.log.

No problem with AWstats, you can configure it like this.

FILE ./awstats.connectons.company.com
 LogFile=”/data/alogs/connections.company.com/access.log/%YYYY-0/%MM-0/%DD-0/access.log”
!FILE

But after running it for a few days I say one host owning the host top 10
list with more then 65000 page requests in only a couple of days.
After a #dig -x 123.123.123.123 I found that this was a Notes Domino
server equipped with an agent that collected the RSS feeds of
Blogs and Activities 24/7.

By configuring the SkipHosts= option in de config file of AWstats for
our Connections environment I could ignore requests coming from
this Domino server for  the upcoming stats collections.

But to get a good picture of the usage of Connections in the pas days I
searched how I got rebuild the AWstats database to completely ignore
the mentioned Domino server in all stats.

Because we use log rotation for our access logs I could not simple delete
the database as built by awstats. Only deleting the database and a
rerun of the awstats.pl script just gave me the stats of the current day.

Solution, #cat all the access logs of the different days to one and
configure this log file for an one-time run in your awstats
configuration file, et voila.

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