Frequently asked questions about OCI integration services and Mirth
What version of Mirth does Datica use?
As of this writing, all of Datica's Mirth environments default to using version 18.104.22.16857 of Mirth. That is the latest stable version that we have verified for our build and supplementary resources. When Mirthconnect releases a new version, it typically contains useful new functionality that you may want to take advantage of. We keep an eye out for these releases and put them thorough testing and validation before promoting them to the default build. If you would like your instance to be updated prior to us approving it, please submit a request to Datica support and we can upgrade your instance. Note that with the update some things do change that can break existing build, so if you choose to upgrade prior to us vetting it out you may encounter issues. Once new versions are approved, we will notify our users to alert them and can help them through the upgrade.
Can I use a different version of Mirth?
If there is a version of Mirth that you prefer to use, yes we can upgrade your instance. Please submit a request to Datica to do so.
As mentioned above, changing versions may break existing build that you have so while Datica will alert you to any known issues/changes be advised that you should do your own validation as well.
Can I import any Mirth channel into my instance?
Unfortunately there is some version clash with importing channels: you cannot import a channel that was built on and exported from a newer version of Mirth than what you're currently using. You can however import channels that were built on and exported an older version of Mirth - you will likely just be prompted whether you'd like for Mirth to automatically optimize the channel for the current version you are running on (selecting Yes is the only option to proceed with importing, however the optimization usually doesn't affect any of the content of the channel itself).
Yes actually! While there's not a specific line number limit, there is a limit on the size of the code being loaded into memory to be compiled. This seems to happen at roughly over 1000 lines so just be aware and if you see either of the following mysterious errors, you may have hit the limit:
Fortunately, this is just a limit of the single step itself. If you split your code into multiple smaller steps, you can avoid the issue. Just utilize channelMap variables in order to bring code from one step into another and you should be set!
How do I clear old data to keep my environment from filling up?
Check out how to enable Pruning in the section on "Settings" in Navigating Mirth
And information on configuring it per channel in the "Summary" section here: Mirth Channel Overview
Do my changes automatically propagate onto my secondary Mirth instance?
For non-channel specific settings, yes as both instances share the same database on the backend. Also, undeployed channels would be updated on both. However, if you modify and deploy a channel on your primary Mirth instance, those changes won't be active on the secondary instance until you deploy the channel there as well. Your secondary Mirth instance can be accessed via http://<Mirth IP>:8081. Your credentials will work for both instances.
Can I use custom Java libraries in my Mirth instance?
Yes, simply provide Datica with your .jar(s) and ask that they place them in the custom-libs directory of the Mirth server. Once there, just go to Settings → Resources → Reload Resource and you should see your .jar file listed in the "Loaded Libraries" section at the bottom.