As you might recall we at IntraVision some time back quit running Lotus Sametime on-premises and switched to LotusLive. This wasn't without issues and I also blogged about the apparent lack of public groups in my "Using LotusLive for Sametime - 2 months in" post a couple of months ago. After experiencing this issue I talked to Erik Vos from RealConnections in the Netherlands at NLLUG. Erik was also having the same problem for his SaaS customers so we worked together to develop a proof-of-concept Notes sidebar plugin called Stommunity to work around the issue. The name Stommunity plays on the words Sametime (ST) and (LotusLive) Community.
So what does the plugin do?
The plugin synchronizes your LotusLive communities with your Lotus Sametime client and creates private groups based on the LotusLive communities you are a member of (and that you select for synchronization). This mimics the missing public group feature of LotusLive Sametime. The below screenshot shows a Sametime client with 4 communities synchronized from LotusLive.
So how does the plugin work?
The plugin sits as a sidebar plugin in your Lotus Notes client and monitors your Sametime client for when it logs into LotusLive Sametime. Once a login is detected it reads the communities the active user is a member of using the LotusLive REST API and shows a list of the communities. The user may then select the communities to synchronize with Sametime. The below screenshot shows the Stommunity plugin waiting for the user to log into Sametime.
Once logged in the communities is read from LotusLive. In the below screenshot you can see that the user is a member of a couple of communities but only one is synchronized with Sametime.
After selecting an additional community and clicking Apply the community is synchronized to Sametime and a private group is created. The below screenshot shows the Sametime client after synchronizing the BlueExtend community with the Sametime client.
So why only a proof-of-concept and not a ready-to-roll plugin?
While developing the plugin we discussed the license implications of a plugin like this. When you sign up for LotusLive Engage you receive a Sametime Entry license which means you may not use the Sametime API which again means that a plugin like this cannot work (from a licensing standpoint). That alone made the project a dead-end and after working a bit with IBM on this it became clear that changing the licensing agreement wasn't in the books. Due to this we are releasing the plugin as a proof-of-concept with open source on OpenNTF hoping that it may inspire someone.
Looking at the plugin as it is now I see a lot of potential. Of course the selection of communities needs to be pushed into the preferences but as a LotusLive customer it would be really cool to have. I imagine an auto-sync option being added as well as an option to just sync all and change (or remove) the prefix I automatically add now ("LL Community:"). Think of having a policy option to automatically make certain, company wide, communities be synchronized to all users (or a set of users). Maybe even controlled from within LotusLive. Now that would be cool and bridge the gap between the products. One could even argue that a plugin like this should be a standard component that should come bundled with LotusLive Notes.
Anyways - I hope it may inspire the LotusLive teams.
The Stommunity plugin may be found on OpenNTF.org and the code may be downloaded from the SVN repository. See below for links to each.
Trusting certificates in WebSphere Application Server
Fri, Nov 29th 2013 3:33a Mikkel Heisterberg If you make SSL connections from a WebSphere Application Server based application the server (or rather the cell) needs to trust the certificate of the server you are connecting to. This is very easy to do in WAS and is easily done using the Integrated Solutions Console (ISC). The way to establish the trust is as follows:
Log into the WebSphere Application Server Integrated Solutions Console (ISC)
From the lefthand navigator select Security/SSL certificate and key management
In the list of rela [read] Keywords: connections
On the IBM Connections SPI's
Wed, Nov 6th 2013 1:25a Mikkel Heisterberg Earlier this week I had a requirement to interact with the IBM Connections user storage from a servlet running within WebSphere Application Server meaning that I needed to obtain the currently logged in users email address from the username (i.e. the principal name in JEE speak). As I saw it there were three options - 1) reproduce the entire Federated Repositories configuration in the servlet config, 2) use an IBM Connections API if available or 3) try and figure out if there was a WebSphere API [read] Keywords: connections
New plugin appdev values for Notes 9.0.1
Tue, Oct 29th 2013 3:36a Mikkel Heisterberg With the release of Notes 9.0.1 we need new values to tweak our configuration to continue developing plugins for Notes. The new values for rcp.base_version and install_id are below. I've also updated the Configure Eclipse 4.2 for Notes 9 page.
rcp.home=framework [read] Keywords: notes
List of OpenSocial fixes in 9.0.1?
Tue, Oct 29th 2013 2:58a Mikkel Heisterberg As reported all over the Yellow-bubble we've now got a Domino 9.0.1 server and a Notes 9.0.1 client to install. All is good and the list of fixes reported by developerWorks is 267. The list however doesn't mention OpenSocial at all. This is sad as this is one of the new features from 9.0 and getting an idea as to what have been fixed would have been nice (plus I know that lots have been fixed).
Hope that IBM will release more information as to what was fixed for OpenSocial. [read] Keywords: domino
Elusive IBM Connections 4.5 CR2 upgrade issue solved
Tue, Oct 15th 2013 3:03a Mikkel Heisterberg We've had a lot of problems trying to upgrade one of our internal test environments
from IBM Connections 4.5 CR1 to CR2. The only symptom was the we were unable to move
past the screen in the update wizard (updateWizard.sh / updateWizard.bat) where we select
to install or remove fixes. The UI would simply refuse to move past this screen -
no message, no log, no nothing. To try "something else" I got the idea to try and run
the update installer in silent mode (updateSilent.bat / updateSil [read] Keywords: connections