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.
Writing command line scripts with node.js
Mon, Feb 17th 2014 11:20p Mikkel Heisterberg Found this little tip this morning to make it easier to use command line scripts written in node.js. Instead of having your node.js file(s) and invoking it using "node myfile.js" on the Mac you can simply do the following:
At the top of the file as the first line add: #!/bin/usr/env node
Make the file executable using chmod +x myfile.js
Now the file is usable by simply using myfile.js. [read] Keywords: mac
Year in review 2012 (not a typo)
Tue, Dec 31st 2013 5:12a Mikkel Heisterberg Boy 2013 was a busy year. In fact it's been so busy and I have been so bad at blogging that I never got around to finish my year end review for 2012. In a draft blog post I had the following:
"2012 was a busy year - maybe the busiest year I've had in a long time. Besides numerous customer projects here in Denmark I've also been involved in a number of international projects and traveled more than ever before. I went to the US twice, Japan twice, Australia once, and to too many European cou [read] Keywords: connections
My IBM Connect 2014 sessions
Tue, Dec 31st 2013 4:54a Mikkel Heisterberg It's been a very busy fall and christmas for me so I haven't bragged about being chosen to speak at IBM Connect 2014 on my blog besides creating a new static page for the event that will - eventually - sum up what I'm up to at the event. I am fortunate enough be have been selected to speak in two sessions - one with my good buddy Mat Newman (aka Yellow Man) and one solo. Below are the session IDs (probably subject to change), the session titles and the abstracts.
BP301 An Introduction to W [read] Keywords: connections
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