Development Servers - Broadcasting - Getting around the Licence Breach

We rsync our production Enterprise Linux/CentOS servers, which host Yellowfin also (Apache Tomcat/MySQL) to Test environment(s).

Upon sync, of course Yellowfin's licence is then 'breached' on said test environment(s) as the server names are now different to the licence. This is fine - we expect it to breach.

However, Yellowfin will still broadcast from said test server, even though the licence is breached. The existing ConfigCode = SMTP setting is still set to 'localhost' after rsync, and the broadcast scheduler still runs and distributes reports from the test server(s). This is our issue where users are receiving scheduled emails from Production, and (sometimes out of date) Test environments.

Our workaround is to use the MySQL command as follows to reset the Test environment field yellowfin.Configuration.ConfigCode to 'xxxxx' -- (it was 'localhost' on the production server)

use yellowfin; update Configuration set ConfigData = 'xxxxx' where ConfigCode = 'SMTP';

Our fix is a temporary workaround but I was wondering a) if you're aware of the breach as per above, and b) if you'd like to secure yellowfin broadcasts to first rely on checking if the licence is valid before running the scheduled broadcasts, and if invalid, don't distribute reports. =)