calling Workflow from .NET

[Former Community Member]

Hi,



Here are the details of the scenario I would like to accomplish:



* The starting point is a portal developed with .net

* From the portal, the user will click on a link to render a pdf/html form

* .net will take care of calling the workflow in the proper way (I need to find out how)

* Adobe workflow (using the Render Qpac) will render the form and return result to our portal server and then to client browser.



The difficult part of this scenario is the calling of the workflow from the .net portal. I was wondering if it is possible to accomplish that since most of the example in the documentation are launching the workflow from the Form Manager (which I am not using here).



I know that the rendering could be done with the Forms .net api, but for now I would like to use a Workflow. So my question is how can I interact between .net and workflow. Can this be done easily?



Thanks for your help.



Fred.

[Former Community Member]

If all you want to do is start the workflow and receive the output from it, you could make the workflow web service enabled and then invoke the web service in your .Net app. The WSDL for the workflow would be located at http://serverName:port/services/process-type-name?wsdl.



Btw, if the output of the workflow is a PDF it will be sent as a SOAP attachment.



Chris

Adobe Enterprise Developer Support

[Former Community Member]

Thanks for the reply.<br /><br />I have exposed my workflow as a webservice. From .net when I make a web reference to the workflow wsdl and try to compile my project I receive the following error:<br /><br />Unable to import binding 'RenderingFormSoapBinding' from namespace 'http://adobe.com/workflow/services'.<br /><br />This is the header of the wsdl:<br /><br /><?xml version="1.0" encoding="UTF-8" ?> <br />- <wsdl:definitions targetNamespace="http://adobe.com/workflow/services" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://adobe.com/workflow/services" xmlns:intf="http://adobe.com/workflow/services" xmlns:ref="http://ws-i.org/profiles/basic/1.1/xsd" xmlns:tns1="http://DefaultNamespace" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><br />- <!-- <br />Generated by Adobe Workflow Server v7.0<br /> --> <br />- <wsdl:types><br />...<br /><br />My system is running on a network completely disconnected from the internet. Could this be the source of the problem (loading binding from adobe site)? <br /><br />Thanks.<br />Fred.

[Former Community Member]

This only seems to happen when you have a workflow variable of type document as either an input or output variable for the workflow. One other thing to note is that in the wsdl:types area the following line appears:<br /><br /><schema elementFormDefault="qualified" targetNamespace="http://DefaultNamespace" xmlns="http://www.w3.org/2001/XMLSchema"><br /> <import namespace="http://ws-i.org/profiles/basic/1.1/xsd" /> <br /><br />We are wondering if the problem is because the machine is on its own network and isolated from the internet? Can anyone confirm if this is a requirement to be connected to the internet to do things like this? Does anyone know if there is a way of circumventing this? <br /><br />In the error above "unable to import binding 'RenderingFormSoapBinding' from namespace..." RenderingForm is the name of the workflow that was exposed as a web service. A colleague of mine wondered if there was a way to tell the .Net environment from not validating the schema but unfortunately my knowledge of .Net is not the best. Any help is appreciated.<br /><br />Dave