Mirth Appliance Clustering Notes

• Load balancing can be used to stop clustering and retain a virtual IP
• Channels are synchronized after their initial state is changed to PAUSED
• Channel DEPLOY triggers synchronization via Appliance Plugin on active node:
• A deploy event is fired off - log entry:
• com.mirth.connect.plugins.appliance.Appliance
  onDeploy() called, waking up MirthConnectSync
• Channel REMOVE does not trigger synchronization
• Configuration is retrieved through:
• http://standby/cp/api/mirthconnect/config
  ... which is forwarded on standby node to:
• http://localhost:8027/api/configuration

Deployit Tricks

1. Use udm for script rules to avoid creation of unwanted steps
2. Use generic otherwise: this will create create/destroy steps and make templating in properties available
3. Use dictionaries and moustaches for package parameters to change checksum and force update
4. Use container properties for script parameters that do not require update when they change
5. Never use file.File but rather generic.File