How Microsoft Is Filling Out .NET with a Content Management Strategy
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
One of the missing components of Microsoft's .NET strategy had been content management. With the inclusion of Content Management Server and the strength of BizTalk Server with XML integration expertise, the Microsoft solution is coming together well.
Why Microsoft Purchased nCompass
When the entire server lineup in the string of product introductions Microsoft has scheduled for the launch in 4Q 2001 and 1Q 2002 are compared, there isn't a single dedicated server to content management. What further drove Microsoft to acquire nCompass was that Sun Microsystems did an outstanding job of encouraging developers to have their applications run on the Solaris operating system. With the big push Microsoft has planned for a solutions-oriented sell into the Global 2,500, not having a Content Management Server product—while competing with the likes of IBM with WebSphere and the many applications based on Sun's platform—was unthinkable. The challenge for Microsoft with the acquisition was to get the majority of developers from British Columbia down to Redmond, Washington, and have them settled in before the major introduction of the .NET Solutions Strategy, scheduled for sometime in 4Q 2001. The issue of Windows XP was secondary; nCompass has been a long-time beta tester of the new operating system, and was well-conversed in what needed to be done to Content Management Server to make it run as efficiently as possible.