CA Client Automation

  • 1.  CA DSM - Web services, connect to the API.

    Posted Feb 04, 2011 05:00 AM
    Hi,

    Dont know if this is the right forum, but I'll give it a try anyway.

    I am trying to open a connection via the CA DSM Web Services API. I am using Visual Studio 2010 and c#. So far I have accomplished to add a service web referense to : http://server/UDSM_R11_Webservice/wsdl and it generates a stub. But when I try to use the proxy/stub class, in the response i.e. using wsDSM.Login("login","password","manager") it throws an exception that it cant handle the response with no Content-type SOAP. I have checked that there is a function for handling the "LoginResponse" and it uses base.Channel.Login().

    Visual Studio generates three classes (I think it uses svcutil.exe)
    DSMWebServiceAPI (interface)
    DSMWebServiceAPIChannel (interface)
    DSMWebServiceAPIClient (class)

    The only documentation I have found to accomplished this is here: http://server/UDSM_R11_Webservice/help . Where you can find examples using Java .But it is diffucult to understand and translate it for implementation in .NET. And trust me I have searched everywhere on the Internet. It is not easy to find any good reference or documentation about this.

    Can anyone here help me out to come any further with this? Thanks in advance!


  • 2.  RE: CA DSM - Web services, connect to the API.

    Posted Feb 14, 2011 09:50 AM
    Thjs was a lot more problematic than I first thought...

    .NET and Java Axis is not compatible in many ways, although SOAP is interopability with any language. Seams like it's problem with namespace's, httpbinding, etc ....

    I am trying to figure this out.

    Looking for examples to implement and consume an java axis web service in .NET.

    sigh


  • 3.  RE: CA DSM - Web services, connect to the API.

    Posted Mar 18, 2011 02:57 AM
    up


  • 4.  RE: CA DSM - Web services, connect to the API.

    Posted Aug 24, 2011 10:15 AM
    Hi,

    I had problems after going to ITCM 12.5 and I got a SOAP content header problem.

    I thought it had been changed to SOAP 1.2 so created a custom binding with a message version of SOAP12. This failed.

    I then went to the web server hosting the web interface (in this case IIS7 on 2008).

    On the directory for the Web service add a HTTP response header called 'content-type' with a value of 'text/xml'.

    This now works fine for me.

    Regards.

    Chris Jackett.