I'll write this up as a position paper, but I just had to get it off my chest...
When people evaluate CoexLinks
, they often ask the question, "Why can't we just use the Exchange Connector
? It does the same thing."
There are three answers, and I am never sure which to give first. Here are the three answers, and you tell me which is most compelling:Exchange Connector is Not Supported
This may seem a pretty blanket assertion, but the following three Microsoft technotes pretty much describe the story:XFOR: Exchange 5.5 SP2 Notes Connector Does Not Currently Support Lotus Notes R5 Server
(documents the lack of support for Exchange 5.5 SP2, the most common configuration of Exchange 5.5. and Notes/Domino R5.x)XCON: Microsoft Support Policy for Exchange Server Coexistence with and Migration from Lotus Notes/Domino 6.x
(documents the lack of support for Exchange 2000 and Exchange 2003 with Notes/Domino R6.x)XFOR: Lotus Notes Client Versions That Are Tested with the Exchange Notes Connector
(documents that even in an unsupported, use at your own risk configuration, the last version of Notes they even tried out was Notes 5.0.10. Since ND6 isn't supported at all as described above, this is not likely to change.)Exchange Connector is Architecturally Weak Solution
This is also a fairly broad assertion, but it is not one Microsoft would likely argue with. They built the Exchange Connector as a way to bridge the gap while people moved to Exchange. Since few people are moving that way these days, they have abandoned the effort. In any case, here are just a few of the myriad design problems:
1) Requires an R4 client running on an Exchange server. The Exchange Connector requires an R4 client, yup R4 (see this technote
and search for "4.62") running on the Exchange server. So, an unsupported version of Notes running as client software on a server is the basis for this product. There are many by-products of this poor design, not the least is this technote:XFOR: Exchange Notes Connector Does Not Send HTML
(documents the issue that if any user has their mail set to go out as MIME, the e-mails will simply be discarded, which is not surprising, since R4 didn't support MIME in messages)
2) Single point of failure. The Exchange Connector must be set up so that all mail travels through one connector on a single Exchange server. There is no provision for load balancing, different routing based on MIME e-mails, or anything else that would allow a larger organization, or a smaller one with diverse needs, to split up the mail. If the rickety Exchange 5.5 server (only version supported) fails, all your mail routing stops.
3) Too many links in on document cause crashes . The Exchange Connector must be set up so that all mail travels through one connector on a single Exchange server. There is no provision for load balancing, different routing based on MIME e-mails, or anything else that would allow a larger organization, or a smaller one with diverse needs, to split up the mail. If the rickety Exchange 5.5 server (only version supported) fails, all your mail routing stops.
Besides this, take a look at Microsoft technotes documenting many other issues: 253712
, etc.Exchange Connector Provides Very Little Flexibility Compared to CoexLinks
The Exchange Connector solves, or tries rather badly to solve, I should say, one problem in one way. When it works correctly, it replaces doclinks with NDL attachments. It does not accurately mark where the original link was, so if there were multiple links, a person may click on the wrong NDL link. It does not provide disclaimer support so that recipients may not know why there is an indication that there is a link, but there is only an attachment. It does not provide the ability to create Notes URL links. It does not provide the ability to create Web URL links in case the Notes client is not available and a web interface has been added. It does not allow limitation of the number of attachments for mail systems that limit attachments.
I could go on and on, but I'll save it for the white paper. Let me know if you want to see more, and I'll happily provide an early copy before it is posted.
Copyright © 2004 Genii Software Ltd.