Chatbot integration with Blue Prism

[vinodchinthakin]

Hi,

We are trying to create a chatbot using tools which are available online, then wants to integrate with Blue Prism.
Now we have created a flow in Microsoft Power virtual agent , facing issue while integrating with Blue prism using api (which is downloaded from DX), can any one help in fixing it.

Does anyone know any chatbot tool which can be integrated with blue prism.
pls share some articles or video url's for reference.

thanks in advance

------------------------------
vinod chinthakindi
------------------------------

[ewilson]

@vinod chinthakindi,

I cant help you with the data gateway integration as I have no hands-on experience with it. I can give you some troubleshooting tips from the perspective of having the Blue Prism runtime resource deployed on an Azure VM​. Not sure that will be much help, but it might give you something to look at.

As I was setting this up in Azure I ran into a similar issue as you in that I was receiving a 401 unauthorized error when I tried to test any of the 3 actions exposed by the connector (i.e. StartProcess, GetProcessList, or GetProcessSchema). Here's what I did, with the help of Chris, to troubleshoot.

1. First thing I did was verify I could reach my Blue Prism instance on Azure by bringing up the list of published SOAP services in the browser. So I used Chrome to navigate to my system (ex. http://XXXXXXXXXXX.cloudapp.azure.com:8181/ws/). If you get the list of public web services you're good there. If not, you may have a network/firewall issue. 
2. After that, I used SoapUI to verify that I could reach my actual Blue Prism process. This entailed importing the WSDL from the remote system (ex. http://XXXXXXXXXXX.cloudapp.azure.com:8181/ws/AddTwoNumbers?wsdl) and then performing a test execution. If this works, you should be good with public access to your SOAP web service. If not, you may have an authentication issue or possibly an HTTP vs HTTPS issue.
3. From there, I went back and verified the complete definition of my Custom Connector definition in Power Automate. That's where I realized my hostname, on the General Information page, was missing a few characters. So I went back to the Azure Function definition and copied the hostname again and pasted it in the Power Automate definition. At this point, I was able to successfully complete the Test option within Power Automate.
4. There could be other areas that are getting in the way of your testing though, so you should also verify:
   1. Each of the 3 Action definitions in Power Automate have the correct value within the code parameter. These should be set to your default API key from your Azure Function definition.
   2. Make sure the URL that's shown for the Actions is correct. For you it will probably be something like https://powerplatformconnector20210427122451.azurewebsites.net/api/BluePrismRestInterface.
   3. Make sure your value for the resourceName parameter is correct. This is the hostname and port of the machie where you're running the Blue Prism process. This has to be a hostname that Azure can access hence the reason it should be an Azure VM, an on-premise data gateway, or simply a public hostname on the internet. In my case, I'm using an Azure VM so my hostname is something like XXXXXXX.southcentralus.cloudapp.azure.com:8182
   4. FInally, you need to create a Connection on the Test page in Power Automate. The Connection is where you specify the HTTP Basic Auth credentials that are required by Blue Prism to run the process that you pass in to the StartProcess call.

Hope this helps.

Cheers,

------------------------------
Eric Wilson
Director, Partner Integrations for Digital Exchange
Blue Prism
------------------------------

[shashank.kumar280]

@vinod chinthakindi

I had similar issue in the past of Data Gateway not appearing in the power automate ui. It was due to a mismatch in the chosen Region during the installation of the Gateway vs the default region in my azure subscription. As the Data Gateway doesn't provide an option to change the Region after installation, I had to re-install the Gateway and choose another region. Eventually it worked out after choosing another region.​

------------------------------
Shashank Kumar
DX Integrations Partner Consultant
Blue Prism
Singapore
+6581326707
------------------------------

[vinodchinthakin]

@shashank.kumar280

Hi
Thanks for your reply. We have re-installed data gatway by chosing same region as in my Azure account.
We are using Free trial subscription only. 
still we are not able to see Gateway. Pls find attachments​

------------------------------
vinod chinthakindi
------------------------------

[vinodchinthakin]

Pls find attachements.

------------------------------
vinod chinthakindi
------------------------------

[vinodchinthakin]

@ewilson @ChrisHogan

We are on the first step, Using  this url​ http://xxxxxxx.cloudapp.azure.com:8181/ws/ ​we are getting nothing, But using http://xxxxxxx:8181/ws/ we are able see the processes which are exposed.

Below are the screenshots.

If you say firewall issue, what changes are required in firewall?

We are using Free Trial Azure subscription. Is the issue because of that?

------------------------------
vinod chinthakindi
------------------------------

[ewilson]

Assuming the first URL you posted is for a Blue Prism VM you created on Azure, you'll need to go in and configure the network settings within the Azure Admin Console. If you open the console in your browser and then click on your VM image you should see the Overview page. In the navigation panel on the left you want to click Networking.

On the Networking page, you need to click the Add inbound port rule button on the right side of the screen.

From there, you need to add rules to allow inbound traffic on port 8181, at a minimum. If you run additional runtime resources on this VM you'll need to open ports for them too.

Cheers,

------------------------------
Eric Wilson
Director, Partner Integrations for Digital Exchange
Blue Prism
------------------------------

[vinodchinthakin]

@ewilson

We have already opened port 8181 in inbound rule of networking of my VM. pls see below attachment.
No additional runtime resources on this VM are created.
​

------------------------------
vinod chinthakindi
------------------------------

[ewilson]

Hi @vinod chinthakindi,

One last thing to check is in the actual Windows VM. Log in as whatever your Windows administrator account is on that VM and check the Windows Firewall. If it's running, you'll probably have to add inbound port rules to it too for Automate.exe and the ports you're using.

Cheers,
​

------------------------------
Eric Wilson
Director, Partner Integrations for Digital Exchange
Blue Prism
------------------------------

[vinodchinthakin]

@ewilson

Logged in VM as windows administrator and created inbound ports for 8181 and for automate.exe.

we tested webservice URL using SOAP UI, 
pls find below attachments for results.

------------------------------
vinod chinthakindi
------------------------------

[ewilson]

@vinod chinthakindi,

One more thing I thought about. You need to change the configuration of Blue Prism to specify that the default runtime resource communicate using the FQDN. See the attached screen shot.

You would also have to set this on the startup parameters of individual runtime resources.

Cheers,

​

------------------------------
Eric Wilson
Director, Partner Integrations for Digital Exchange
Blue Prism
------------------------------