COM + Web service: Routing to XML Web services by check box 2

services|web|xml| check box table 1:wko Model supported scenarios

Wko Client Wko Server
VB 6.0 or unmanaged C + + VB 6.0 or unmanaged C + +
VB 6.0 or unmanaged C + + VB. NET or C #
VB 6.0 or unmanaged C + + SOAP V1.1 (described in WSDL)
VB 6.0 or unmanaged C + + Microsoft SOAP (ATL server,soap TK)
C # or VB. NET SOAP V1.1 (described in WSDL)
C # or VB. NET vb 6.0 or unmanaged C + +
C # or VB. NET VB. NET or C #
C # or VB. NET Microsoft SOAP (ATL server,soap TK)
Microsoft SOAP Toolkit V2.0 VB 6.0 or unmanaged C + +
Microsoft SOAP Toolkit V2.0 C # or VB. NET
SOAP v1.1 VB 6.0 or unmanaged C + +
SOAP v1.1 C # or VB. NET

Table 2:cao Model supported scenarios

Cao Client Cao Server
C # or VB. NET (early bound) VB 6.0 or unmanaged C + +
VB 6.0 or unmanaged C + + VB 6.0 or unmanaged C + +
VB 6.0 or unmanaged C + + C # or VB. NET
C # or VB. NET C # or VB. Net

This new COM + Web service applies to the following users:

COM + users that are currently installed with Microsoft®visual basic®6.0 or unmanaged Microsoft Visual c++®com+ applications that require certain activation actions through a firewall. (using SOAP does not exclude access to the same components on the server through DCOM, which the client computer can select.) For these customers, if you want to use SOAP instead of DCOM, using both the client-agent export and the CAO model requires no changes to the client and server applications. You only need to enable SOAP on the server application, export it as a client agent, and then install the agent on the Windows XP computer that you want to use as the SOAP client.
A company that is completely migrated to managed code on Windows XP and Windows. NET Server. COM + WEB Services help you set the remote endpoint at both ends of the connection.
Developers who need to combine and match various services in both scenarios, and developers who write managed server components, or managed client applications with unmanaged server components. In the second case, the developer can take advantage of the COM + Web service to take full advantage of the earlier unmanaged components before replacing them with managed code.
Simple known object (WKO) sample
In addition to providing SOAP support for Linux and Apachein, it is easy to apply COM + Web services to other Microsoft products, such as ATL Server Web services. Simply use Microsoft Visual studio®.net to build, compile, and deploy the default ATL WEB service on the server. The client code that accesses it is as follows (please replace MyServer with the name of the WEB server hosting the ATL Server application, replacing jaltserver with the name of your ATL Server DLL):

Mon= "Soap:wsdl=http://myserver/jaltserver/jaltserver.dll?"
HANDLER=GENJALTSERVERWSDL "
Set c = GetObject (Mon)
WScript.Echo C.helloworld ("COM + Web Service")

The preceding example is a simple description of a new SOAP moniker that is contained in Microsoft Windows XP and Microsoft Windows. NET servers.

Data Publishing
If you only want to provide data instead of using data, simply select a check box, and then enter a value for the IIS virtual root name. To create a complete COM + Web service, follow these steps:

Use Visual Basic 6.0 to create a simple Microsoft Activex®dll and enter the following code:

Function Add (ByVal Value1 as Double, ByVal Value2 as double) as double
ADD = Value1 + Value2
End Function

In the General tab on the Visual Basic Project Properties page, set unattended Execution and retained in Memory, and select Remote Server Files in the Component tab. Build this DLL using the Visual Basic development environment.

After you create a Visual Basic application, you need to register it as a COM + application. Start the Component Services Administration tool to create a COM + application on Windows XP. (In this example, the application is named Vb6soap.) Import the DLL you created as a component, then browse to the Activation tab of the COM + application Properties page, select Uses Soap, enter a soap Vroot (for example, Vb6soap), and click OK (as shown in Figure 1).



Figure 1:vb6soap COM + Application Properties page