none
Architecture: Windows workflow manager with ASP.NET Web API RRS feed

  • Question

  • Hi 

    Intro:

    Windows workflow manager 1.0  hosts Workflow applications (Declarative or Imperative) in multi-tenent environment and exposes Workflow applications as REST service. Workflow applications are built on top of windows workflow foundation.

    Client application (MVC, Web Forms, WPF etc) can invoke workflow applications as REST service through WF Manager

    Workflow applications run the automated business logic and return the output to the caller (client). Based on the workflow application out come data returned to the client by invoking ASP.NET Web API service.

    In the investigation, MSDN provided samples and other community resources Workflow applications are NOT returning actual data that should returned to the client. WF application simply returning a Web API service URI to the client after running the business logic(workflow). 

    Can you please suggest best practice here 'whether WF application has to return the data by invoking the ASP.NET Web API service' where client invokes the WF application?

    In the investigation so far 'WF application(NOT only Declarative BUT code activity as well) failed to return the data that has received from Web API service as it is'. of course when the data is NOT manipulated in WF application, end client can directly invoke the ASP.NET Web API service to obtain the data based on the WF application out come, which involves two service calls (One to the WF service and second call to Web API Service).

    Issue:

    It is feasible to implement WCF service with WF where WCF exposes workflow as service and returns data based on the workflow out come. 

    Now ASP.NET Web API has to replace WCF - there is no template support such as Web API - WF available.

    As the WF application (through WF Manager) can not return collection of JSON objects that are returned from the Web API to the client, the archiecture is changed to 'Web API invoking the WF application, based on the WF business logic out come return the actual data from database to the client. Here Web API returns the data based on WF out come.' This is tested successfully.

    Your help and architectural suggestion with best resources greatly appreciated on this.

    Regards,


    Apriori algorithm [association rule]

    Wednesday, July 31, 2013 9:45 PM

All replies

  • Are you saying that the output of a WCF Workflow service under Workflow manager is a URL to a WEB API Service that ultimately returns workflow output, if any?

    It doesn't seem like there is any advantage to using Workflow Manager, on premises, if that is the case.

    Why not simply use a Web API to call a SOAP Workflow Service?

    Sounds much simpler


    Stanley Tonkonogy

    Tuesday, July 14, 2015 11:57 PM