Install Extensions

Mirth® Connect by NextGen Healthcare Amazon Web Services (AWS) Preferred Deployment

Use a Shared Keystore Across the Cluster

Upload the keystore file into S3. The file must be accessible by your ECS cluster. Note the Object URL of the file in S3. Include the following environment variables in your ECS configuration: KEYSTORE_DOWNLOAD - The S3 Object URL of the Mirth® Connect keystore file. This file will be downloaded into the container and Mirth® Connect will use it as its keystore. ALLOW_INSECURE - Allow the insecure SSL connections when downloading files during startup. This applies to keystore downloads, plugin downloads, and server library downloads. Parent topic: ECS File Storage

Mirth® Connect by NextGen Healthcare Amazon Web Services (AWS) Preferred Deployment

Install Custom JAR Files Into the server-launcher-lib Folder

Create a zip file containing all the JAR files that you wish to install. Upload the created zip file into S3. The file must be accessible by your ECS cluster. Note the Object URL of the file in S3. Include the following environment variables in your ECS configuration: CUSTOM_JARS_DOWNLOAD - The S3 Object URL of the zip file containing your custom JARs. This file will be downloaded into the container and the JARs will be installed into the server-launcher-lib folder. ALLOW_INSECURE - Allow the insecure SSL connections when downloading files during startup. This applies to keystore downloads, plugin downloads, and server library downloads. Parent topic: ECS File Storage

Mirth® Connect by NextGen Healthcare Amazon Web Services (AWS) Preferred Deployment

ECS File Storage

When running Mirth® Connect by NextGen Healthcare in ECS, the local file system of each container is ephemeral, so certain Mirth® Connect features do not work as usual. Installing extensions, installing custom JAR files into the server-launcher-lib folder, and using a shared keystore across the cluster will not work without additional configuration. To use these features, we recommend storing the appropriate files in S3 and setting environment variables that tell the containers where to download the files from. Install Extensions Install Custom JAR Files Into the server-launcher-lib Folder Use a Shared Keystore Across the Cluster

Mirth® Connect by NextGen Healthcare Amazon Web Services (AWS) Preferred Deployment

Use a Shared Keystore Across the Cluster

Upload the keystore file into S3. The file must be accessible by your ECS cluster. Note the Object URL of the file in S3. Include the following environment variables in your ECS configuration: KEYSTORE_TYPE - The type of keystore, for example, JKS. KEYSTORE_DOWNLOAD - The S3 Object URL of the Mirth® Connect keystore file. This file will be downloaded into the container and Mirth® Connect by NextGen Healthcare will use it as its keystore. ALLOW_INSECURE - Allow insecure SSL connections when downloading files during startup. This applies to keystore downloads, plugin downloads, and server library downloads. OS and CPU/Ram recommendations - depends on research item on S,M,L and XL setups Small Medium Large ECS Task vCPU=2048, 4GB RAM vCPU=2048, 8GB RAM vCPU=4096, 16GB RAM Parent topic: Manual Steps To Setup ECS

Mirth® Connect by NextGen Healthcare User Guide

Install a New Extension

Extensions are packaged into ZIP files. To install an extension in Mirth® Connect: Navigate to the Install Extension from File System section at the bottom of the Extensions view. Select the Browse... button, then select the ZIP file of the extension you would like to install. Select the Install button. If the extension ZIP file is valid, you will see a notification asking you to restart the server: Restart the Mirth® Connect server and launch the Mirth® Connect Administrator again. You will see the new extension listed in either the Installed Connectors Table or Installed Plugins Table, depending on the type of extension you installed. Parent topic: Extensions View

SSL Manager User Guide

Installation

The SSL Manager extension is installed like any other Mirth® Connect by NextGen Healthcare extension. This can be done through the Mirth® Connect Administrator in the Extensions view or by extracting the contents of the provided ZIP file into the extensions directory inside the Mirth® Connect installation directory. For older versions of NextGen® Connect Integration Engine, the plugin can be installed via Plugins Extension Manager. Note: After restarting the server, make sure that you launch the Mirth® Connect Administrator by selecting the Launch Mirth® Connect Administrator button and not using a previously downloaded JNLP file. Note that if you are upgrading from version 3.0.3 or earlier, when you restart the server after installing the SSL Manager, any connectors using SSL may not yet work correctly as additional configuration is needed. For details on installing an extension, see Installing a New Extension in the official NextGen Connect User Guide on the Success Community.

Install Extensions

Recommendations

Use a Shared Keystore Across the Cluster

Install Custom JAR Files Into the server-launcher-lib Folder

ECS File Storage

Use a Shared Keystore Across the Cluster

Install a New Extension

Installation

Install Extensions

Use a Shared Keystore Across the Cluster

Install Custom JAR Files Into the server-launcher-lib Folder

ECS File Storage

Use a Shared Keystore Across the Cluster

Install a New Extension

Installation