DB2 9.5 ESE 32 bits for Linux can’t be licensed

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.

IBM AT&T VPN client on Linux (Ubuntu)

A couple of months ago AT&T release a beta version of their VPN Client for linux.

Unfortunately they released the client as a RPM ( RedHat package ) and not
as an Ubuntu DEB package.

But help was nearby, on this website I found how to convert the RPM
package to an Ubuntu DEB package.

http://blog.afmacedo.com/?p=11

And here you can download the latest IBM AT&T VPN Client
for Linux (@ 07/01/09 )

ftp://ftp.attglobal.net/pub/client/linux/agnclient-1.0-2.0.1.3000.i386.rpm

After converting and installing I could find the app here :

Internet -> AT&T Global Network Client

And check it out AT&T VPN client on Linux

Secondary addressbook Domino LDAP Lotus Connections profiles

We configured our Lotus Connections setup to use our Domino LDAP
as the user repository.
In this Domino LDAP we have a primair and secondary addressbook.

When configuring profiles to use our Domino LDAP we discovered that
profiles wouldn’t read any entries that were in the secondary address book.

But after some experimenting with the settings in the file profiles_tdi.properties
we found out that when we leave the parameter source_ldap_search_base
empty we were able to retrieve the users from the secondary address book.

Strange issue but for now we can work with it.