JIRA Installation

To set up JIRA on server (Windows) through remote desktop connection, first we need to download JIRA from Atlassian. There are JIRA installer and WAR file on Atlassian website. The installer is recommened for convenience.

After finishing the installer download, run the installer and follow the steps described in documentation (i.e. set directories and ports).

After installation, go to JIRA_DIRECTORY and run startup_bundled_jre.bat to start JIRA if your JIRA is not automatically started. To stop JIRA, run shutdown_bundled_jre.bat.

When JIRA is started and a user interface shows up, you will be required to set up JIRA first. For database settings, please refer to the documentation for different databases. Another possibly useful material is a screenshot attached, i.e. JIRA setup - PostgreSQL - local computer.JPG. Note that you need to install the database (also create a user and a database specificly for JIRA) first and then set the databse on JIRA.

Below are some configuration details when I set JIRA on a Windows server.

 

#### Configuration ####

[1] JIRA_DIRECTORY: D:Program FilesAtlassianJIRA
[2] JIRA_HOME: D:Program FilesAtlassianApplication DataJIRA
[3] JIRA_URL: http://localhost:8088
[4] HTTP Port Number: 8088
[5] Control Port Number: 8085
[6] PostgreSQL_DIRECTORY: D:Program FilesPostgreSQL9.3
[7] PostgreSQL_SCRIPTS: D:Program FilesPostgreSQL9.3in

 

#### Notes ####

[1] See JIRA 6.3.11 documentation for installation and setup details.
[2] Install successfully. You can access JIRA via http://xxx.xxx.xxx.xxx:8088.
[3] Set up successfully: email notification, database(PostgreSQL).
[4] The PostgreSQL driver is upgraded from 9.0 to 9.3.

[5] Ensure that ports you set are not occupied by other applications.

 

#### Check ports ####

In a Command Prompt, input "telnet ipAddress portNumber". If "... Could not open connection to the host, on port: ...", then the port is not occupied. Otherwise, the port is used other applications. 

 

#### Debug ####

ERROR: Database password authentication failed.

Solution: Modify Atlassian/Application Data/.../dbconfig.xml