I understand your architecture situation. Normally, FactorySQL Alerts are used to send emails. Would your IT department open up a single port (SMTP, port 25) from the FactorySQL machine to the email server?
The best you could do right now with FactoryPMI is to have the client send the daily email. Use a timer global event script to run the code, then a DB SQLTag of a datetime type to record when you last sent the email. That way any open client would send it, but you shouldn’t have a problem with concurrency - especially if your timer is set to check slowly (every 10 minutes or so).
Having a constantly running Jython engine in the Gateway is a feature request that has been around for awhile. I’ll note your interest. Unfortunately the only practical application that I can come up with is scheduling periodic emails or printouts - both of which can be accomplished through the client, as long as it’s logged in, without any user interaction. I like the idea in theory, but it doesn’t seem to be that practical since FactorySQL handles all the alarming and most always running periodic tasks.
Perhaps an easy implementation may be an autologin configuration based on IP address (localhost) and a setting for the service (Gateway) to launch the client locally if it’s not open. An instance of the client may be the best “Jython engine”. I’ll see what the developers think.