Skip to main content
Solved

setting a reference to a folder using shared references.


mygis
Supporter
Forum|alt.badge.img+13
  • Supporter

Hello,

I am using FME Server 2016.1 and I need to reference a folder named "farms:. I have added that into the config file and it appears in my resources list, no problem. However, the issue I am having is that I cannot run any workspace when I select the file for processing. If the files are put in other resources like data/myfiles, there is no issue. Below is the configuration I have added into the fmeserverconfig.txt file:

SHAREDRESOURCE_TYPE_7=FILE

SHAREDRESOURCE_NAME_7=rivers

SHAREDRESOURCE_DISPLAYNAME_7=rivers

SHAREDRESOURCE_DESCRIPTION_7=This shared resource is for the rivers

SHAREDRESOURCE_ISMIGRATABLE_7=false

SHAREDRESOURCE_DIR_7=C:/ProgramData/Safe Software/FME Server///resources/data/water/rivers/

SHAREDRESOURCE_SECURITY_DEFAULT_ROLES_7=fmeadmin

 

 

 

The error I get on FME Server is:

statusMessage

Undefined macro `rivers' dereferenced in file `rivers\\shape2shape\\rivers2tab.fmw'

 

 

Note, when using the workspace in WB, it works perfectly. If I access to my data from the data folder in the resources, it works as well.

Any help would be much appreciated.

Thanks.

Best answer by stalknecht

  1. If the FME Engines require direct access to the shared resource (for example, a workspace run by the Job Submitter service, rather than using the Data Upload Service to supply the resource), you must also add an entry for the shared resource definition to fmeEngineConfig.txt (also located in <FMEServerDir>Server\\), on the machine that hosts the FME Server Core, as well as any other machines on which engines are installed:
MACRO_DEF <Name> "<Directory>"

Example:

MACRO_DEF SERVER_TEMP "C:/Server"

Example (specifying a UNC path):

MACRO_DEF FME_SHAREDRESOURCE_UNCDATA "//servername/Data/"

View original
Did this help you find an answer to your question?

3 replies

stalknecht
Contributor
Forum|alt.badge.img+19
  • Contributor
  • Best Answer
  • July 12, 2017

  1. If the FME Engines require direct access to the shared resource (for example, a workspace run by the Job Submitter service, rather than using the Data Upload Service to supply the resource), you must also add an entry for the shared resource definition to fmeEngineConfig.txt (also located in <FMEServerDir>Server\\), on the machine that hosts the FME Server Core, as well as any other machines on which engines are installed:
MACRO_DEF <Name> "<Directory>"

Example:

MACRO_DEF SERVER_TEMP "C:/Server"

Example (specifying a UNC path):

MACRO_DEF FME_SHAREDRESOURCE_UNCDATA "//servername/Data/"


mygis
Supporter
Forum|alt.badge.img+13
  • Author
  • Supporter
  • July 12, 2017
stalknecht wrote:

  1. If the FME Engines require direct access to the shared resource (for example, a workspace run by the Job Submitter service, rather than using the Data Upload Service to supply the resource), you must also add an entry for the shared resource definition to fmeEngineConfig.txt (also located in <FMEServerDir>Server\\), on the machine that hosts the FME Server Core, as well as any other machines on which engines are installed:
MACRO_DEF <Name> "<Directory>"

Example:

MACRO_DEF SERVER_TEMP "C:/Server"

Example (specifying a UNC path):

MACRO_DEF FME_SHAREDRESOURCE_UNCDATA "//servername/Data/"

Hi and thanks @stalknecht

 

I will try it now, but just another question, does the MACRO_DEF have to be a unique name?

 

 

Would this make sense?

 

 

fmeServerConfig.txt

 

 

SHAREDRESOURCE_TYPE_7=FILE

 

SHAREDRESOURCE_NAME_7=FME_SHAREDRESOURCE_SCE

 

SHAREDRESOURCE_DISPLAYNAME_7=rivers

 

SHAREDRESOURCE_DESCRIPTION_7=This shared resource is for the rivers

 

SHAREDRESOURCE_ISMIGRATABLE_7=false

 

SHAREDRESOURCE_DIR_7=C:/ProgramData/Safe Software/FME Server///resources/data/water/rivers/

 

SHAREDRESOURCE_SECURITY_DEFAULT_ROLES_7=fmeadmin

 

 

fmeEngineConfig.txt

 

 

MACRO_DEF FME_DATA_REPOSITORY "!FME_SERVER_ROOT!/resources/system/temp/upload/" \\

 

MACRO_DEF FME_SHAREDRESOURCE_LOG "C:/ProgramData/Safe Software/FME Server///resources/logs/" \\

 

MACRO_DEF FME_SHAREDRESOURCE_DATA "C:/ProgramData/Safe Software/FME Server///resources/data/" \\

 

MACRO_DEF FME_SHAREDRESOURCE_TEMP "C:/ProgramData/Safe Software/FME Server///resources/temp/" \\

 

MACRO_DEF FME_SHAREDRESOURCE_SYSTEM "C:/ProgramData/Safe Software/FME Server///resources/system/" \\

 

MACRO_DEF FME_SHAREDRESOURCE_BACKUP "C:/ProgramData/Safe Software/FME Server///resources/backups/" \\

 

MACRO_DEF FME_SHAREDRESOURCE_SCE "C:/ProgramData/Safe Software/FME Server///resources/data/water/rivers/"

 

 

Thanks.

 

 

 


stalknecht
Contributor
Forum|alt.badge.img+19
  • Contributor
  • July 12, 2017
mygis wrote:
Hi and thanks @stalknecht

 

I will try it now, but just another question, does the MACRO_DEF have to be a unique name?

 

 

Would this make sense?

 

 

fmeServerConfig.txt

 

 

SHAREDRESOURCE_TYPE_7=FILE

 

SHAREDRESOURCE_NAME_7=FME_SHAREDRESOURCE_SCE

 

SHAREDRESOURCE_DISPLAYNAME_7=rivers

 

SHAREDRESOURCE_DESCRIPTION_7=This shared resource is for the rivers

 

SHAREDRESOURCE_ISMIGRATABLE_7=false

 

SHAREDRESOURCE_DIR_7=C:/ProgramData/Safe Software/FME Server///resources/data/water/rivers/

 

SHAREDRESOURCE_SECURITY_DEFAULT_ROLES_7=fmeadmin

 

 

fmeEngineConfig.txt

 

 

MACRO_DEF FME_DATA_REPOSITORY "!FME_SERVER_ROOT!/resources/system/temp/upload/" \\

 

MACRO_DEF FME_SHAREDRESOURCE_LOG "C:/ProgramData/Safe Software/FME Server///resources/logs/" \\

 

MACRO_DEF FME_SHAREDRESOURCE_DATA "C:/ProgramData/Safe Software/FME Server///resources/data/" \\

 

MACRO_DEF FME_SHAREDRESOURCE_TEMP "C:/ProgramData/Safe Software/FME Server///resources/temp/" \\

 

MACRO_DEF FME_SHAREDRESOURCE_SYSTEM "C:/ProgramData/Safe Software/FME Server///resources/system/" \\

 

MACRO_DEF FME_SHAREDRESOURCE_BACKUP "C:/ProgramData/Safe Software/FME Server///resources/backups/" \\

 

MACRO_DEF FME_SHAREDRESOURCE_SCE "C:/ProgramData/Safe Software/FME Server///resources/data/water/rivers/"

 

 

Thanks.

 

 

 

The name should be unique but they can point to existing locations that are used in other names.

 


Reply


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