After some more investigation, it looks like the DSC web service proxy that I'm using is not correctly generated (or the wsdl is not correct ?). In fact, instead of having DataSet classes used, it should rather be DSResource classes that should be generated and used in the proxy but they are not ! I did generate the proxy (.NET 4 using svcutil) for the DSC service in the same way as I generated the QMS API (QMSBackendService) which is working fine. Can someone explain how to use the DSC services and how to generate a working proxy ? I did not find any explanation or examples :-(
We would also find this immensely useful. Our QlikView infrastructure is an entirely automated setup process with the exception of the DSC and QVWeb configuration because of the omission of these methods from the QMS API.
From our investigation the following methods exist on the IQMS interface but are not marked with the [OperationContract] attribute and so are not available to consumers of the QMS API. This is preventing us from completely automating the setup of a new QlikView environment using this API.
The following methods would also make development of some internal tools much simpler for us (we currently have to use QvClient to make them):
I believe the crux of this change involves adding the following three lines above the declaration of each of the mentioned methods in IQMS.cs.
It would be very much appreciated if someone from Qlik would be able to comment on this.