Cooperation between Sun Microsystems and Microsoft probably won’t drastically alter the information technology landscape, analysts and IT professionals say, but it should eliminate some integration headaches.
Last month’s historic agreement between the two computing giants is most likely to create near-term progress in two areas: identification and directory services, and Web services.
Further down the road, look for better communication between servers running Windows and Sun’s Solaris version of Unix. And Sun’s StarOffice productivity package might get better at parsing documents created by Microsoft’s Office software.
“I think the benefits to customers are pretty obvious. It’s going to be easier to mix and match these environments,” said John Fowler, Sun’s chief technology officer for software.
The two companies had been “at a high state of acrimony for a long period of time, and we’ve had to do lots of reverse engineering in our products up to now to make them work with Microsoft products,” Fowler added. “Now we can make products work together in a much more direct way.”
A Microsoft representative would only e-mail a company statement on the matter: “The announcement laid the foundation for closer collaboration at various levels within the companies, though at this point it is very early to speculate as to specific impact this may have on various products, standards and pending benefits as they relate to different customers and their unique needs.”
Directory structures up first
Besides settling pending litigation between the companies, the Sun-Microsoft agreement commits the companies to sharing unspecified technologies and cross-licensing patents, with the goal of improving interoperability between systems.
Initial efforts will be focused on directory structures, identity services and communications protocols, Fowler said, to make it easier for Windows clients to sign on and share data with Sun servers.
“We can do a lot of that now,” he said, “but having an agreement to (go) after some of the more esoteric parts of Kerberos authentication, for example, would help.”
Directory compatibility is at the top of IT administrators’ wish lists. Sun servers use the Lightweight Directory Access Protocol (LDAP) standard, while Windows relies on Microsoft’s proprietary Active Directory protocols. Allowing Sun to poke around with Active Directory should lower the technical hurdles to signing on users between Sun and Microsoft systems, said Brian Conlon, chief information officer for global law firm Howrey Simon Arnold & White.
“I’m pleased at where they’re focusing their initial efforts, on identity management and the authentication and single-sign-on issue,” Conlon said. “If we can have a single facility or service for access control on customer-facing services and portals, that would save some trouble.”
Tony Scott, chief information officer for General Motors’ information systems and services division, agreed that better directory interoperability will have immediate payoffs.
“We have Microsoft everywhere on the desktop, and Sun LDAP directory (on Unix systems), so we have Active Directory and Sun LDAP integration work between the two that we have to do on a one-off, case-by-case basis,” he said. “This is a perfect case where they can do that work for us and make that just plug in and work. We’ll be delighted if they can pull that off. We would rather spend the money on manufacturing or designing a new car.”
Web services in the wings
A little further into the future, Web services is likely to be a focus of Sun-Microsoft cooperation. Microsoft will continue to promote its .Net software for creating Web-based applications. And Sun will keep pushing its Java language, which is incompatible with Microsoft’s .Net.
But, Fowler said, the formats can be made to work together better, building on work being done by the Web Services Interoperability Group.
“We’re looking at how can we go beyond that, whether that’s standards we promulgate together or active cooperation on products,” Fowler said. “We’re still competitors–we’re not here to promote .Net. But we have to realize our customers need to work in a mixed world.”
Gordon Haff, an analyst for research firm Illuminata, said there will continue to be a basic Web services split between Sun and Microsoft on developers tools–Microsoft’s C# versus Sun’s Java–but customers increasingly expect the resulting applications to work together.
“You may very well continue to have multiple ways of developing applications,” Haff said. “The important thing is, can those applications talk to each other on a meaningful level? That’s going to happen at some level because customers are demanding it. They’re saying, and rightly so, that the underlying details of how Web services are implemented shouldn’t really matter that much.”
And the big computing companies need to listen to customers, said analyst Matt Rosoff, as it becomes increasingly difficult to push new technology.
“It’s getting harder and harder with each passing year to explain to businesses why they should upgrade,” said Rosoff, an analyst for research firm Directions on Microsoft. “Sun and Microsoft understand they’re in the same boat. They’re thinking about what do they need to do to really compel upgrades, and interoperability is a big part of that.”
Law firm CIO Conlon said that his company has focused on Java for initial work on Web services but that compatibility with .Net would provide useful reassurance going forward.
“If they can agree on a Web services framework, I think that would be a real plus,” he said. “Our target architecture is a Java-based one–there’s just more third-party support for it…But it would be good to know our choices aren’t going to be limited.”
Solaris waiting on the bench?
Besides general directory and identity improvements, analysts also see a good chance for increased links between Solaris and Windows. Solaris-specific connections to Windows technology would serve Sun’s interests by giving Solaris another distinction from Linux, said Stephen O’Grady, an analyst for research firm Red Monk. And anything that slows Linux is likely to appeal to Microsoft.
“That’s a scenario where the win-win is pretty clear,” O’Grady said. “Sun does need to have more to differentiate Solaris against Linux, and Microsoft wants to play more effectively in higher-end computing tasks.” The ability to function alongside Solaris would be a compelling pitch for Microsoft, he said.
StarOffice is likely to be a thornier issue, O’Grady said. Sun no doubt would like full access to the file formats used by Microsoft Office. StarOffice can read and manipulate Microsoft-generated documents now, but complex formatting or the presence of “macros”–mini-programs used to automate common tasks–can cause StarOffice to choke on a document.
“I do think there’ll be some degree of exchange on Office formats…but I don’t see Microsoft giving up that stuff lightly,” O’Grady said, adding that pressure from the European Union and other regulators could force Microsoft’s hand. “Microsoft isn’t going to just hand over the formats and fall into lockstep with StarOffice, but external factors could play a role there.”
Sun’s Fowler said StarOffice already has solid compatibility with Microsoft Office formats and won’t be a focus of initial efforts between the companies.
Rosoff said Sun is unlikely to push the Office issue, instead treating the Microsoft deal as an opportunity to shore up its server business and back away from desktop ambitions. “I think Sun might look at the desktop business and re-evaluate the viability of that business,” he said. “My suspicion has been Sun got into that business mainly to be a thorn in Microsoft’s side…Now they have a way to back out and refocus on the back-end stuff, where their strength is.”