Both Ed Brill and Gary Devendorf referred to an IBM DeveloperWorks article on integrating Lotus Domino with SharePoint. Something Gary has been doing for quite some time already. So I though I’d have a look to see what’s going on …
… Microsoft has been taking shots at the IBM Lotus Domino product line for years. Not long ago, Microsoft Exchange Server was going to take Lotus Domino’s place in the enterprise landscape. That prognosis fell flat, but Microsoft continues to take aim at the venerable Lotus Domino platform. Microsoft Windows SharePoint Services is Microsoft’s latest collaboration offering; it may be used standalone or combined with numerous other Microsoft products to build applications that attempt to duplicate Lotus Domino functionality. …
Windows SharePoint Services is part of Microsoft Office System (yes, several products) (check here and here). And yes it “attempts” to duplicate Lotus Domino functionality, with very good success I can tell you.
… With SharePoint entering the fray, many customers mistakenly think that they must select it or Lotus Domino; however, the platforms can peacefully coexist and work together. You can easily harness the power of both. This article examines various ways to integrate Domino-based data and applications into a SharePoint environment. It begins with a brief introduction to the SharePoint platform.
The following tools are used in this article:
- Microsoft Windows Server 2003 with SharePoint Services
- Lotus Domino V7.0.1
- IBM Lotus Domino Designer V7.0.1 …
Good approach. It’s a pity the author did not look into Microsoft Office SharePoint Server 2007 and the related updated version of Windows SharePoint Services (Version 3). Simply because this is recognised as a huge upgrade in functionality eliminating a lot of suggested development effort.
Also “peacefully coexistence” is fine, but at the end of the day Lotus Domino and Microsoft Office System are both platforms with a huge overlap in functionality and at the end of the day organisations would want to consolidate / rationalise platforms rather than maintaining multiple platforms with a lot of similar functionality. I do agree that it does not make sence to migrate some (overly) complex Domino applications just for the sake of migration (Gartner Group confirms this).
All in all good tips and some useful resources as long as you don’t forget why you choose the coexistence route instead of migration. Coexistence is not a sustainable strategy for the longer term