JIRA is an excellent issue tracking and management software tool developed by Atlassian in Australia , which can track and manage various types of issues, including defects, tasks, requirements, improvements, etc. JIRA uses J2EE technology and can be deployed across platforms. It is being used by a wide range of open source software organizations, as well as well-known companies around the world.
JIRA products are very complete and powerful, with simple installation and configuration, multi-language support, very friendly interface, and very good integration with other systems such as CVS, Subversion (SVN), VSS, LDAP, and mail services, complete documentation, availability and scalability. Aspects are very good, with complete user rights management.
Environment: jira software, 192.xx8.171.xx0; jira database, 192.xx8.171.xx2.
1. Download
Official website download address: https://www.atlassian.com/software/jira/download , only see the installed version under the window, this time you need to click? All JIRA download options option, open the linux download page bar options, select JIRA 6.3 .6 (TAR.GZ Archive) to download. wget http://www.atlassian.com/software/jira/downloads/binary/atlassian-jira-6.3.6.tar.gz , but the download is slow, you can go to my Baidu cloud network disk address http://pan .baidu.com/s/1eQgTYKE download.
2. Installation
2.1, install the jdk environment
Install tomcat environment under Linux, refer to: http://blog.csdn.net/mchdba/article/details/23769731
Install jdk environment under Linux, reference: http://blog.csdn.net/mchdba/article/details/38768513
2.2, create a directory
mkdir –p / home / jira
mv /root/atlassian-jira-6.3.6.tar.gz ./
2.3, unzip the installation
tar -xvf atlassian-jira-6.3.6.tar.gz
cd atlassian-jira-6.3.6-standalone
Because port 8080 is already occupied, an error will be reported when jira is started. When server.xml is found, you need to change the default port 8080 to 8081, which is probably in the attachment on line 49 of the file. The modification method is as follows:
#First check if port 8081 is occupied
[root@name01 conf]# lsof -i:8081
[root@name01 conf]#
[root@name01 conf]# vim /home/jira/atlassian-jira-6.3.6-standalone/conf/server.xml
#，
[root@name01 conf]# more server.xml |grep 8080
[root@name01 conf]# more server.xml |grep 8081
[root@name01 conf]#
Place jira_home
vim /home/jira/atlassian-jira-6.3.6-standalone/atlassian-jira/WEB-INF/classes/jira-application.properties
jira.home = / home / jira_home
2.4, start jira
[root@name01 bin]# /home/jira/atlassian-jira-6.3.6-standalone/bin/start-jira.sh
To run JIRA in the foreground, start the server with start-jira.sh -fg
……
Server startup logs are located in /home/jira/atlassian-jira-6.3.6-standalone/logs/catalina.out
Using CATALINA_BASE: /home/jira/atlassian-jira-6.3.6-standalone
Using CATALINA_HOME: /home/jira/atlassian-jira-6.3.6-standalone
Using CATALINA_TMPDIR: /home/jira/atlassian-jira-6.3.6-standalone/temp
Using JRE_HOME: /usr/lib/jvm/jdk1.6.0_35/jre
Using CLASSPATH: /home/jira/atlassian-jira-6.3.6-standalone/bin/bootstrap.jar:/home/jira/atlassian-jira-6.3.6-standalone/bin/tomcat-juli.jar
Using CATALINA_PID: /home/jira/atlassian-jira-6.3.6-standalone/work/catalina.pid
Tomcat started.
[root@name01 bin]#
You can see that the Tomcat container where jira is located has been started successfully.
Open the URL http://192.xx8.171.xxx:8081/ , the background tomcat log reports the following error:
2014-9-17 18:46:02 org.apache.catalina.core.StandardServer await
严重: StandardServer.await: create[localhost:8005]:
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)
at java.net.ServerSocket.bind(ServerSocket.java:328)
at java.net.ServerSocket.(ServerSocket.java:194)
at org.apache.catalina.core.StandardServer.await(StandardServer.java:427)
at org.apache.catalina.startup.Catalina.await(Catalina.java:777)
at org.apache.catalina.startup.Catalina.start(Catalina.java:723)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:321)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455)
2014-9-17 18:46:02 org.apache.coyote.AbstractProtocol pause
The error message on the page is as follows:
JIRA Startup Failed
Configured jira.home '/home/jira/atlassian-jira-6.3.6-standalone' must not be a parent directory of the webapp servlet path '/home/jira/atlassian-jira-6.3.6-standalone/atlassian-jira '
***************************************************************************************************************************************************************************************
Configured jira.home '/home/jira/atlassian-jira-6.3.6-standalone' must not be a parent directory of the webapp servlet path '/home/jira/atlassian-jira-6.3.6-standalone/atlassian-jira '
Re-set jira.home, set it to not be in the jira installation software directory, then restart the jira service, open the jira website, OK, you can see the page as follows:
3. Chinese
The download address of the Chinese package is: http://download.csdn.net/detail/mchdba/7941381 , copy the JIRA-Language-STD-CN.jar Chinese package to the linux jira installation directory, and note that the jdk version is jdk1 when starting .6 series, under /home/jira/atlassian-jira-6.3.6-standalone/atlassian-jira/WEB-INF/lib, then restart the jira service
/home/jira/atlassian-jira-6.3.6-standalone/bin/shutdown.sh
/home/jira/atlassian-jira-6.3.6-standalone/bin/start-jira.sh
Open http://192.168.171.230:8081/secure/SetupDatabase!default.jspa again , and you will see the following Chinese interface:
4, jira placement
First create the jira database and account password:
mysql> CREATE DATABASE `jira636` /*!40100 DEFAULT CHARACTER SET utf8*/;
Query OK, 1 row affected (0.13 sec)
mysql> GRANT ALL ON jira636.* TO jira_user@'%' IDENTIFIED BY 'jira_user0919';
Query OK, 0 rows affected (0.38 sec)
mysql>
Configure the database connection information on the interface, and then click the "Next" button, as shown in the following figure:
If an error is reported, class not found: com.mysql.jdbc.Driver
You need to copy the jdbc driver package mysql-connector-java-5.1.25-bin.jar to the /home/jira/atlassian-jira-6.3.6-standalone/atlassian-jira/WEB-INF/lib directory, then restart, The error message is as follows:
JIRA Startup Failed
org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT pluginkey, pluginenabled FROM pluginstate (Table 'jira636.pluginstate' doesn't exist)
Solution: delete the database configuration file dbconfig.xml, then restart jira, reconfigure
PS: The error is reported after the sinicization, because there is a problem with the sinicized version. Replace the JIRA-Language-STD-CN.jar sinicization package with JIRA-6.3.3-language-pack-zh_CN.jar. The download address of the new sinicization package is:
http://download.csdn.net/download/mchdba/7943421 , configure DB first, as shown in the following figure:
After configuring the database, enter the program title in the new interface and click the "Backward" button
Enter the temporary authorization code to register:
After registration, fill in the administrator account and password
After configuring the mail server, click the "Finish" button as shown below,
After that, the JIRA installation is officially completed, and the following automatically jumps to the JIRA management page, as shown below:
5. Crack the authorization
Click the gear-shaped management icon in the upper right corner, select "System", and then select "Authorization", and see that the use date is less than 1 month, as shown below:
Replace the atlassian-extras-2.2.2.jar in the attachment with the jar package of the same name in \atlassian-jira\WEB-INF\lib in your JIRA installation directory. The download address of the crack package is: http://download.csdn.net /detail/mchdba/7950429 .
Fill in the authorization code. Examples of authorization code parameters are as follows:
Description=JIRA: Commercial,
CreationDate=your installation date, format (yyyy-mm-dd),
jira.LicenseEdition=ENTERPRISE,
Evaluation=false,
jira.LicenseTypeName = COMMERCIAL,
jira.active = true,
licenseVersion=2,
MaintenanceExpiryDate=The expiration date you want to set, such as: 2099-12-31,
Organization=joiandjoin,
SEN = Note that the SEN you applied for has no prefix LID,
ServerID=ServerID you applied for,
jira.NumberOfUsers=-1,
LicenseID=LID The SEN you applied for, be careful not to lose the LID prefix,
LicenseExpiryDate=The expiration date you want to set, such as: 2099-12-31,
PurchaseDate=your install date, format (yyyy-mm-dd)
An example of the authorization code for this installation is:
Description=JIRA: Commercial,
CreationDate=2014-09-20,
jira.LicenseEdition=ENTERPRISE,
Evaluation=false,
jira.LicenseTypeName = COMMERCIAL,
jira.active = true,
licenseVersion=2,
MaintenanceExpiryDate=2099-12-31,
Organisation=pl,
SEN = SEN-L4572887,
ServerID = BPT3-4QRK-FCRR-HEP3,
jira.NumberOfUsers=-1,
LicenseID=AAABBw0ODAoPeNptkFtLxDAQhd/zKwI+R9Kwy66FPKxthGhvtF0p4kuso0a6sUwvuP/edissyj4MD
HPOfHOYqzu0tICWeoJy4a + FzzkNwpIK7q1ICF2Ntu3tl5P3Ot89 + 1SNphnMPCEBwqkJTQ9y9jN + w
zxBPi2a68jW4DpQr/a0rZJS5VmuC0XOBNnjAH/s5bGFxBxABmkcqzzQu2jRTd3bEZaFZvE+AnYzR
JDYWNeDM64G9d1aPJ4TeXxOlOK7cbZbjrbNgkyGwwtg+rbvJpBkHikAR0Adytt0XzFV7R5Y+qQzV
kWZIoVK5FQsWq03YrvdkN/Ekz3S4SXlcpRswPrDdPD/aT+P1nzDMC0CFQCM9+0LlHVNnZQnSTwuR
O3eK+2gVgIUCteTs4Q3khIgrnsY64hxYB/d8bM=X02dh,
LicenseExpiryDate=2099-12-31,
PurchaseDate=2014-09-20
Fill in the above authorization code information into the authorization code input box, and click the "Add" button, as shown below:
After that, if you see that the authorization information is updated, it means that the crack is successful, and you will see the following success information, as shown below:
6. Recover data
Enter the authorization code:
AAABBw0ODAoPeNptkFtLxDAQhd/zKwI+R9Kwy66FPKxthGhvtF0p4kuso0a6sUwvuP/edissyj4MD
HPOfHOYqzu0tICWeoJy4a + FzzkNwpIK7q1ICF2Ntu3tl5P3Ot89 + 1SNphnMPCEBwqkJTQ9y9jN + w
zxBPi2a68jW4DpQr/a0rZJS5VmuC0XOBNnjAH/s5bGFxBxABmkcqzzQu2jRTd3bEZaFZvE+AnYzR
JDYWNeDM64G9d1aPJ4TeXxOlOK7cbZbjrbNgkyGwwtg+rbvJpBkHikAR0Adytt0XzFV7R5Y+qQzV
kWZIoVK5FQsWq03YrvdkN/Ekz3S4SXlcpRswPrDdPD/aT+P1nzDMC0CFQCM9+0LlHVNnZQnSTwuR
O3eK+2gVgIUCteTs4Q3khIgrnsY64hxYB/d8bM=X02dh
Click Recover to start recovering data as follows:
The 24M jira data file under Linux is imported very quickly, and the import is completed in 4 minutes, as shown below:
If the import reports an error:
An error occurred while parsing the file. Your import file is incorrect. Probably due to an old version of CDATA in the file (http://jira.atlassian.com/browse/JRA-4980). Exception error org.xml.sax.SAXParseException; lineNumber: 168270; columnNumber: 16; XML document structures must start and end within the same entity.
Workaround: Select the Disable button instead of the Enable button as follows:
Sincerely, JIRA's latest Linux version 6.3.6 installation, cracking and data migration have been successfully completed.
Reference document: http://www.linuxidc.com/Linux/2014-08/105586p3.htm