Forge Home

mirthconnect

MirthConnect management module

12,872 downloads

7,678 latest version

4.5 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.2.1 (latest)
  • 0.2.0
  • 0.1.0
  • 0.0.5
  • 0.0.4
  • 0.0.2
  • 0.0.1
released May 26th 2016
This version is compatible with:
  • RedHat

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'myoung34-mirthconnect', '0.2.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add myoung34-mirthconnect
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install myoung34-mirthconnect --version 0.2.1

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

myoung34/mirthconnect — version 0.2.1 May 26th 2016

puppet-mirthconnect

Build Status  Coverage Status  Puppet Forge Bitdeli Badge

Puppet Module For Mirthconnect

About

Mirth Connect allows applications to communicate with disparate health information systems using a wide variety of protocols and messaging systems. It supports Windows, OSX, and RHEL/CentOS distributions, while this module is aimed at CentOS only (untested on RHEL).

Supported Versions (tested)

OS

  • AWS Linux
    • Mirth Connect Base install (Mirth Connect not pre-installed)
      • 3.4.0.8000.b1959 (from source only)
  • CentOS 6
    • Mirth Connect Base install (Mirth Connect not pre-installed)
      • 3.4.0.8000.b1959

Prerequisites

  1. Yum repository with Mirth Connect RPMs available (The EULA does not allow redistribution) if using the 'yum' provider (see usage).
  2. Valid license information

Parameters

  • admin_password
  • The password to set the admin password to post-install.
  • db_dbname
  • Optional database name for mirth to use in the mirth.properties file.
  • Not optional if the db_provider is set to anything but 'derby'
  • db_host
  • Optional database hostname for mirth to use in the mirth.properties file.
  • Not optional if the db_provider is set to anything but 'derby'
  • db_pass
  • Optional database password for mirth to use in the mirth.properties file.
  • Not optional if the db_provider is set to anything but 'derby
  • db_port
  • Optional database port for mirth to use in the mirth.properties file.
  • Not optional if the db_provider is set to anything but 'derby'
  • db_provider
  • Optional database provider for mirth to use in the mirth.properties file.
  • Currently the only valid strings are 'derby' or 'mysql'
  • db_user
  • Optional database user for mirth to use in the mirth.properties file.
  • Not optional if the db_provider is set to anything but 'derby'
  • java_version
  • Optional java version to install. Defaults to 'java-1.8.0-openjdk'
  • provider
  • The provider to download the MirthConnect package from. Can be one of 'rpm', 'source', or 'yum'.
  • rpm_source
  • The source of the RPM if using the 'rpm' provider.
  • tarball_source
  • Optional source of the source tarball.
  • Not optional if using the 'source' provider.

Quick Start

  1. Via Yum

    yumrepo { "my mirth repo":
       baseurl  => "http://server/pulp/repos/mirthconnect/",
       descr    => "My Mirth Connect Repository",
       enabled  => 1,
       gpgcheck => 0,
     }
    class { 'mirthconnect':
      provider => 'yum',
    }
    
  2. Via RPM (default)

    class { 'mirthconnect::mirthconnect':
      provider       => 'rpm' # RPM is the default.
      rpm_source     => 'www.foo.com/mirth-1.2.1.rpm' # change the source RPM
      admin_password => 'foo',
    }
    
  3. Using MySQL instead of derby

    $override_options = {
      'mysqld' => {
        'lower_case_table_names' => '1' ,
      }
    }
    
    $mysql_root_password = 'somerootpass'
    $mirthdbuser = 'mirth'
    $mirthdbpass = 'mirthdbpass'
    $mirthdbname = 'mirthdb'
    
    class { '::mysql::server':
      root_password    => $mysql_root_password ,
      override_options => $override_options ,
    }->
    
    mysql::db { $mirthdbname:
      user     => $mirthdbuser,
      password => $mirthdbpass,
      host     => 'localhost',
    }
    
    class {'mirthconnect':
      db_host        => 'localhost',
      db_user        => $mirthdbuser,
      db_pass        => $mirthdbpass,
      db_provider    => 'mysql',
      db_port        => '3306',
      db_dbname      => $mirthdbname,
      admin_password => $mirth_admin_password,
      provider       => 'rpm',
    }
    
    Mysql_grant["${mirthdbuser}@localhost/${mirthdbname}.*"] -> Service['mirthconnect']
    

Hiera

mirthconnect::admin_password: 'admin'
mirthconnect::db_dbname:      'mirthdb'
mirthconnect::db_host:        'localhost'
mirthconnect::db_pass:        'abc1234'
mirthconnect::db_port:        '3306'
mirthconnect::db_provider:    'mysql'
mirthconnect::db_user:        'mirth'
mirthconnect::provider:       'rpm'
mirthconnect::rpm_source:     'www.foo.com/mirth.rpm'
mirthconnect::tarball_source: 'www.foo.com/mirth.tar.gz'

Testing

  • Run the default tests (puppet + lint)

      bundle install
      bundle exec rake
    
  • Run the beaker acceptance tests

Due to licensing issues, I cannot distribute the MirthConnect RPM.

    $ for i in `ls spec/acceptance/*_spec.rb`; do echo $i; MIRTH_YUM_URL=http://my.foo.com/yum/ bundle exec rspec $i | grep -A 150 Destroying\ vagrant\ boxes; done