Despite Lotus Connections being a great option for organisations looking to deploy a social software platform, it does not include any wiki functionality. This is going to be remedied in a Summer release, but for organisations looking to get started now it remains a significant functionality gap. To compensate, IBM have worked with Atlassian Confluence and Socialtext to integrate those wikis into Connections.
At Headshift, we’ve been looking at how this integration works, and how organisations can use Confluence and Socialtext within Connections. The screenshots below use Confluence, although it works very similarly with Socialtext.
Once the integration is set up (no easy task, you may need some help!), you are given the option of creating an associated wiki when you create a community, shown below.

Once the Community is created, two new areas are added to the Community. A link to the wiki space itself and the feed from the wiki. This wiki has been created for us automatically by Confluence.

If we click on the “Confluence Wiki” link, we are taken directly to our new wiki in Confluence and can add some content.

We now see that content in the Community.

So far, so good, but we’ve also found some limitations.
- Both the wiki and Lotus Connections must use the same LDAP.
- You can only create a new wiki, you cannot use an existing wiki. A workaround could be to create your Community and move content from an existing wiki into your new one, but that is far from ideal.
- When you click on the “Confluence Wiki” link, it takes you directly into the Confluence UI, leaving Connections behind. The only way back is the back button – it may not be obvious for novice users how to return to Connections.
- There is no single sign-on. Even though the two systems use the same LDAP, if you click on “Confluence Wiki” you need to sign in before you can edit any content.
There is a more serious issue in how content is presented in the Community, especially once you get to a certain level of complexity.
Here is a screenshot of a basic structure of our wiki in the Enterprise 2.0 community

You can see that there are three children. However, when shown in Connections they appear at the same level as the Home page. Connections shows a list of all pages, and doesn’t show page hierarchy.

Further the links highlighted above do not resolve correctly. They refer to the Connections server, not the Confluence server.
It gets worse when you add images / attachments…

Translates to:

So, our recommendation is that to display simple wiki content, this approach works, but once you go beyond the basics there are some limitations. We’d be more than happy to take a look at your Confluence and Lotus Connections environments, and help plan the best approach for you – so get in touch if we can help.
If you enjoyed this post, make sure you subscribe to my RSS feed!



















February 23rd, 2009 at 5:17 pm
Jon, thanks for the summary!!! If you run Confluence on WAS, can you get SSO then ? Also, I recently used the information in this link to enable SSO between Confluence (which was running on Tomcat and using a Domino LDAP) and Connections (running on WAS and pointing to the same Domino LDAP): http://www.automatedlogic.com/domblog.nsf/dx/DominoTomcatSSOIntegration
I also made a customization on the Confluence side to quickly enable the person card there. That way, users would have an easy way to come back. If you are interested, let me know.
Hope this helps.
February 23rd, 2009 at 5:20 pm
I tried installing Confluence on WAS, but gave up after I got a few errors!
February 23rd, 2009 at 7:28 pm
Luis/Jon
We have tried this so the answer in a nutshell is not out of the box. Unfortuntley the plugin really needs to be open sourced to allow it to work for various customer environments. As we use Siteminder as our single sign on solution, you can SSO onto Connections and Confluence, but the connector just barfs at you.
Also, when you create new wiki’s from Connections, it creates some hideous group names in Confluence.
Jon – installing Confluence on WAS is a piece of cake mate
although give me Tomcat/Resin any day…I think I have a few blog posts on this, so you can check them out.
February 25th, 2009 at 9:53 pm
Jon, thanks for the detailed walkthrough of using the IBM Lotus Connections integration with Confluence. I’m sorry you had some difficulties with our Partner’s product.
I wanted to point out that we are enthusiastically expanding out our range of Connectors with critical applications that users use everyday in their jobs and ensuring that the experience is useful and easy to use. I definitely encourage you to have a look at our Office, Widget (connects to a huge range of web resources and brings that content into Confluence), and Sharepoint Connectors.
We will get your excellent feedback back to our partner IBM so that we can improve the aspects of the Lotus Connector that you pointed out need improvement.
Adnan Chowdhury
Confluence Product Manager
January 25th, 2010 at 2:32 pm
[...] Connections as a wider social networking tool. We’ve already looked at one integration point, adding Confluence wikis to Connections communities, and were disappointed with the results. This becomes especially tricky now that Connections ships [...]