Tag: update_site

Patch for lost messages in Sametime 7.5.1 tabbed chat interface

As previously mentioned (Sametime 7.5.1 tabbed interface is loosing messages!) I upgraded to Sametime Connect 7.5.1 and began loosing chat messages when using the new tabbed chat interface. I was kindly informed by Hans-Peter Kuessner from Domblog.de of two IBM patches for the issue. I contacted Lotus Support and requested the hotfixes and promptly received them. I have provisioned the hotfix to my users using the automatisk provisioning built into Sametime 7.5. The automatic update of user Connect clients has worked like a charm and the patch has solved the issue. Nice!

Below is a screenshot of the dialog shown to users after the patch has been automatically installed and a screenshot of the “Manage plug-ins” dialog after the feature patch has been installed.

Only feature I could see the need for would be some way to see which users have installed the patch and who haven’t. Of cause users do not have the option of not installing the patch but still it would be nice to know how many of the users have been updated. Some might be connecting from home where they might not have access to the update site. I haven’t checked the log so strictly speaking I don’t know if it’s there but somehow I doubt it.

Lotusphere 2007: Run your Update Sites from Domino (ID211)


Just attended ID211 by Thomas Gumz from IBM on how you can use Domino as the source for your Update Site to provision features and plug-ins to Sametime 7.5, Expeditor and Notes 8. Lotus has built a really cool template, shipping with Notes 8, that allows you to run an Update Site out of a Notes database instead of using a file system based site. Very cool.

Thomas also mentioned that in Notes 8 you can provision features and plug-ins using NRPC instead of HTTP for remote sites. This will only work against Domino 8 servers since this is a new call that has been added to the NRPC protocol. The URL syntax will be something like nrpc://intranet.company.com/_<replica_id>/updatesite.nsf instead of the http:// equivalent.

Update Site for Sametime – why not simply go local?

As pointed to by Adam Gartenberg there’s a new article out on developerWorks (Creating an update site for your IBM Lotus Sametime Connect plug-ins) on how to create an Update Site for your Sametime client deployment. As much as I would recommend the article I really would suggest that readers don’t stop there and read the entire story on Update Sites at Eclipse.org (How to keep up to date) before venturing into this territory.

Although the developerWorks article does a nice job of describing the subject for the Sametime inclined I would recommend also reading about the Eclipse foundations…

As an aside I also wants to mention that you can test plugins using an Update Site without having a HTTP server ready (although we all have a Domino server ready, no?). You can do this because the Eclipse framework also allows for local Update Sites (i.e. on the same computer or on a network share). To use this feature simply choose “Local Site” instead of “Remote Site” and point your Sametime client to the Update Site directory under your Eclipse workspace. Very nice for testing.