Over the last several months, news has been drifting out of Microsoft about a project that will dramatically change the software giant's e-business solutions. The project, which bears the code name Jupiter, will create an e-business platform that could be attractive to many companies, particularly small and medium-size businesses. In the process, Jupiter could challenge Java-based alternatives from Microsoft's competitors, including IBM and its WebSphere franchise.
To a great extent, Jupiter is Microsoft's response to the challenges that today's e-business software poses to companies with limited IT resources. For such companies, most e-business software is overly complex and requires skills that they do not possess. Much of this complexity is due to the fact that individual e-business products--even those from the same vendor--require different skill sets. For instance, companies often must use one set of development tools for Web application servers, another set of tools for portal servers, yet another set for e-commerce applications, and so forth.
In addition, e-business software products vary widely in their support for industry standards. Even when they do support the same standards, their implementations of those standards can vary in significant ways. This creates further complexity when companies attempt to integrate e-business applications with legacy systems and with each other. Such complexity makes it difficult to integrate business processes across an enterprise, much less integrate processes that involve suppliers and other business partners.
In response to these problems, Microsoft wants to do for e-business software what it did a decade ago for office productivity applications. Just as it entered a market filled with standalone desktop applications and took it by storm with an integrated suite--Microsoft Office--it now intends to transform an e-business software market filled with similar standalone solutions.
The Elements of Jupiter
While Microsoft wants Jupiter to become the Office of e-business software, it realizes that it will take several years and at least two to three versions to make the new suite comparable to its desktop predecessor. As such, Jupiter is both a product and a long-term strategy to integrate key technologies from numerous Microsoft products. These technologies will include the following:
-
A single development environment--One of Jupiter's main design points will be the ability to create all types of e-business solutions--including commerce, portal, and content presentation applications--via a consistent development environment. Naturally, Microsoft's Visual Studio suite of development tools will fulfill this role. Within Jupiter, the two Visual Studio tools that will likely play the most prominent roles will be Visual Studio .NET 2003 and Visual Studio Tools for Office. While the former product is already shipping, the latter tool is currently available in a beta version for download.
-
A single runtime environment for all e-business applications--As developers write applications for Jupiter, they will--at least in theory--be able to deploy them to a single runtime environment. To achieve this, Microsoft intends to integrate the runtime components from its Commerce Server, SharePoint Portal Server, and Content Management Server products onto the Jupiter platform. This would allow users to deploy and seamlessly manage a wide variety of e-business applications through a consistent set of interfaces. These interfaces would provide a single set of services for content management, catalog management, personalization, and Web site management across all applications.
While Jupiter will act as a convergence point for Commerce Server, SharePoint Portal Server, and Content Management Server, it is unlikely that Microsoft will discontinue these products. Just as the software giant continues to sell individual Office products, so it will continue to offer its server products on a standalone basis.
-
An integration engine for applications and business processes--Microsoft wants to position Jupiter as the preeminent platform for Web-enabling legacy applications and integrating business processes that involve both employees and automated systems. To deliver these functions, Microsoft will make BizTalk Server 2004, which the vendor intends to ship in the fourth quarter of this year, a core component of Jupiter. The application integration product includes improvements in the areas of business process workflow management, support for XML Web services, and integration with Microsoft Office and Visual Studio .NET.
-
Integration with Office applications--Naturally, Microsoft wants companies to use Office applications as the interfaces of choice to Web applications built on Jupiter. To encourage such choices, Microsoft is already developing linkages between the products in Jupiter and Office 2003, the next version of the desktop suite, which will likely ship in the fourth quarter of this year. Office 2003 features XML Web services that will link Office applications with each other and with Windows server products, including those slated for inclusion in Jupiter.
Clearly, Microsoft's plans for Jupiter are ambitious ones. However, does the company have the right stuff to make its latest brainchild a giant among e-business platforms? I'll tell you what I think next week, when I discuss Microsoft's strategy at greater length and assess what Jupiter could mean for mid-market customers and the IT vendors who serve them.
Lee Kroon is a Senior Industry Analyst for Andrews Consulting Group, a firm that helps mid-sized companies manage business transformation through technology. You can reach him at
LATEST COMMENTS
MC Press Online