Search

LOTUSCONNECTIONS.org

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

So it seems, DB2 9.5 ESE 32 bits can’t be licensed on a Linux 32 bits server

http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21313828

So if you want to use DB2 9.5 ESE 32 bits for Linux in production you will have
to switch to the 64 bits version. That or go with one of the lower version
of the DB2 9.5 family like Workgroup Edition or Personal Edition.

http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.qb.server.doc/doc/r0023732.html

1. Only test and development are supported in DB2 Enterprise Server Edition and DB2 Text Search for Linux on x86-32 hardware.

Are there special licenses for test and dev environments? Because
either what the purpose is of your environment with a trial license
it will stop working when the end date kicks in.

Ray & Anita – In Da Name Of Love

In the Profiles part of Lotus Connections you can configure
multiple profile types, which will give you different lay-outs per type.

You can follow this InfoCenter link how to set it up.
Mitch Cohen also wrote a very detailed guide how to do it.

One thing I came about is how to populate the PROF_TYPE database
field in the EMPINST.EMPLOYEE table. This column is used to determine
what kind of profile type should be used for an user.

I discovered that you can use the following line in the
map_dbrepos_from_source.properties file to use a LDAP attribute
to populate the PROF_TYPE field. This option is not mentioned
in the InfoCenter of Lotus Connections.

PROF_TYPE=employeeType

(
or what LDAP attribute you want to use, but the field employeeType
looks pretty obvious to me :-p

employeeType is an attribute from the objectClass inetorgperson
)

With this config, the sync_all_dns.sh command will use the LDAP
field employeeType to fill the PROF_TYPE column in the
EMPLOYEE table of profiles. This also will keep the profile type
up-to-date if the employeeType LDAP attribute of a user should change.                                       

Below a script you can use to set the rights for every part of Connections correctly.

Handy to fix the rights after you have done an upgrade.

FILE ConfigureRightsActivities.py
 appName = ‘Activities’
 lcsearchadmin=’LCdev admin’
 lcadmin=’LCdev admin’

 AdminApp.edit(appName, ‘[ -MapRolesToUsers [ ["person" no yes "" ""] ["everyone" yes no "" ""] ["reader" no
 yes "" ""] ["search-admin" no no "'+lcsearchadmin+'" ""]  ["widget-admin" no no "'+lcadmin+'" "" ] ] ]’)
 print “done…. Configuring rights Activities EAR”
 AdminConfig.save()
!FILE

Run it as follow.

./wsadmin.sh -lang jython -port 8880 -username wasadmin -password udontneedtoknowthispunk -f ./wsadmin_scripts/configureRightsActivities.py

To do it for the other parts just change the appName var, be aware
that the roles between all the Connections parts differ. The Homepage
part for example doesn’t has the search-admin role.

Lotus Connections 2.0.1 Fix Pack 1 ( 2.0.1.1) has been released.

Currently there are already four new ifixes for the 2.0.1.1 version. Can’t give
any practical tips yet, cause I didn’t saw a change to apply this one.

When installing Lotus Connections one of the tasks is to make a secure trust
between the WebSphere server and the IHS server. To do this you have to
configure SSL in such a way that the signer of the SSL certificate of the
WebSphere server is known by the IHS server.

After three weeks of down-time my website finally is back on the net.

My ISP (Telfort) messed something up therefor I lost my internet connection.
Because I host my server @home my website also was unreachable for
three weeks.

As an extra suprise my IP was changed so I also had to change my DNS
entries, something I found out after a few days.

But eh were back now

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

Very detailed….

Flash alert for WebSphere Application Server concerning a security risk.

And then why post it here , Lotus Connections runs on WAS 6.1.0.13
and thus is vulnerably.

Check out the fix here.

Problem Description:
Customers who have Web based applications, including Web services applications running on WebSphere Application Server, have the risk of an attacker having the ability to display application specific files contained within the war file. In addition, there is a potential risk for customers who are using the WebSphere administrative console with administrative security disabled. Credit to Edward Schaller for disclosing this problem to IBM.

For V6.1.0.11 through 6.1.0.21:

• Apply Interim Fix APAR PK81387
• –OR–
• Apply Fix Pack 23 or later (6.1.0.23 targeted to be available late March 2009).