IBM Content Manager, Version 8.5      Supports:  Oracle, DB2, Java

Getting started with the CMWebService in a .NET environment

When working with the web services in a .NET environment, you can either generate the XML by using the Microsoft SOAP Toolkit to create low level routines, or you can use the WSDL tool to generate proxy classes.

Toolkits such as the Microsoft SOAP Toolkit provide low-level APIs for generating and exchanging SOAP messages. These APIs allow you to specify an XML document that represents the body of a SOAP message and send the document to the web service URL and returns the reply document as part of the SOAP message. This is a low-level interaction with the web services. This type of interaction allows the most flexibility because the web service interface does not change, even if the XML schema changes.

The disadvantage to by using the web service this way is that you must generate XML messages and deal with low-level APIs for sending and receiving SOAP messages. In this case, the WSDL is used only for specifying the endpoint URL of the web service.

To create XML and SOAP requests, you can write a web service client that uses a WSDL utility. A WSDL utility can automatically process your XML and SOAP requests and responses by representing them as proxy classes. Microsoft provides a WSDL utility that can represent XML documents as C# proxy classes.

To write an application that uses the classes generated by Microsoft .NET's WSDL utility, follow these steps:

  1. Ensure that the following software is installed:
    .NET 1.1 client
    • .NET Framework SDK Version 1.1 from the Microsoft
    • .NET Web Service Enhancements SP1 from the Microsoft
    • .NET Framework SDK, Version 1, Release 1, Hotfix 892202 from the Microsoft
    .NET 2.0 client
    • .NET Framework SDK version 2.0 or 3.0
    • Web Services Enhancements SDK 3.0
  2. Create C# proxy classes from the WSDL and schema files.
  3. Using the C# samples for guidance, program your web service application client by using the C# proxy classes.
    Important:
    When you use the C# samples, it is assumed that the server is local. However, the server and the web service samples can be installed on different machines, in which case you must modify the server URL accordingly.

    In addition, the proxy classes that are shipped with the samples might not match the sample data stored in First Steps. This can happen if the sample data was imported with a fix pack level that is different from the level in which the web services are running. In these cases, the samples will not work as shipped, and you must generate a new WSDL and new proxy classes.



Feedback

Last updated: December 2013
dcmws004.htm

© Copyright IBM Corporation 2013.