COM + Web service: Routing to XML Web services via check boxes (turn)

services|web|xml| check box COM + Web service: Routing to XML Web services through check boxes
John Noss and Jonathan Hawkins
Microsoft Corporation
November 2001

Summary: COM + WEB Services has new features that you can integrate with Microsoft. NET Remoting and implement the checkbox activation of XML WEB Services Publishing through a SOAP for COM + component. This article introduces a few examples of basic interoperability, configuration, and managed and unmanaged COM + components (XML Web servi on Microsoft Windows. NET Server and Microsoft Windows XP Professional) CES release) deployment.

Directory
Brief introduction
Simple known object (WKO) sample
Simple client-activated object (CAO) example
Transactional Components Sample
It's all just beginning.
Brief introduction
COM + WEB Services has new features that you can integrate with Microsoft. NET Remoting and implement the checkbox activation of XML WEB Services Publishing through a SOAP for COM + component. This article introduces a few examples of basic interoperability, configuration, and managed and unmanaged COM + components (XML Web Ser on Microsoft Windows. NET Server and Microsoft®windows®xp Professional) Deployment of the vices release). The example also introduces several new features that enable clients running Windows XP to access XML Web Services on a remote server.

When developers use. NET Remoting and managed code to refine existing unmanaged COM + server and client code, these features help them to leverage and simplify the migration process. During the testing phase of the. NET Framework, a number of users asked how to configure. NET Remoting for simple, cross-computer activation operations. The solution for COM + WEB services is to automatically configure both the server (Microsoft Windows. NET Server) and the client (Microsoft Windows XP Professional) computers to use the. NET Remoting to Provides SOAP to replace DCOM.

Microsoft Windows XP and the Microsoft. NET Framework are the two most important software releases this year. Both are designed to streamline processes and improve the capabilities of software developers, so it is natural to use both products and leverage their strengths to provide an integrated, easy-to-use solution. COM + WEB service provides an easy way to publish COM + components as XML Web services, as well as new integration features for accessing XML Web services from client computers. You can learn about its easy-to-use features from the following Microsoft Visual Basic scripting Edition (VBScript) examples that determine the current temperature of the Alaska Fairbanks. Run this example on Windows XP (installed. NET Framework) or on Windows. NET Server:

Set soapobj = GetObject
("SOAP:WSDL=HTTP://WWW.XMETHODS.NET/SD/TEMPERATURESERVICE.WSDL")
WScript.Echo "Fairbanks temperature =" & Soapobj.gettemp ("99707")

In the above example, the server is an Apache SOAP server running on Linux, but you can also use any SOAP V1.1 server with a standard WEB service Description Language (WSDL) description feature.

Note: If the "Server not Found" error occurs, you will need to manually configure the firewall settings in the Internet options in Control Panel.
One of the advantages of using SOAP as a communication protocol between computers is that it increases the kind of computers that can interoperate.. NET Remoting has the following two basic operational models:

Known objects (WKO): Wko is the most common XML Web Services model supported by the SOAP V1.1. It allows you to work with other computers running SOAP V1.1 compatible stacks. Servers and clients can be non-Windows servers running Apache SOAP and Pocket PCs running Pocketsoap, or windows-based servers and clients. The only requirement is that the description feature that is compatible with the WSDL 1.1 version must be installed on the server in order to generate the appropriate proxy. This agent was generated at run time and no user intervention was used for the first time using a WSDL moniker.
Client-activated objects (CAO): The CAO provides a richer development environment, including stable and persistent connections. Rather than a typical XML Web Services model, it is more like the DCOM model, but requires a version of the. NET framework installed on both the server and the client.
COM + WEB Services can use the Wko and Cao two activation models, and all server applications can provide Wko and Cao endpoints. By combining activation models, XML Web Services, and. NET Remoting, developers can easily combine and match managed and unmanaged clients and servers. The following table shows examples of the scenarios supported by the two activation models.