Skip to main content
  • EN

Hi,

I have a 2015 FME Server that I am preparing to upgrade to 2017.

We found out last week that 3 of the 50 legacy jobs do send emails and are in daily use by our DMS team.

The email part of the workspaces consists of a

FMEServerEmailGenerator transformer and

FMEServerNotifier transformer that connects to the topic Email.

However there are no Subscriptions configured on the 2015 FME Server.

So I'm wondering how is it working so I can port the configuration to FME Sever 2017 and test these important jobs? Every article I read about configuring sending Email refers to a Subscription.

I have made a sample workspace and send an email by using the 2 transformers above connecting to the topic, so it is working.

I've checked \\Utilities\\smtprelay\\james\\apps\\james\\SAR-INF\\config.xml on the 2015 server but don't see anything specific. I know the SMTP relay service is part of the FME Core in 2017.

Any tips would be appreciated.

Thanks,

Annette

To try and understand: does the mails currently get sent in FME Server 2015, without any subscriptions?

To try and understand: does the mails currently get sent in FME Server 2015, without any subscriptions?

Yes, it works without the subscription. Also of note, I suspect the server was originally upgraded from version 2013 to 2015 at some point in time.

 

 

Yes, it works without the subscription. Also of note, I suspect the server was originally upgraded from version 2013 to 2015 at some point in time.

 

 

That's weird. You could consider looking inside the repository database to see if there's any subscriptions defined there that's not showing up in the GUI.

 

On the server, connect with pgAdmin to localhost on port 7080 with user and password 'fmeserver'. Look inside the tables 'fme_subscription' and 'fme_subscription_topics' (I think).

To try and understand: does the mails currently get sent in FME Server 2015, without any subscriptions?

Hi David - that was indeed the solution. They were available in the repository but not in the GUI. We restored the 2015 backup in 2017 and then they appeared. Strange but working. Thanks for your help.

 

 

Hi David - that was indeed the solution. They were available in the repository but not in the GUI. We restored the 2015 backup in 2017 and then they appeared. Strange but working. Thanks for your help.

 

 

Sounds like you found an old bug! Good to hear you got it working.

Reply


Community Stats

30,194
Posts
114,615
Replies
37,858
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.