The client generation from WSDL tool cannot handle all WDSL files. It is advisable to test the WSDL using a 3rd party tool like SOAPUI to ensure that it is valid prior to trying to generate a COBOL client for it. If it does import into SOAPUI and you can call the web service correctly then you should open up a support incident with Customer Care and we will review the WSDL file to see why it is failing. It is much easier to call a WCF service from a managed .NET client than from a native client. In a .NET COBOL client you can simply add the service reference to your project and then you can instantiate the service and invoke its methods. I had covered this in a previous thread in this forum, where you can create a managed .NET COBOL client that calls the WCF service and then register it for COM Interop so you can call this client from native code using the OLE support. Please look at the thread here : and here Thanks:
↧