by the time you read this, biztalk server 2004, the third version of biztalk, will have been released. as you can see by the articles in this special issue of .net developers journal, this is a very important product release, and it is poised to have a profound impact on how developers create enterprise applications.
at the same time, 2004 is "the year of web services" - again. unlike the past couple of "years of web services," this time its for real. most of the required standards have been released or at least defined, all the infrastructure pieces are falling into place, and architects and developers are starting to chant the services-oriented architecture mantra.
these two events are going to converge, the result being a very powerful toolset that can be brought to bear on application requirements.
there are three primary ways biztalk server 2004 can be used in conjunction with web services: orchestrating web services exposing orchestrations as web services invoking web services as part of message processing this article will look at each of these topics, and will also touch on how infopath and biztalk server 2004 can work together, which is a natural extension of exposing orchestrations as web services.
overview
visual studio .net and tools for non-microsoft platforms have made it increasingly easy for developers to expose application and business functionality as web services. in addition, developers are increasingly using web services for interoperability, building web services layers on top of their enterprise applications. in the ideal services-oriented ecosystem, applications would expose functionality as services, which would in turn be aggregated and composed into applications in order to meet bus... 下一页