I'm not sure I quite understand the requirements, but have you looked at the FME Server Console command line tool?

http://docs.safe.com/fme/html/FME_Server_Documentation/Content/ReferenceManual/FME_Server_Console.htm

---

I'm not sure I quite understand the requirements, but have you looked at the FME Server Console command line tool?

http://docs.safe.com/fme/html/FME_Server_Documentation/Content/ReferenceManual/FME_Server_Console.htm

Thanks for the suggestion and sorry if I wasn't clear with my query. Hopefully this clarifies things a bit.

 

 

I have a tool as an executable file in a local folder e.g. C:\\ToolFolder\\Tool.exe

 

 

The tool is standalone and doesn't require a system installation. It's run fine from it's path using windows command prompt.

 

 

I have created a custom transformer that uses a system caller to make use of the tool and that runs fine in FME Desktop.

 

 

I now want to make use of the tool on FME Server and I'd like to know what my options are for making the C:\\ToolFolder\\Tool.exe available within the FME Server environment.

 

 

I found this tutorial which is useful and suggests that I will need to access the FME server file system. There are probably a few ways to do this though.

 

 

https://knowledge.safe.com/articles/34522/fme-server-resources-uploading-referencing-and-con-1.html

 

 

Hope that helps

 

 

 

---

A possible solution would be to

• Copy Tool.exe into one of the shared resources on FME Server, e.g. the "Data" resource where you could create a subdirectory "ToolFolder"
• In your workspace, point the SystemCaller to

   

  $(FME_SHAREDRESOURCE_DATA)/ToolFolder/Tool.exe

If you need the SystemCaller to also work on FME Desktop, you can override the value of FME_SHAREDRESOURCE_DATA in the workspace parameters. This value is ignored when running on FME Server.

---