Upgrading from Mingle 2.3
Before you get started
Starting with Mingle 3.0 MySQL will no longer be supported. All existing MySQL users will need to migrate their data to Postgres or Oracle before upgrading to Mingle 3.0. See here for help migrating to Postgres or Oracle.
These instructions are for upgrading from Mingle 2.3 to Mingle 3.0. Look here to see how to upgrade from Mingle 2.3.1 and here to see how to upgrade from Mingle 2.2. Upgrades from earlier versions such as 1.0, 1.1, 2.0, 2.0.1, 2.1 and specifically, the 1.0 Early Access & 2.0 Early Access versions are not supported.
- Please ensure that no-one, other than Mingle administrators completing the upgrade, has access to Mingle during the upgrade process. We expect that the upgrade of Mingle is completed by Mingle administrators only.
- The upgrade to 3.0 involves migration of your existing data which is a very sensitive process. We strongly recommend that you make a backup of the Mingle data directory and your database before starting the upgrade process. DO NOT SHUT DOWN THE SERVER IN THE MIDDLE OF THE UPGRADE PROCESS AT ANY COST.
- ANY TEMPLATES THAT WERE INSTALLED WITH THE PREVIOUS RELEASES WILL BE REPLACED. This has no impact on any of your existing projects or any templates that you have created yourself. If you have modified the pre-installed templates and wish to keep them you must export them and then import them using a different name before the upgrade.
- The Mingle database will be upgraded and any projects in your 2.3 database will be upgraded and fully usable as soon as you start a newly installed 3.0 Mingle server.
- Any old project export files (.mingle files) can be directly imported into the 3.0 version of the application. They will be automatically upgraded upon import.
- If you are migrating to Mingle 3.0 and have properties already called "Created On" and/or "Modified On" these will be renamed to be called "Created On_1" and/or "Modified On_1" and any previous uses of these properties (in Favorites, Formulas etc...) will be updated. Use in MQL (including MQL filters) will not be updated and, as a result, any previous MQL using "Created On" and "Modified On" will now use Mingle's predefined properties of the same name in the query.
Installing the software
Windows
- Note the location of the Mingle data directory and the port on which Mingle is currently running. Typically, the Mingle data directory is in your home directory (C:\Documents and Settings\[username]\Mingle) and the port is 8080.
- Run the Mingle uninstaller to remove your current installation. The uninstaller will stop the Mingle service if it is currently running.
- Run the new installer.
- Specify the same data directory and port as the previous installer.
- Specify a config directory. Unless you specifically need to use another location we recommend using a sub-directory inside the Mingle data directory (such as /dataDir/config) as your config directory. Mingle will automatically move the existing mingle.properties file from the specified data directory to the config directory. The installer will automatically start the new Mingle service when it completes.
- Open your browser to any Mingle page. You will be walked through the upgrade steps. All existing project data will be upgraded for continued use.
If you do not uninstall Mingle manually and try to install a newer version at the same location as an existing installation, Mingle will automatically uninstall the existing installation of Mingle before installing the new version.
OS X
- Note the location of the Mingle data directory and the port on which Mingle is currently running. Typically, the Mingle data directory is in your home directory (C:\Documents and Settings\[username]\Mingle) and the port is 8080. These are both visible from the Mingle launcher application window.
- Stop Mingle and quit the Mingle launcher application.
- Drag the new copy of the Mingle application (Mingle_3_0_xxxxx.app) into your Applications directory (overwriting the old Mingle).
- Start Mingle
- Specify the same data directory and port as the previous installer.
- Specify a config directory. Unless you specifically need to use another location we recommend using a sub-directory inside the Mingle data directory (such as /dataDir/config) as your config directory. Mingle will automatically move the existing mingle.properties file from the specified data directory to the config directory. The installer will automatically start the new Mingle service when it completes.
- Open your browser to any Mingle page. You will be walked through the upgrade steps. All existing project data will be upgraded for continued use.
Linux/Unix (except Solaris)
- Note the location of the Mingle data directory on which Mingle is currently running. This is contained in the mingle.properties file in the Mingle data directory.
- If the Mingle server is currently running, stop it using the './MingleServer stop' command inside the 'mingle' application directory.
- Untar the newly downloaded archive.
- Start Mingle, using './MingleServer --mingle.dataDir=/path/to/your/data start' where /path/to/your/data is the location of your data directory.
- Open your browser to any Mingle page. You will be walked through the upgrade steps. All existing project data will be upgraded for continued use.
Solaris
The steps to install on Solaris are very similar to that on any other UNIX except
- You would use the UNIX zip installer rather than the tar.gz installer due to the fact that the default Solaris tar command is incompatible with the format with GNU tar.
- You will have to ensure that the MingleServer script in the application directory has execute permissions.
After installation is complete...
Configuring Mingle's authentication
The authentication settings for Mingle are controlled through the [mingle_data_directory]/config/auth_config.yml file. This file is created by default on all brand new installations. For a detailed explanation of how to change Mingle's authentication please see here.
Advanced configuration
For further information on configuring Mingle see here.