Skip to main content
  • EN

Hello!

I have a question about the usage of Notifications for FME Server 2016.

I created a Notification with a Publication and a Subscription. The Publication is working and collects the attachments of e-mails in a dedicated folder. From there a Workspace should be triggered to start reading the folder paths, making use of de FileDirectory Reader and process the files that are read. For the triggering of the Workspace a Subscription is created and for some reason, it does not work or does not work all the time. In some cases the restarting of FME Server can help but this is obviously not a solution.

The Workspace that is triggered does not have a JSON-reader. In Tutorials I saw a JSON-reader was part of the solution to trigger a Workspace. In the example parameters of the e-mail were read and would be handy to read for example e-mail parameters. Since these parameters are not needed, as all the information comes from the files read using the FileDirectory Reader, I am using a simple Creator to start the Workspace/Workflow.

There are two aspects that are puzzling for me:

1. When I publish the FME Workspace I choose the JobSubmitterService. I could choose the NotificationService but in my case it does not seem to matter if I make use of this service or not: attempts are unfortunately still in vain for a stable solution. If you click on [edit...] and go to the advanced section you could choose the "Notification Content Format" that can be set either on HTML or (by default) on JSON. As there is no option to choose for no format, would this imply that JSON or HTML code is always needed for the NotificationService?

2. When I test the topic, making use of the empty JSON-string {}, the Workspace will run. This would suggest that the Subscription is functioning.

What could I do to make the Subscription work properly? I would like to be more in control and need some more in depth understanding about the problem.

Any suggestions?

Best Regards,

Jochgem

The Json or Html is only used to pass through the parameters. Yours don't need them so I think you can ignore them.

Your subscription and topic looks already well configured because the workspace runs when you test.

Probably the trouble is how you trigger the topic.

Are you using the same topic for the publisher and the subscriber?

Do you have any logging?

 

Hi Wilko,

Thanks for your reply. The same topic has been used for the publisher and the subscriber. That should not be the problem.

I am now engaged with another problem: the FME Server UI is not accessible anymore after a Windows Update (HTTP 404 error). I will not reinstall FME Server and see if that is any help. For this reason I can not provide you at the moment with any logging.

Thanks anyway! If I have any updates or any progress I will share it with you and the community.

Best Regards,

Jochgem

Hi Wilko,

Thanks for your reply. The same topic has been used for the publisher and the subscriber. That should not be the problem.

I am now engaged with another problem: the FME Server UI is not accessible anymore after a Windows Update (HTTP 404 error). I will not reinstall FME Server and see if that is any help. For this reason I can not provide you at the moment with any logging.

Thanks anyway! If I have any updates or any progress I will share it with you and the community.

Best Regards,

Jochgem

Hi @jochgem

 

It might be useful to post the follow up question as a new question, that way it will gain more visibility and it's easier to answer.

 

 

If you can't access logs through the web ui, log files can be accessed from the REST API or the FME Server System Share location, which is specified at installation time.

 

Hi!

 

Thank you, Jennifer, for the useful information. FME Server is running again, now using port 8080 instead of port 80, but the problem is persistent. (It was not really a question but simply work that still had to be executed.)

I include hereby a log file. I have doubts if it has any value to solve this problem, as log files are only written when the Workspace is running and the problem occur in triggering the Workspace? Or are the activities of Notifications also logged somewhere?

Hereby the log file. Any suggestions are still welcome. 🙂

@jlutherthomas @stalknecht

Best Regards,

Jochgem

Probably the publishing workspace fails and does not trigger the topic in some circumstances. Look at the logging of the publisher job when the subscriber is not trigered.

Reply


Community Stats

30,353
Posts
115,359
Replies
38,089
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.