Hi,
Has anybody attempted to publish a script tool created in R using the R-ArcGIS Bridge as a Web Tool before? A Web Tool I am working on relies on a R Script tool as part of the model. The model and the script tool itself both run successfully in ArcGIS Pro with no issues.
In testing this out, I have published the standalone script tool to my organization's Portal and, while it publishes successfully, when I attempt to run it within the portal it fails.
My assumption is that I might need to install R, and the packages/dependencies used by the tool, onto the federated server that our Portal runs on. But, as someone relatively new to Enterprise and Web Tool publishing, I could be wrong about this.
Does anyone in the community have any insights into this process and/or experience sharing an R Script tool as a Web Tool in Portal? Any help would be appreciated greatly - this is something I have been stuck on for a while now.
Solved! Go to Solution.
Hello Dylan,
Thanks for asking this question. You are right, you need R on the server so that once your script tool makes R calls, it has access to the R interpreter.
We have seen some issues with timeouts lately, you may want to increase the timeout time limit in your portal. R can be notoriously slow and this results in a tool that just does not do anything in the portal, where in reality it just cannot finish and times out.
The most streamlined way of sharing the R web tool is creating a script tool in ArcGIS Pro and sharing it, it seems that is exactly what you have done.
Orhun
Hi Dlan,
The R-ArcGIS Bridge isn't officially support by Esri. But you may have success posting your question here as well:
https://community.esri.com/t5/r-arcgis/gh-p/r-arcgis
Calvin
Hello Calvin,
Thank you for the resources. One correction: R-ArcGIS Bridge is an officially supported product of ESRI.
I will add to the great resources you shared with our new product landing page.:
https://www.esri.com/en-us/arcgis/products/r-arcgis-bridge/overview
Orhun
Hello Dylan,
Thanks for asking this question. You are right, you need R on the server so that once your script tool makes R calls, it has access to the R interpreter.
We have seen some issues with timeouts lately, you may want to increase the timeout time limit in your portal. R can be notoriously slow and this results in a tool that just does not do anything in the portal, where in reality it just cannot finish and times out.
The most streamlined way of sharing the R web tool is creating a script tool in ArcGIS Pro and sharing it, it seems that is exactly what you have done.
Orhun
Thank you, Orhun!
This project got shelved, but this will certainly be useful in any future scenario where I need to share a tool that utilizes the R-Arc bridge though our Portal.
No problem, Dylan!
In order to make the future process easier, below is a link that outlines the steps of getting R setup on your server. Hopefully, these steps will minimize the number of moving parts and make using your R tools on Portal easier.