Home > SAP Tips > SAP best practices > Microsoft bets big on Web services
SAP Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 

SAP BEST PRACTICES

Microsoft bets big on Web services


Johanna Ambrosio
12.04.2003
Rating: --- (out of 5)


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


Microsoft is betting that most customers will be moving toward a services-oriented architecture for their application development environments in the not-too-distant future. That bet is in the form of the next generation of Windows, code-named Longhorn, which will integrate middleware and other technologies to help bring Web services front and center.

As things stand now, customers need to set up a whole, mostly separate infrastructure for the development of Web services -- including Microsoft's .NET development tools, middleware like Microsoft's BizTalk, and even software to help manage and track all the Web services that are created and used within one corporation. Some of this software can be used to also develop client-server applications that are not Web services -- but some tools are specific to Web services.

And perhaps most wrenching of all, today's programmers and other IT staffers need to be trained to develop Web services and to use a host of new standards and protocols that they didn't need to deal with in a non-wired world. It's a matter of "thinking" in Web services, rather than in the vein of client-server or other development models.

The goal with Longhorn, industry analysts say, is to integrate Web services functionality so deeply into the operating system that programmers and others will be able to create and use Web services in a more intuitive fashion. A developer will be able to specify what the application should do instead of how it should work underneath the covers.

"Microsoft is certainly the company that grasped onto the concept of Web services first," says Thomas Murphy, a senior program director at Stamford, Conn.-based Meta Group. "And now they're taking it into the operating system." For Microsoft, the starting point is always the operating system, because that's the core of its product strategy, Murphy says. Other vendors are focused on other pieces of the pie.

There are dozens of companies in the Web services space, which has many niches. But in terms of an overall platform, a Web services decision comes down to two major choices: Microsoft's .NET and Sun Microsystems' Java, Murphy and other observers say. The goal is to eventually use Web services to help these two environments interoperate, and that's beginning to happen.

As defined by Microsoft, Longhorn has three major components: Avalon, which is the user interface; WinFS, the new file system that is based on metadata; and Indigo, the communications system that will include middleware to pass messages back and forth among different Web services, their objects and components. So a developer will no longer need to understand exactly how everything works.

One key question is how much Longhorn will incorporate Web services standards like XML Metadata Interchange, from the Object Management Group.

"If you don't subscribe to standards, then Web interoperability becomes limited," says Dana Gardner, a senior analyst with the Yankee Group in Boston. And so he wonders whether Longhorn will be positioned primarily as a means of uniting Microsoft's own architectures -- operating systems, Office applications and the like -- or whether it will allow companies to create heterogeneous systems that work together seamlessly, with the underpinnings hidden from the customer.

"It will be interesting to see whether they use Web services to further assert Windows, or to engender heterogeneity," Gardner notes.

Yet, even with Microsoft pushing Longhorn and its associated .NET tools, it won't be a completely Web services world, industry watchers say. Users will still be able to develop "regular" client-server applications, in addition to Web services.

"For desktop applications, you'll want to use object-oriented because it's tightly coupled," says Jason Bloomberg, an analyst at consultancy ZapThink LLC, in Waltham, Mass. "But for distributed computing, it makes sense to use a services-oriented model. And Microsoft is now saying that the default way of application development is now services-oriented" via Longhorn.

Also, other suppliers will be moving ahead, since Longhorn is still in development. Says Ron Schmeltzer, another ZapThink analyst: "IBM and Microsoft have been amicable over the past two or three years to help make Web services standards happen, but now the gloves are coming off. I expect Microsoft and IBM to be a lot more competitive than in the past. Microsoft will be coming from the bottom and IBM from the top."

FOR MORE INFORMATION:


Rate this Tip
To rate tips, you must be a member of SearchSAP.com.
Register now to start rating these tips. Log in if you are already a member.




Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


RELATED CONTENT
SAP best practices
Increase column width in a transaction screen
Select Text fields: Case-insensitive
Finding BADIs you can use
Updating an RT table entry in SAP HR Payroll -- without the ADDWTE option
Is this the quickest way to find a BADI?
Adding custom fields for retail product comparisons in SAP BW
ABAP Objects in SAP Workflow to provide improved performance
Top 10 SAP tips of 2007
Retrieve BI data with Web Services
Eliminate database read/write times with ABAP shared memory

The Information Architect
Top 10 SAP tips of 2007
Service-oriented architecture: Realizing tangible benefit from SOA in the near term
BCP plans key to emergency planning
Achieving ROI with Web services
SAP RFID Learning Guide
Wireless security: 802.11i promises much, but doesn't deliver all of it -- yet
The SearchSAP.com Glossary Challenge
SAN consolidation reduces costs, boosts performance
Oracle's rose-colored grid vision
Planning for Windows Server 2003

Enterprise SOA (enterprise service oriented architecture)
Getting started with a NetWeaver career
The benefits of EAI
When to choose SOAP, RFC and HTTP adapters
SOA in a nutshell, courtesy of SAP
SAP exec talks partners, platforms and the SAP economy
SAP NetWeaver jobs: What the future holds
Hourly rates of NetWeaver consultants
SAP NetWeaver: Special Report
Demystifying SOA in SAP NetWeaver
Business process platform creation for healthcare, part 2

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
Enterprise Services Architecture  (SearchSAP.com)
NetWeaver  (SearchSAP.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary

DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

HomeNewsTopicsBlogsTipsAsk the ExpertsMultimediaWhite PapersProducts
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Reprints  |  Site Map




All Rights Reserved, Copyright 2000 - 2008, TechTarget | Read our Privacy Policy
SearchSAP.com is a search service provided by TechTarget and is completely
independent of and not affiliated with SAP AG.
  TechTarget - The IT Media ROI Experts