First create ec2 Ubuntu instance. This can be 14.04 now on MirthConnect 3.2 and above. Hurray!
Great thanks for the original guide: https://gist.github.com/jgautsch/9157402
# Update Ubuntu
sudo aptitude update
# Safe upgrade of Ubuntu
sudo aptitude safe-upgrade
# Make the ~/downloads folder
mkdir ~/downloads
# Change into ~/downloads/ folder
cd ~/downloads/
# Download the most up to date Mirth Connect .sh file. You can find this here: [Mirth Connect Downloads](https://www.mirth.com/Downloads)
curl -O http://downloads.mirthcorp.com/connect/3.5.1.b194/mirthconnect-3.5.1.b194-unix.sh
# (Optional) You may want to install nginx to manage SSL, basic auth or to provide multiple DNS endpoints for your Mirth instance
sudo apt-get install nginx
# Remove any existing versions of Java. We're using a version of Mirth greater than 3.4.x now, so Mirth now REQUIRES Java 8. You can roll back to an earlier version of Mirth to support Java 7. Mirth Requires the Oracle version of Java to run (not the OpenJDK).
sudo apt-get purge openjdk-\*
# Install python software properties (required for next command)
sudo apt-get install python-software-properties
# Add apt-get repository source
sudo add-apt-repository ppa:webupd8team/java
# Add package listings from repository in previous command to listings
sudo apt-get update
# Now we can install Java
# So install Java...
sudo apt-get install oracle-java8-installer
# Now we're ready to install Mirth Connect
cd ~/downloads/
# Set the permissions to be able to run the installer script
sudo chmod a+x ~/downloads/mirthconnect-3.5.1.b194-unix.sh
# Now run the Mirth Connect installer
sudo ~/downloads/mirthconnect-3.5.1.b194-unix.sh
You can hit enter through most of the installer, the defaults are good. There are two hard prompts that you'll need to insert data into ->
Application data should go in : /usr/local/mirthconnect/application
Logs should go : /usr/local/mirthconnect/logs
###Accessing Mirth Itself
Once Mirth is up and running, you can access it by going to http://yourIPAddress:8080 and following the steps to download the Java Applet. The default username/password is admin/admin and you'll be prompted to change this after your first log in.
###If Mirth stops
Mirth runs as a daemon by default when you start the software. If Mirth stops for whatever reason you can start/stop mirth using mcservice located in the default mirth directory /usr/local/mirthconnect. The format for this is service mcservice start|stop|restart
You don't need to do this at first, but is necessary for any project at scale. Datica's Mirth runs on HA Postgres boxes.
The default database that Mirth Connect will use is Derby. However, this is not really supposed to be used in production, so we will switch over to good ol' Postgres. Remember that your channels will not transfer between the two databases, so if you did any work on the derby database, make sure to export any channels/message history before performing the cutover.
I've found that Derby usually doesn't scale to more than a few thousand messages or a stream with any amount of real traffic, so installing PG is a must sooner rather than later. Here is a nice intro to installing and using PostgreSQL on Ubuntu
Let's start with a nice update of the apt-get repository:
apt-get update
Next we'll go ahead and download Postgres and its helpful accompanying dependencies:
sudo apt-get install postgresql postgresql-contrib postgresql-client-common
Now postgres is installed.
By default postgres uses ident authentication, tying each server user to a Postgres account. So to get going we will first switch into the default user, and then create our user and database mirth ("mirth").
$ sudo su - postgres
$ createuser -d -R -P mirth
Enter name of role to add: mirth
Enter password for new role:
Enter it again:
$ sudo -u postgres createdb -O mirth mirth
According to this mirthcorp.com thread, once PostgreSQL is installed and the user/role that we're going to use is created, we just have to update the mirth.properties file with the URL and credentials to the new database and start the server, and that will automatically create the schema for us. The default port for postgres is 5432, so our URL is 0.0.0.0:5432. Our user/pw is whatever we made in the createuser step.
Open up sudo nano /usr/local/mirthconnect/conf/mirth.properties and replace:
database = derby
...
database.url = jdbc:derby${dir.appdata}/mirthdb;create=true
with
database = postgres
...
database.url = jdbc:postgresql://localhost:5432/mirthdb
database.username = mirth
database.password = <YOUR PASSWORD>
If you had used your mirth installation at all thus far, all the stuff you saved is gone with the old database. So when you log in to Mirth Connect, it will be with the default username/pw again (admin:admin), and you will be prompted to change it, and you'll have to re-create any of your channels again.