I'm trying to figure out how to use the directory watch on various user folders. The idea is when they update datasets it kicks off a job updating automatically.
Page 1 / 1
What version of FME Server?
I suggest you check this : https://knowledge.safe.com/articles/51817/directory-watch-publisher-tutorial-2017.html
Always use UNC path for your folders.
I suggest you check this : https://knowledge.safe.com/articles/51817/directory-watch-publisher-tutorial-2017.html
Always use UNC path for your folders.
I watched the first video but I didn't see how i could create my own folder path. It only let me create a folder in resources? The UNC path gets an error?
I watched the first video but I didn't see how i could create my own folder path. It only let me create a folder in resources? The UNC path gets an error?
After you created into Ressources your folder's path that you want to watch on you Network, you have to create a Notification/Publication. And after you create your Notification/Subscription and you'll choose FME Workspace protocol to run the job you need when FME Server detects a new file in your folder.
Hi @brianapeters,
If you are looking to watch a folder that isn’t in the FME Server System Share you will need to use the UNC path to set that directory in the Publication. If you are receiving an error then it is likely that the account running the FME Server Services does not have read/write permissions to view this file path.
See Step 5 here: http://docs.safe.com/fme/html/FME_Server_Documentation/Content/ReferenceManual/Directory_Watch_Publisher.htm for reference.
If the error still persists after you have corrected those permissions then please let me know what error is being reported.
Hi @brianapeters,
If you are looking to watch a folder that isn’t in the FME Server System Share you will need to use the UNC path to set that directory in the Publication. If you are receiving an error then it is likely that the account running the FME Server Services does not have read/write permissions to view this file path.
See Step 5 here: http://docs.safe.com/fme/html/FME_Server_Documentation/Content/ReferenceManual/Directory_Watch_Publisher.htm for reference.
If the error still persists after you have corrected those permissions then please let me know what error is being reported.
I use local system for Appserver/core/database and an AD group for engines. Would you recommend using the AD for the App Server?
Hi @brianapeters,
If you are looking to watch a folder that isn’t in the FME Server System Share you will need to use the UNC path to set that directory in the Publication. If you are receiving an error then it is likely that the account running the FME Server Services does not have read/write permissions to view this file path.
See Step 5 here: http://docs.safe.com/fme/html/FME_Server_Documentation/Content/ReferenceManual/Directory_Watch_Publisher.htm for reference.
If the error still persists after you have corrected those permissions then please let me know what error is being reported.
I added the AD group user/pass to the Core service and it now excepts the folder path!
Hi @brianapeters,
If you are looking to watch a folder that isn’t in the FME Server System Share you will need to use the UNC path to set that directory in the Publication. If you are receiving an error then it is likely that the account running the FME Server Services does not have read/write permissions to view this file path.
See Step 5 here: http://docs.safe.com/fme/html/FME_Server_Documentation/Content/ReferenceManual/Directory_Watch_Publisher.htm for reference.
If the error still persists after you have corrected those permissions then please let me know what error is being reported.
On the topic monitoring page I'm getting an error "There was an error connecting to monitoring service " What would this error refer to?
On the topic monitoring page I'm getting an error "There was an error connecting to monitoring service " What would this error refer to?
ok I'm going to solve my own problems i guess.... lol I just recently upgraded to 2018.1..1.1 I did not configure the websocket! I made all the changes and it now monitors the topic!
ok I'm going to solve my own problems i guess.... lol I just recently upgraded to 2018.1..1.1 I did not configure the websocket! I made all the changes and it now monitors the topic!
By the way, I don't know where you are in this world, but I can tell you that Safe employees aren't at the job at this moment. They always response so be a little patient... Thank you.
About your problem you should check this : https://knowledge.safe.com/questions/63922/topic-monitoring-not-working-fme-server-2017.html
By the way, I don't know where you are in this world, but I can tell you that Safe employees aren't at the job at this moment. They always response so be a little patient... Thank you.
About your problem you should check this : https://knowledge.safe.com/questions/63922/topic-monitoring-not-working-fme-server-2017.html
I wasn't expecting replies right away. Re-reading my post i didn't mean sound impatient or even agitated... I had figured out at least this problem just as i posted and wanted to let them know. I apologize that it reads that way!
By the way, I don't know where you are in this world, but I can tell you that Safe employees aren't at the job at this moment. They always response so be a little patient... Thank you.
About your problem you should check this : https://knowledge.safe.com/questions/63922/topic-monitoring-not-working-fme-server-2017.html
https://knowledge.safe.com/questions/38124/topic-monitoring-is-not-working-after-configuring.html
your link led me this lick and i found another mistake i made. My slashes were backwards!
I wasn't expecting replies right away. Re-reading my post i didn't mean sound impatient or even agitated... I had figured out at least this problem just as i posted and wanted to let them know. I apologize that it reads that way!
Hi @brianapeters,
I'm pleased to see you were able to troubleshoot the error yourself but I will just add some comments here in case any other users run into this problem!
Re the accounts running the services - the FME Server Core controls anything run in the notification service so it must also be running under an account that has correct permissions to the directory you are trying to watch.
Re "There was an error connecting to monitoring service" this error usually occurs because:
a) topic monitoring uses the websocket protocol which requires port 7078 to be open to incoming traffic (https://docs.safe.com/fme/html/FME_Server_Documentation/Content/ReferenceManual/FME-Server-Ports.htm)
b) If you have SSL configured you will need to make sure you followed Step 5 here to enable SSL on the websocket server.