Skip to content

Add section describing how OIE is expected to be compatible with Mirt… #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jonbartels wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add section describing how OIE is expected to be compatible with Mirt… #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,16 @@ Please do your best to include the following information in your issue:
* The output of the command you executed (Hint: add `--progress=plain` to your `docker` command to see the full output)
* Use [Markdown](https://guides.github.com/features/mastering-markdown/) to format your issue text, ESPECIALLY if you are including code snippets or command output. This will make it easier for us to read and understand your issue.

#### Upgrading from Mirth Connect

Open Integration Engine can be upgraded from Mirth Connect 4.5.2. The following steps will connect Open Integration Engine to your existing Mirth Connect database, allowing you to continue using your existing channels, connectors, and other configurations.

1. Update your Mirth Connect installation to Mirth Connect 4.5.2
2. Backup your Mirth Connect database
3. Stop your Mirth Connect server
4. Update Open Integration Engine to use the same `vmoptions` and `mirth.properties` files as your Mirth Connect installation. Containerized instances will use environment variables to set these options. Other installations use the config files.
Copy link

@leovander leovander Jul 3, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Containerized instances will use environment variables to set these options.

Is that generally true? It's the tiniest nit in the world, but the docker hub connect hub page/readme has the following:

You can use environment variables to configure the mirth.properties⁠ file or to add custom JVM options.

e.g. shall/should/must.

That is the ideal way, but couldn't a containerized version also read from a mirth.properties file?

5. Start Open Integration Engine, watch for errors in the console and `mirth.log`

------------

<a name="what-is-oie"></a>
Expand Down