Skip to main content
Solved

FME server cannot find arcpy


Forum|alt.badge.img

We are having trouble getting fme server find the arcpy libraries while executing a workbench using python caller to do some processing using the arcpy libraries. Where does fme server look for Python libs?

We are running fme server 2015

Best answer by jdh

From the documentation: http://docs.safe.com/fme/html/FME_Server_Documenta...

Uploading Python Modules to FME Server

If you have a Python module you need to use on FME Server which is not part of the Python standard library, use the Upload tool on the Resources page of the Web User Interface, and upload it to the folder under Engine\\Plugins\\python that corresponds to the Python release compatible with the module (for example, python27).

 

 

 

Note that to use arcpy you need to have a license available on the machine running the FME Engine.
View original
Did this help you find an answer to your question?

5 replies

jdh
Contributor
Forum|alt.badge.img+28
  • Contributor
  • Best Answer
  • April 25, 2016

From the documentation: http://docs.safe.com/fme/html/FME_Server_Documenta...

Uploading Python Modules to FME Server

If you have a Python module you need to use on FME Server which is not part of the Python standard library, use the Upload tool on the Resources page of the Web User Interface, and upload it to the folder under Engine\\Plugins\\python that corresponds to the Python release compatible with the module (for example, python27).

 

 

 

Note that to use arcpy you need to have a license available on the machine running the FME Engine.

Forum|alt.badge.img
  • Author
  • April 26, 2016
jdh wrote:

From the documentation: http://docs.safe.com/fme/html/FME_Server_Documenta...

Uploading Python Modules to FME Server

If you have a Python module you need to use on FME Server which is not part of the Python standard library, use the Upload tool on the Resources page of the Web User Interface, and upload it to the folder under Engine\\Plugins\\python that corresponds to the Python release compatible with the module (for example, python27).

 

 

 

Note that to use arcpy you need to have a license available on the machine running the FME Engine.

Thanks for the response, a followup, for arcpy which files specifically should I upload ? There are quite a few of them..


jdh
Contributor
Forum|alt.badge.img+28
  • Contributor
  • April 27, 2016
guha wrote:

Thanks for the response, a followup, for arcpy which files specifically should I upload ? There are quite a few of them..

As far as I know (never having tried it myself) the entire contents of ..\\ArcGIS\\Desktop10.x\\arcpy


Forum|alt.badge.img+1
jdh wrote:

From the documentation: http://docs.safe.com/fme/html/FME_Server_Documenta...

Uploading Python Modules to FME Server

If you have a Python module you need to use on FME Server which is not part of the Python standard library, use the Upload tool on the Resources page of the Web User Interface, and upload it to the folder under Engine\\Plugins\\python that corresponds to the Python release compatible with the module (for example, python27).

 

 

 

Note that to use arcpy you need to have a license available on the machine running the FME Engine.
I didn't install ArcMap on FME Server but installed the 64bit ArcPython library on the server and then uploaded it in the resources folder. I didn't get it to work. I'm hoping I don't have to have ArcMap installed because it's a 32 bit install vs the 64 bit server install I was hoping to use. --I'll do some more research and let you all know what I find out!

 


jdh
Contributor
Forum|alt.badge.img+28
  • Contributor
  • September 28, 2017

I believe you need to have arcGIS installed in order to check out a licence. Make sure to also install the 64-bit background geoprocessing. http://desktop.arcgis.com/en/arcmap/10.3/analyze/executing-tools/64bit-background.htm to use arcpy in 64-bit fme.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings