Installing Confluence on Windows

 This option will create a space that you and your users can use to get to know Confluence. You can delete this space at any time.

Use this option if you have a full site export of an existing Confluence site. This is useful when you’re migrating to another database or setting up a test site.  

Good to know:

• You can only import sites from the same or earlier Confluence version.
• The system administrator account and all other user data and content will be imported from your previous installation.

In the setup wizard:

• Upload a backup file – use this option if your site export file is small (25mb or less).

• Restore a backup file from the file system – use this option if your backup file is large. Drop the file into your <confluence-home>/restore directory then follow the prompts to restore the backup.

• Build Index – we’ll need to build an index before your imported content is searchable. This can take a long time for large sites, so deselect this option if you would rather build the index later. Your content won't be searchable until the index is built.

Choose this option if you're happy to manage users in Confluence, or don't have a JIRA application installed.

Good to know:

• If you do plan to manage users in a JIRA application, but have not yet installed it, we recommend installing JIRA first, and then returning to the Confluence setup.
• You can add external user management (for example LDAP, Crowd or JIRA) later if you choose.

 Choose this option if you have a JIRA application installed and want to manage users across both applications.

Good to know:

• This is a quick way of setting up your JIRA integration with the most common options. 
• It will configure a JIRA user directory for Confluence, and set up application links between JIRA and Confluence for easy sharing of data.
• You'll be able to specify exactly which groups in your JIRA app should also be allowed to log in to Confluence. Your license tiers do not need to be the same for each application. 
• You'll need either JIRA 4.3 or later, JIRA Core 7.0 or later, JIRA Software 7.0 or later, or JIRA Service Desk 3.0 or later.

In the setup wizard:

• JIRA Base URL – the address of your JIRA server, such as http://www.example.com:8080/jira/ or http://jira.example.com/

• JIRA Administrator Login – this is the username and password of a user account that has the JIRA System Administrator global permission in your JIRA application. Confluence will also use this username and password to create a local administrator account which will let you access Confluence if JIRA is unavailable. Note that this single account is stored in Confluence's internal user directory, so if you change the password in JIRA, it will not automatically update in Confluence.
• Confluence Base URL – this is the URL JIRA will use to access your Confluence server. The URL you give here overrides the base URL specified in Confluence, for the purposes of connecting to the JIRA application.
• User Groups – these are the JIRA groups whose members should be allowed to use Confluence. Members of these groups will get the 'Can use' permission for Confluence, and will be counted in your Confluence license. The default user group name differs depending on your JIRA version:
  • JIRA 6.4 and earlier: jira-users. 
  • JIRA Software 7.x and later: jira-software-users
  • JIRA Core 7.x and later: jira-core-users
  • JIRA Service Desk 3.x and later: jira-servicedesk-users
• Admin Groups – provide one or more JIRA groups whose members should have administrative access to Confluence. The default group is jira-administrators. These groups will get the system administrator and Confluence administrator global permissions in Confluence.