Writing SOAP Web Services for use with Proclaim

Imports, export, webservices, custom integration work, 3rd party software plugins etc. Questions about these topics live here.
Post Reply
revellbikes
Posts: 422
Joined: Fri Jun 15, 2012 12:44 pm
Has thanked: 11 times
Been thanked: 43 times

Writing SOAP Web Services for use with Proclaim

Post by revellbikes » Thu Dec 03, 2015 11:50 am

Bit of a broad question this really...

I'm looking for online resources or good books that will give me a good foundation to write a Web Service to be consumed by Proclaim.

I have successfully written a WCF service that connects to an SQL DB using LinQ for basic data retrieval, but fell at the last hurdle with hosting this and then consuming in Proclaim.

From what I understand, it would be best to write a SOAP web service in ASP.NET :roll:

Firstly, are my assumptions correct? Is ASP.NET in fact the way to go for a relative novice?

I'm looking to try get a basic understanding of the technology first, including deploying them and then try apply this to my requirements - a two way SQL Server interaction.

Thanks in advance.

steve
Posts: 375
Joined: Wed Nov 30, 2011 10:20 pm
Been thanked: 75 times

Re: Writing SOAP Web Services for use with Proclaim

Post by steve » Fri Dec 04, 2015 11:02 am

Hi,
quick answer for your final step: google "Web Deploy with one-click Visual Studio ASP.NET Webservice" (link below)
long answer:

I am no expert in webservices but have had success using Microsoft Visual Studio Web Developer 2010 Express to deploy ASP.NET Web Services to internal server running IIS and doing exactly as you are trying - interacting with non-proclaim databases via proclaim WEBSERVICE maths

to quote MSDN on ASP.NET XML webservices: "This topic pertains to a legacy technology. XML Web services and XML Web service clients should now be created using Windows Communication Foundation." but certainly WCF is more complex to get running for a first timer and the debate over which technology to uses rages strong on the internet forums.

If you are just hosting an internal webservice to interact with an SQL database then the ASP.NET approach is probably ok in my book, but it would be worth persisting with getting a WCF service working

I use a number of tools, but Microsoft Visual Studio Web Developer 2010 Express is as good as any (and free) and is set up for easy publishing of your webservice to an internal server running IIS.

try these links below for the basics of getting one running in a dev environment using ASP.NET and e.g. c#. This will spit out a basic webservice endpoint (URL) that you can consume on the dev computer via webpage, and retrieve WSDL with the http://localhost/MyWebService.asmx?wsdl. Proclaim seems to run quicker if you save the WSDL to e.g. your server DOCS directory rather than referencing the live copy each time.

http://www.c-sharpcorner.com/Blogs/1146 ... ing-c.aspx
http://www.codeproject.com/Articles/940 ... Everywhere
https://msdn.microsoft.com/en-us/librar ... s.90).aspx

To deploy your webservice to your IIS server to consume the webservice from anything other than the dev server, have a search for how to configure Web Deploy one click, e.g.
https://msdn.microsoft.com/en-us/librar ... .110).aspx
I fell foul of active directory permissions in the publishing step, resorting to running VisualStudio as domain administrator in order to publish the app to IIS, but I'm sure if you had better knowledge of IIS this could be resolved in a better way.

Be sure that you are confident of the visibility scope of your published webservice on IIS so you don't expose anything you don't want to outside your corporation (or even inside your corporation to inquisitive staff!)

Post Reply