@ManuToivanen,
I'd recommend using SoapUI to test the framework. It has better support for working with Soap web services than Postman does in my experience. Within SoapUI, create a new Project and then enter the URL of the Process Dispatcher VBO's WSDL (eg. http://localhost:8181/ws/ProcessDispatcher?wsdl). From there you should see 4 available actions: CleanUp, GetProcessStatus, Initialise, and RunProcess. You can ignore CleanUp and Initialise unless you're trying to manually manage your bpInstance information (which I don't recommend).
Once you've got you project created, click on the RunProcess action and expand it. You should see a Request1 entry. Double click that to open to definition window. You'll see the Soap request envelope definition. You'll need to fill in some values. Here's an example of one of mine:
In the pop-up, you'll select Basic and then enter the username and password for calling the Soap service. After that, you should be able to press the Submit Request. If the request successful, you should see a response similar to this in the response window:
Cheers,
Eric
I'd recommend using SoapUI to test the framework. It has better support for working with Soap web services than Postman does in my experience. Within SoapUI, create a new Project and then enter the URL of the Process Dispatcher VBO's WSDL (eg. http://localhost:8181/ws/ProcessDispatcher?wsdl). From there you should see 4 available actions: CleanUp, GetProcessStatus, Initialise, and RunProcess. You can ignore CleanUp and Initialise unless you're trying to manually manage your bpInstance information (which I don't recommend).
Once you've got you project created, click on the RunProcess action and expand it. You should see a Request1 entry. Double click that to open to definition window. You'll see the Soap request envelope definition. You'll need to fill in some values. Here's an example of one of mine:
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:blueprism:webservice:processdispatcher">
<soapenv:Header/>
<soapenv:Body>
<urn:RunProcess>
<bpInstance xsi:type="xsd:string">auto</bpInstance>
<UseSSO xsi:type="xsd:boolean">False</UseSSO>
<BPCredentialName xsi:type="xsd:string">Blue Prism</BPCredentialName>
<ProcessName xsi:type="xsd:string">CalcWSProcess</ProcessName>
<ProcessParameters xsi:type="xsd:string"><![CDATA[<inputs><input name='taskId' type='Text' value='12345' /></inputs>]]></ProcessParameters>
<CallbackInfo xsi:type="xsd:string">{'eventID': 3}</CallbackInfo>
<ResourcePoolName xsi:type="xsd:string">DispatchedProcessPool</ResourcePoolName>
</urn:RunProcess>
</soapenv:Body>
</soapenv:Envelope>You'll want to set the following values:
- bpInstance = auto
- UseSSO = True
- BPCredentialName = The name of the credential in Credential Manager to use to execute the specified process (this is the one that's passed to AutomateC)
- ProcessName = The name of the Blue Prism process you want to execute
- ProcessParameters = This is the XML input that you would pass to the process if it expects input. If it doesn't take any direct input, you can leave this as is.
- CallbackInfo = If you have a service that will accept a callback post from the process, this is where you could specify any extra information you want passed back. Otherwise, leave blank.
- ResourcePoolName = The name of the Blue Prism Resource Pool that should be used to execute the process.
In the pop-up, you'll select Basic and then enter the username and password for calling the Soap service. After that, you should be able to press the Submit Request. If the request successful, you should see a response similar to this in the response window:
Cheers,
Eric
