Discussing ‘best practices’ in Cloverleaf is like debating a ‘best’ golf grip, much less anything we talk about in IT — I’ve heard the latest version of ITIL does away with phrase almost completely…
We don’t use the cycling options as the SysAdmin who runs our Unix servers has been using the same home-grown scripts since we adopted Cloverleaf when version 3.7 was the latest and greatest.
I’ve found that EO depends on the interface(s) in the process. For mature, very vanilla HL7 stuff, “disable all” works and keeps the folks who manage space on the servers from going all white-knuckled. Disk-based batch file interfaces, the same. New implementations — especially when you don’t get a warm and fuzzy about the vendor — turn it up. Then ratchet it back as your comfort level grows. Anytime you’re going through a firewall, more is also better.
But we’re also a small shop, two servers (1 prod/1test) each with two sites, totalling 26 processes/70+ threads — I’m sure some of the bigger enterprises will chime in with more specific guidance.
.
