Now I am using json output to expose my transformation as rest web service, that's OK, but I m looking for the same thing but this time for a job, is there is a way to expose a job kettle as rest web service.
Related
I have a .net core webapi with some services. This application can also run scheduled tasks in the background using Quartz for .Net and now I need one of those tasks to consume some of the services within the api.
I know it's a bad practice to consume a service from within another, but a scheduled task is not a service. So is this ok? Should I simply use HttpClient to connect to the current running api?
I haven't had much luck finding a way of using the WCFCommunicationListener as well as HttpListner(OwinCommunicationListner) inside same Reliable service. I Want to use two different listeners one that provide the Soap functionality that I can achieve using WCFCommunicationListener and other will simple Web Api consumption that what pretty much OwinCommunicationListner provides. I don't want to use the WcfCommunicationListener for my REST functionalities, I want to consume my REST apis as Web Api.
I will run two of them on two separated services. Using Docker for WCF and Owin for Web API.
If the problem you have is trying to share code then just have a shared library outside of the two services.
An sample on WCF on Docker here https://blogs.msdn.microsoft.com/webdev/2017/02/20/lets-try-wcf-self-hosted-services-in-a-container/
So, I have a WCF Workflow server. This server is consumed by an ASP.NET application. I wanted to use this server as backend. The ASP.NET application needs to perform queries like FindAllClients, GetClientbyId and such.
Question is: What kind of service should process these requests? Should these queries be exposed as workflows? Should a workflow server even process client data queries?
Is there a workflow a workflow involved in FindAllClients()? Sounds to me like something that is not very workflow like so I suspect the answer is no. And in that case what would be the point of using a WF4 service over a standard WCF service?
is it possible with SAP to generate client stubs and transfer objects from a WSDL served by a .NET WCF web service? Or do I have to build my SOAP XML requests manually?
To be more on the point. I still have a WCF web service and the wsdl. I have no knowlege in SAP. So the question is. Is it possible and how can I create client service stubs and the transfer objects in SAP from my WSDL?
It's easy to create an ABAP client for an existing web service if you have access to the URL for obtaining the wsdl file or the wsdl file itself. See this link for an step by step tutorial wich is basically:
1- Generate proxy from wsdl using assitant
2- Use proxy generated in your ABAP program
Regards
You can use the WSDL from the wcf for this. You can get the WSDL as service.svc?wsdl. However at times, some SOAP client generator expect all the definitions of the SOAP/WSDL in a single call. For that you might have to look at the following pages:
http://weblogs.asp.net/pglavich/archive/2010/03/16/making-wcf-output-a-single-wsdl-file-for-interop-purposes.aspx
http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/f03b6e78-ef28-4692-8f19-62d2f2d3bc9c
WCF: how to generate a single WSDL document, without WSDL:import?
I'm trying to develop a Silverlight application that will download a specified file from a SQL database. I'm aware Silverlight can not do this independently, so I am wondering as to what the best way to accomplish this is.
The website that the Silverlight app will run on is asp.net with C# code behind.
Thank you.
An easy way would be to run a web application or service to grab the data. You could have the Silverlight application query the web app for the needed data which would trigger the app to query the database. You would program the web app to return the data in whatever format you needed, JSON, XML, etc.
One way to do this would be to write a simple Asp.Net Handler. The other would be to expose the download functionality via a WCF Service. If this download functionality would be implemented as WCF Rest Service, even non WCF Clients would be able to download the file.