Large-scale implementations of InterSystems technology often involve dozens of environments, each with its own set of complex configuration settings spread across a wide array of administrative screens and menus. It’s easy for these settings to get out of sync among various instances, creating problems that aren’t discovered until they impact production systems. The result is increased sustainment cost and an unacceptable level of risk to healthcare workflows and patient outcomes.
The J2 Settings Framework addresses this problem by bringing all of your HealthShare and IRIS settings together in a unified, configuration-as-code representation.
It provides your team with a simple administrative dashboard that enables centralized change management and source control, monitoring and alerting of configuration changes, and one-click deployment of approved changes across the enterprise.
With the J2 Settings Framework, your engineers will spend less time wrestling with configuration issues and chasing down errors, and more time innovating. That means greater overall system stability, vastly reduced risk of downtime or interrupted data flows, and more reliable decision-making at the point of care.
The J2 Settings Framework provides a centralized user interface for monitoring and updating your settings, exporting them as XML, and pushing / applying them to other servers.
You can even specify conditional values for different server levels — for example, port 123 on Dev, port 456 on Stage, and port 789 on Prod — in a single setting that gets automatically applied correctly to each server.
Some of the biggest names in government, healthcare, and business turn to J2 to help them utilize InterSystems technology to its fullest potential. Get in touch with us to find out why.