Completing the Mingle configuration wizard
Now you're ready to open a web browser and complete the Mingle configuration wizard.
If you want Mingle to be able to send email, you will need to know the details of an existing SMTP (outbound email) server. If you don't have these details, please contact your organization's email server administrator.
Please be aware that the database needs to be setup prior to install Mingle.
The Welcome to Mingle page should open in your browser automatically at this stage.
If you have the database ready, select the checkbox. Then the Continue button will be enabled to allow you to proceed with the installation.
Step 1 - Connecting to a database
If you have not installed a database you will need to do this before completing this step. If you have already configured a database for Mingle (e.g. if you're upgrading or re-installing) the wizard may skip this step.
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.
- From the Database droplist select PostgreSQL or Oracle. When a database is selected the default options for that database will be displayed. You may update the defaults. Some specifics about your database will also need to be entered.
- In the Database host or Machine name field type the name or the address of your database server. By default this is set up to run on the installation server i.e. localhost.
- In the Database port or Listener port field, if you want to run Mingle on a port other than the default set up for PostgreSQL or Oracle, update the port number.
- In the Database name or Database instance name field use the default name or update this with the name of the database you created for use with Mingle.
- In the Database username or Username field use the default username or update this with the name of the user you created for use with Mingle.
- In the Database password or Password field, if you have set up a password, enter it here.
- Click the Continue button. Mingle checks the database credentials you entered, and if correct, Mingle will display the Set up the database page.
When using Mingle with an Oracle database a password is required.
If the connection test failed, check to ensure you entered the correct username, password, and database name. Also ensure that the PostgreSQL or Oracle database server is running.
Step 2 – Setting up the database
Click the Continue button.
When Mingle finishes setting up the database, then the Configure the URL page will be displayed.
If you are upgrading or re-installing Mingle, the wizard may skip this step.
Step 3 - Configuring the URL
Enter the URL information for your Mingle instance.
- Site URL is the URL that users of Mingle will use to access your Mingle instance. This URL is used in all outbound communication with Mingle users. For example, users can subscribe to email changes in Mingle. When Mingle sends an email about a change, the email will include links back to Mingle for additional information. These links are generated using the site URL that you enter here.
- Secure site URL is a secure (https) URL to your Mingle instance. This URL is used in secure outbound communications with external systems. For example, any OAuth communication will occur using the secure site URL. If the site URL that you entered is an https URL and you leave the secure site URL blank, then the site URL will be used as the secure site URL. If the site URL is not an https URL and you leave the secure site URL blank, then any functionality that requires secure communication will not be enabled. Currently, OAuth communication is the only area in Mingle which requires secure communication.
Additional information about the site URL and the secure site URL can be found in advanced mingle configuration.
If you have an alternate app context configured, you should not include this in either the site URL or the secure site URL. For example, suppose you have an alternate app context of "/mingle" and the URL to open Mingle in your browser is, "http://your_mingle_server.com:8080/mingle" then your site URL should be, "http://your_mingle_server.com:8080".
Step 4 - Configuring the SMTP connection
Configure the SMTP connection
The SMTP connection settings can be edited by a Mingle administrator at any time by clicking on the Email link from the instance Admin menu.
Complete details for the SMTP (outbound email) server. For details of the values to enter here, please contact your organization's email server administrator.
- Type or update the SMTP server address.
- Type or update the SMTP server port number. Typical ports are 25 and 587.
- Type or update the SMTP domain.
- If your organization's SMTP server requires a user name and password, type them here.
- If your organization's SMTP server requires TLS encryption, be sure to tick the TLS checkbox.
- Type the email Sender address from which you want Mingle to send emails (this will also become the Reply To address).
- Type the Sender name from whom you want Mingle to send emails.
Step 5 - Accepting the ThoughtWorks End User License Agreement
Read through the license terms, select the Accept license as above checkbox.
Click the Continue button. Then Mingle will display the Set up the first user account page.
Step 6 - Setting up the first user account
Complete all of your details on this page, ensuring that you follow each of the instructions next to the field names.
Click the Continue button. Then Mingle will display the Import project templates page.
Step 7 - Importing project templates
Project templates allow you to quickly create new projects.
Click the Continue button. Then Mingle will display the Register your license page.
Step 8 - Managing your Mingle license
Managing your license
Anonymous access and Mingle licenses
To enable anonymous access on a appropriately licensed instance see project settings.
Numbers for full and light users
Each Mingle license indicates the maximum number of active full and light users that can be created on that instance. If the active number of full or light users exceeds the maximum allowed the instance will be incorrectly licensed.
In some scenarios administrators are prevented from exceeding the maximum user allowance. In these scenarios a warning banner will be shown to indicate that no more users can be activated until the license has been updated or the active user count decreased.
Beginning with Mingle 2.3 any available full user seats can be used to activate full or light users. This means that even if you have not specifically purchased a light user seat you will be able to use a full user seat to register a light user.
Incorrectly licensed Mingle instances and resolving any licensing issues
Mingle instances that are incorrectly licensed will have limited functionality. There are number of scenarios that cause a Mingle instance to be incorrectly licensed and the impact of having an incorrectly registered Mingle instance depends on how the license is invalidated.
- No license - all users will be set as light users, no new users or new projects can be created, any anonymous access projects will be inaccessible to anonymous users. This may only be resolved by registering a valid license.
- Expired license - all users will be set as light users, no new users or new projects can be created, any anonymous access projects will be inaccessible to anonymous users. This may only be resolved by registering a valid license.
- Too many full users - all users will be set as light users, no new users or new projects can be created. This may be resolved by registering a valid license or deactivating the excess full users.
- Too many light users - all users will be set as light users, no new users or new projects can be created. This may be resolved by registering a valid license or deactivating the excess light users.