Settings
The Settings page organizes server configuration into tabs. Each tab covers a distinct area of administration. Changes here affect the entire server.
Server tab
Section titled “Server tab”Shows information about the running Mirth Connect instance (version, runtime, operating system, database type, uptime) and lets you adjust server-wide settings, grouped into sections:
- General — environment name, server name, default background color, whether to provide usage statistics, and auto-logout (enable plus the inactivity interval in minutes)
- Channel — clear the global map on redeploy, default queue buffer size, and which metadata columns (source, type, version) channels store by default
- Email — the outbound mail (SMTP) settings the server uses for notifications: host, port, timeout, from address, and whether to use a secure connection and authentication
- Notification — server notification settings
Administrator tab
Section titled “Administrator tab”Controls preferences for the web administrator interface, in two sections.
System Preferences apply to everyone using this server:
- Dashboard refresh interval — how often the Dashboard polls for statistics updates
- Message browser page size — default number of messages per page in the message browser
- Event browser page size — default number of events per page in the Events view
- Format text in message browser — whether to pretty-print message content
- Confirmation prompts — toggles for the message-browser text-search prompt, the filter/transformer iterator dialog, the attachment-type dialog, and the reprocess/remove-messages confirmation
- Import / export code template libraries with channels — whether channel import and export include linked code template libraries (Yes, No, or Ask)
User Preferences apply to your own account:
- Administrator background color — use the server default or choose a custom color to visually distinguish environments (useful when managing multiple servers)
- Check for new notifications on login — whether to show unread system notifications at sign-in
Tags tab
Section titled “Tags tab”Manage the color-coded tags that can be applied to channels. Add new tags or delete unused ones. Tags appear on the Dashboard and the Channels list to help organize large deployments.
Configuration Map tab
Section titled “Configuration Map tab”The configuration map is a server-wide key/value store accessible in channel scripts via configurationMap.get('key'). Use it to externalize environment-specific values (hostnames, ports, passwords) so the same channel configuration works across dev, test, and production without code changes.
Add, edit, and delete entries here. Each entry has a key, a value, and an optional comment.
Database Tasks tab
Section titled “Database Tasks tab”Lists available administrative database tasks (such as index rebuilding or integrity checks). Select a task and run it on demand. These tasks are advanced operations — consult Mirth Connect documentation before running them in production.
Resources tab
Section titled “Resources tab”Manage shared classpath resources (JAR files, libraries) that channels can reference. Adding a resource here makes it available to all channels on the server without bundling it into individual channel scripts.
Data Pruner tab
Section titled “Data Pruner tab”Configure automatic pruning of old messages and content from the message store:
- Enable pruner — turn pruning on or off
- Prune metadata after N days — removes message metadata older than the specified number of days
- Prune content after N days — removes raw and processed message content (metadata is retained longer for auditing)
- Archive before pruning — optionally archive messages before deletion
- Prune errored messages — whether to prune messages that ended in an error state
Plugin-specific tabs
Section titled “Plugin-specific tabs”If optional plugins are installed, additional tabs appear:
- MirthSync — configuration for the MirthSync plugin (channel synchronization)
- Cloud Services — configures the secure admin tunnel that lets you manage this Mirth server remotely over a peer-to-peer (P2P) connection. See Connections.