The various files and folders present in the installation directory are used to contain application configuration files and other executables.
Other files and folders present in the Installation Directory include the following:
- cli-lib: Libraries used by the Command Line Interface. These should not be changed.
- client-lib: Libraries used by the Mirth Connect Administrator. These should not be changed.
- custom-lib: Custom libraries can be dropped in this folder, to be used by the default library resource.
- docs: Contains license information for Mirth® Connect and all third-party libraries. Also contains the Javadoc documentation used by User API.
- extensions: Extension libraries used by the Server, Administrator, and CLI. These should not be changed.
- logs: This is the default location that server logs will be written into. This can be changed from the log4j2.properties file.
- manager-lib: Libraries used by the Server Manager. These should not be changed.
- mccommand(.exe): The entrypoint script for launching the Command Line Interface.
- mcmanager(.exe): The entrypoint script for launching the Server Manager.
- mcserver(.exe): The entrypoint script for launching the Mirth Connect server in a shell or other custom job.
- mcserver.vmoptions: Entries set here will be added as command-line parameters to the Java process when running mcserver.
- mcservice(.exe): The entrypoint script for launching the Mirth Connect server as a service / daemon.
- mcservice.vmoptions: Entries set here will be added as command-line parameters to the Java process when running mcservice.
- *-launcher.jar: These libraries are used by the entrypoint scripts to launch their respective applications.
- public_api_html: Contains the files used to serve up the REST API documentation.
- public_html: Contains the files used to serve up the launch page, if the Web Dashboard WAR fails to load.
- server-lib: Libraries used by the Mirth® Connect server. These should not be changed.
- server-launcher-lib: JARs in this directory will be loaded into the main server thread context classloader at startup. This is required if you are using any custom log4j2 appender libraries.
- webapps: All WAR files in this directory will automatically be published by the Mirth® Connect web server at startup.
