· Nov 13, 2023

System Default Settings and TestingEnabled / LogGeneralTraceEvents

We are successfully using System Default Settings to manage differences in settings across environments where the production and underlying code are otherwise identical. However, the TestingEnabled and LogGeneralTraceEvents settings don't appear to be settable via this mechanism. While we appear to be able to set them on the SDS page, they do not show up as selectable when resetting the settings on the Production Settings tab in the management portal - see screenshots below. Is there any way of managing these two settings so we can have development and test servers running with TestingEnabled set to true, but production servers set to false? Thanks!

Product version: Ensemble 2018.1
$ZV: Cache for Windows (x86-64) 2018.1 (Build 184U) Wed Sep 19 2018 09:09:22 EDT
Discussion (3)2
Log in or sign up to continue

@Colin Brough - this was recently discussed on a thread internal to InterSystems, and I credit @Eduard Lebedyuk 
for the following options, which were suggested within the context of Enabled/Disabled Business Hosts on different environments using the same Production (some don't apply to your question about logging and testing, but I include them all for completeness):

1. Track a separate production class for each environment.
2. Use SDS to effectively disable Business Hosts (for example, by setting the Port property to an empty string).
3. Create a custom adapter/business host that has SDS configurable setting "RealEnable", which would be checked in OnInit or OnProcess input.
4. Use Interoperability Schedules, with Business Host always off/on.

I think (1) and (3) would be most likely to work for you here.

Also, it's not going to help you in the immediate term, but be aware that TestingEnabled (along with some other fields) is supported for SDS starting in InterSystems IRIS 2023.3 (I am very excited about that!!)