would anyone know of a WCF testing tool, much like soapui, that can be used to make calls to federated endpoints? If there is know such tool, any ideas on how to call these services would be appreciated. One idea i had was to create a basic http binding endpoint for every service but this would produce a lot of configuration overhead. Is this or creating my own tool to call the services the best approach?
Thanks,
Andy
Related
I have to use a number of functions provided by a government web service. I have no idea what they used to implement this service. Could have been COBOL for all I know.
My problem is that I've been trying to access this service using the security features provided by WSE3.0 but have had no luck. I'm consistently getting errors regarding the certificates.
After some research I've realized that WSE3.0 is essentially defunct and I should be using WCF. But, I'm only writing a client and most literature seems to refer to the services themselves.
Is there even such a thing as using 'WCF' to write a client? Should it matter which I use?
Thanks in advance.
Sure, WCF is a great choice for writing a web service client. Here is how to create the client ("add service reference"). After this you need to create the binding (just like in the service samples).
I am going to need a web service that receives a string via HTTP POST and processes it without any response to the client. However, since I'm not the one making the client (which will be cell phones) I am unable to use a generated client class to consume the service. The service would also need to be self hosted in a regular Windows service, if that matters.
As I'm not too experienced with web services nor WCF, I am frankly unsure if I can or should use WCF for this, but as it's the only type of web service I'm at least a little familiar with I figured it would be great to start out with one if at all possible.
I've been googling around quite a bit but haven't been able to find any good references to this, so I'd also be very grateful if someone has a link lying around to someplace that discusses it.
I think you need WCF Restful service with one way operation. Following link might help you:
A Developer's Guide to the WCF REST Starter Kit,
I am writing an test application to do a load test on my existing WCF service.
There can be numerous clients calling the WCF service.
How do I write code to generate several clients calling the WCF service.
Any lead or forum or blog will immensely help.
Thanks
I have not used it myself, but the WCF Load Test might do the trick.
You can load test web service using SOAP UI. Free Version is here
Folks,
I'm building a pretty standard workflow that I want exposed via a WCF endpoint - I'm using the "WCF Service Application" project template and I've got a .xamlx service. This is a very simple document interchange workflow service - I want consumers to POST me a blob of XML as the body of an HTTP post (with HTTP headers containing authentication tokens). In response, these consumers will get a blob of XML containing the reply. 2 goals for me using REST/POX here are the document/message-based nature of the interaction AND I want to make client development easy for non-.NET environments (especially limited environments like Silverlight and iPhone).
I don't really see how to make this possible using out of the box features (unless I'm missing something). Does anybody know how to create a RESTful (or even REST-ish, I'm not picky) endpoint for a WF4 service-hosted workflow? Any info leading in the right direction here would be great.
There is an unreleased item on CodePlex to cover this, which includes source code. Also see this SO answer which contains another idea for achieving this.
If you'd like to see the CodePlex activity released, please up-vote the UserVoice request.
Using a REST Pass-Through Service
As #Maurice mentions, you can also treat the WF service as a back-end service and expose a REST service that simply calls through to the WF service.
This method is a bit clumsy, but has the advantage that it doesn't use anything unreleased or really complicated.
If the back-end service runs on the same machine as the REST service (which is probably what you'd do), you should expose the WF service using the named pipes binding. This binding is fast, but only works when the caller and callee are on the same box.
A further thought: your REST pass-through service is blocked while the back-end service is being called. If your WF service is not very fast, you'd benefit from making your REST service asynchronous so it doesn't block a thread pool thread while the WF service is being called.
There are no out of the box activities that will allow you to use REST with WF, the Receice is pure SOAP.
You can either build a custom REST Receive activity and use that with your workflow. Depending on your needs this is going to be quite a handful to a lot of work. The easy option is use use a standard REST WCF endpoint and convert the REST data to SOAP, pass rhe request on to the workflow, and do the reverse on the result message.
I'm developing a new set of web services at my company.
My manager asked me to provide a greater level of security for this, as the web services will handle sensitive informations.
I've searched the net for resources about how to secure an web service and the two runner ups are WSE3.0 and WCF.
But I have no idea which one is the best option to choose from.
My requirement stipulate that some of the web service must be called by non-.NET environment, so how to proceed?
Which one is the best in such scenario?
If you have the luxury of doing new development, DEFINITELY go with WCF!
It offers much more functionality, much more options for security, bindings, and way more extension points should you need to tweak your system.
WCF also support way more industry-standard interoperability scenarios than anything else before, so you should be more than covered in this area, too.
Here are a few articles specifically on WCF security:
Fundamentals of WCF Security
Programming WCF Security
WCF Security Guidance
No question here - it's a slam dunk - go with WCF !!
Marc