1. Mirth Connect
2. Home
3. Examples and Tutorials

Created by Rusty Gadberry, last modified by Gerald Bortis on Nov 01, 2010

The following is what I had to do to get Mirth 1.8.0 to run on an IBM iSeries (AS/400) server. This addresses the issue of getting Mirth to run using the Sun SSL provider and making the JVM start using that provider.

1. Create a folder named Mirth. It should be owned by the profile that will be used to install Mirth.

2. Create a profile named Mirth.

3. Use the Windows installer to install Mirth, pointing it to the folder you created on the iSeries server.

4. Back on the iSeries, change the owner of the Mirth directory objects to Mirth.

5. Copy the java.security file located in folder /QIBM/ProdData/Java400/jdk15/lib/security and name it java.security.sun.

6. Change java.security.sun file as follows.

   #
   # List of IBM providers and their preference orders (see above):
   #
   security.provider.1=sun.security.provider.Sun
   #security.provider.2=com.ibm.crypto.provider.IBMJC E
   #security.provider.3=com.ibm.jsse2.IBMJSSEProvider 2
   #security.provider.4=com.ibm.security.jgss.IBMJGSS Provider
   #security.provider.5=com.ibm.security.cert.IBMCert Path
   #security.provider.6=com.ibm.security.sasl.IBMSASL
   #security.provider.7=com.ibm.i5os.jsse.JSSEProvide r
   #
   # List of Sun providers and their preference orders (see above):
   #
   #security.provider.1=sun.security.provider.Sun
   security.provider.2=sun.security.rsa.SunRsaSign
   security.provider.3=com.sun.net.ssl.internal.ssl.P rovider
   security.provider.4=com.sun.crypto.provider.SunJCE
   security.provider.5=sun.security.jgss.SunProvider
   security.provider.6=com.sun.security.sasl.Provider
   #
   # Determines the default key and trust manager factory algorithms for
   # the javax.net.ssl package.
   #
   #
   #ssl.KeyManagerFactory.algorithm=IbmX509
   ssl.TrustManagerFactory.algorithm=PKIX
   #
   # Sun key manager factory
   ssl.KeyManagerFactory.algorithm=SunX509

7. Change Mirth.sh as follows.

   java -Djava.version=1.5 -Dos400.security.properties=/QIBM/ProdData/Java400/jdk15/lib/security/java.security.sun
   -classpath $CLASSPATH com.webreach.mirth.server.launcher.MirthLauncher mirth-launcher.xml

8. Start Mirth by submitting a job. This is done so Mirth will run under the correct profile to avoid authority issues when the Derby database is initially allocated.

   SBMJOB CMD(QSH CMD('/mirth/mirth.sh')) JOB(MIRTH) JOBQ(QSYSNOMAX) USER(MIRTH)

9. Use NETSTAT to verify ports 8080 and 8433 are active.

10. Review mirth log located in /mirth/logs for any errors.

Document generated by Confluence on Nov 11, 2019 08:40

Atlassian