Several weeks ago, I promised a reader [EDIT: Read the comments here.] to discuss why I would think twice before adding a TaskSpace interface to a solution that already included an eRoom interface. Aside from the obvious that TaskSpace is a brand new interface and could most likely use service pack or two, I am always hesitant to provide too many interfaces into a solution. There are times for it, but it is important not to add them just because you can.
SharePoint
Microsoft SharePoint, what more is there to say?
Standardizing Authentication
Been a busy week on the ECM standards front. There has been a lot of discussions going around. I’ve been silent on the topic as I’ve been focusing on learning more about SAML and XACML so that I can respond to James’ question. Plus, the dialogs are going great and I haven’t needed to keep them going.
I am not ready to give James an answer on XACML, yet. I feel I am ready to start a dialog on SAML though.
Choosing a Target for Standards
Reaction to my previous two posts revealed two simple things about the Universe. Enterprise Architects want/need ECM standards now. Enterprise Content Management people don’t think that the ECM world is ready for them. They are both right, so let the fighting begin.
Brian “Bex” Huff wrote about the lack of useful ECM standards and how writing a standard to the lowest common denominator would leave it all but useless. He raises some excellent points, but I think there is an important thing here. If an ECM system doesn’t support a minimal level of functionality, is it really Enterprise worthy? If it isn’t ready for the Enterprise, do we care if it can’t integrate with everything else? I’m thinking No on both counts.
SharePoint vs eRoom, or Microsoft vs the World?
I’ve been discussing this topic of late. I haven’t been able to dive into SharePoint since my last post, but I have had some rather interesting things come up on this topic and wanted to share.
Josh Maher came up with quite an interesting view in his blog. SharePoint is for Microsoft people, and eRoom is for everyone else. His arguments seem sound until one detail comes forward, eRoom only works on Microsoft platforms. I don’t want to address the future here, just the present. eRoom requires:
- A database. SQL Server 2000, SQL Server 2005, or an embedded SQL database that installs onto windows.
- Windows Server 2000 or 2003 with Internet Information Services (IIS) installed.
Doesn’t sound very anti-Microsoft to me. The difference here, as Josh points out, is that SharePoint works closely with all the latest Microsoft products. However, the latest SharePoint server also needs those newer products to fully garner all of the benefits. Microsoft wants you to upgrade your Office suite. That is more money in their pocket. When eRoom makes a release, they don’t typically require you to have the latest version of all the integrated products.
SharePoint and EMC
One of my favorite Documentum bloggers outside of yours truly, Johnny Gee, has been blogging of late on SharePoint and Documentum. He ran a three part series comparing the two. Yesterday, he posted an entry comparing SharePoint and eRoom. This was even commented upon by an Enterprise Architect blog that I regularly read by James McGovern. I read the entry, and it has drawn an interesting, and very dead-on, observation. The latest post has a very decided pro-eRoom stance. In Johnny’s defense, he was just posting some observations from a reader and not taking credit. One the other hand, it is a very biased view of the world.
First, let me say that I do not have the depth of knowledge to take up SharePoint’s defense in detail. I am also not as inclined to do so being a little pro-EMC. However, I will make two statements about eRoom and SharePoint:
Word of Pie 