When you start a channel, the Mirth® Connect Administrator automatically checks if there are any dependencies of the channel that should be started first. If there are, they will be shown in a special dialog:
By default only the channels you have selected will be bolded in the dialog, meaning that only they will be started. If you want to start the other channels in the dependency chain as well, check the " Start/resume # additional channels " check box before selecting the OK button. Upon pressing OK the channels will be deployed in the numeric order shown in the dialog.
The numbered list in this dialog indicates the different "tiers" in the dependency graph. Any downstream dependencies will be deployed / started
first, and only then will their dependent channels be deployed / started. In the example picture above,
if the checkbox is checked, the channel labeled
1. will be started first, then the channel labeled
2., and then finally the channel labeled
3., which was the original channel selected from the Dashboard table.
- If the checkbox remains unchecked, only the originally selected channel(s) are started. You can always tell which channels will be affected, because they will appear as bold in the list.
Deploying channels is very similar in behavior, except that the chain of channels shown in the dialog will include both dependents and dependencies:
This is because deploying a channel may entail undeploying any selected channels first, and then redeploying them. So when (re)deploying a particular channel, this sequence is followed:
- All dependent channels are undeployed.
- The selected channel is undeployed.
- All dependency channels are undeployed.
- All dependency channels are deployed.
- The selected channel is deployed.
- All dependent channels are deployed.
