Announcement

Collapse

NextGen (Mirth) Connect 3.10.0 Released!

NextGen (Mirth) Connect 3.10.0 is now available as an appliance update and on our GitHub page. This release includes better SQL Server database support, security improvements through fixes and library updates, and improvements for the Advanced Clustering plugin with a focus on improving performance of many of the tasks that are carried out on a frequent interval. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Deploy one channel vs Deplay all

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Deploy one channel vs Deplay all

    How do I deploy just one channel? The only option that I see is Deploy All. I disabled the one didn't want to deploy, clicked on refresh and did a deploy all but it still deployed because I can see the connection drop within Cloverleaf. Is this a bug or am I doing something wrong?

    Thanks,
    Austin

  • #2
    Reeploy one channel vs Deplay all

    The only option is to Deploy All. When you deploy all, Mirth will actually restart the engine, causing any open connections to be lost.
    Chris Lang

    Comment


    • #3
      Reeploy one channel vs Deplay all

      In order to have the feature of Deploy All and Deploy Channel, do I make some type of product enhancement request or can I work on it myself? I have over 200 threads in Cloverleaf and a Deploy All would drop all connections going to Cloverleaf. Wouldn't be good.
      Thanks.

      Comment

      Working...
      X