Blog

Continuing the Sametime clustering catch up - Day 2


Tags :


This time I was lucky enough to find 3 access points but all were WEP.  Bummer.  So this time I found a cool tiny Thai place for dinner.  The service was fantastic at Thai Basil.

But down to business.  I know part of the customer team reads this daily (however we know that the IBM'ers here do not and have no idea what they are missing right?) and are expecting a lot.  But I won't let too many secrets out.  In my eyes the basics of the cluster are a success.  There were modifications to be made to a class file that searched and modified the appearance of the Sametime home server when using LDAP.  But they also had some other customizations that we have to build back in.

Replacing the Home Sametime Server (HSS) is a main key of Community Clusters.  Proper DNS plays a major role in this since we are parsing the server name with the LDAP queries.  Integrating this new cluster with an existing Sametime chat server (during the migration time) and then the internal and external meeting configuration is all still to come.

We did somehow manage to make a Sametime admin client that only did Meeting Services.  How we got it, we don't know nor did we spend the time to work it out.  But it was blue (from the new Sametime FP1 for 6.5.1 changes. Yes, this means that IBM put a blue IBM banner at the top for branding above the normal yellow.  The only strange part was that the product title was called IBM Lotus Web Conferencing.  I wonder what happened to the Instant Messaging part of that title bar?  And now it goes back to Sametime.


I am definitely full from the Keang Keow Wan (Thai green curry with chicken, medium spicy) and a dessert that was recommended.  Fried bananas with mango and green tea ice cream.