[JIRA] The latest Linux version jira6.3.6 is used to install Chinese-based cracking and data migration.

[JIRA] The latest Linux version jira6.3.6 is used to install Chinese-based cracking and data migration.

Preface:

JIRA is an excellent problem tracking management software tool developed by Atlassian, Australia. It can track and manage various types of problems, including defects, tasks, requirements, and improvements. JIRA adopts J2EE technology and can be deployed across platforms. It is widely used by open-source software organizations and world-renowned companies.

JIRA is a complete and powerful product, with simple installation and configuration, multi-language support, user-friendly interface, and excellent integration with other systems such as CVS, Subversion (SVN), VSS, LDAP, and email services, complete documentation, excellent availability and scalability, and complete user permission management.

Environment: jira software, 192. xx8.171.xx0; jira database, 192. xx8.171.xx2.

1. Download

Official Website: https://www.atlassian.com/software/jira/download. only the installation packages under windows are displayed. Click here? All JIRA download options: Open the linux download page and select JIRA 6.3.6 (TAR. GZ Archive. Wget requests.

2. Install jdk 2.1

Install tomcat environment in Linux, refer to: http://blog.csdn.net/mchdba/article/details/23769731

Install jdk environment in Linux, see: 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. decompress and install

Tar-xvf atlassian-jira-6.3.6.tar.gz

Cd atlassian-jira-6.3.6-standalone

Because port 8080 is occupied, an error is reported when jira is started. xml, you need to change the default port 8080 to port 8081, which is about to be attached to line 49th of the file. The modification method is as follows:

# Check whether 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

# <Connector port = "8080 ",

<Connection port = "8081"

[Root @ name01 conf] # more server. xml | grep 8080

[Root @ name01 conf] # more server. xml | grep 8081

<Connection port = "8081"

[Root @ name01 conf] #

Configure 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] #

The Tomcat container where jira is located has been started successfully.

Open the web site http://192.xx8.171.xxx: 8081/, the background tomcat log error is as follows:

18:46:02 org. apache. catalina. core. StandardServer await

Severe: 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. <init> (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)

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'

Reset jira. home, set it to not in the jira Installation Software Directory, restart the jira service, open the jira URL, and click OK. The page is displayed as follows:

3. Chinese

The specification package is: kernel, pay attention to jdk version for jdk 1.6 series,/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.xxx. 171. xx0: 8081/secure/SetupDatabase! Default. jspa, you will see the following Chinese interface:

4. JIRA Configuration

First, create a 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 click the "Next" button, as shown in:

The jdbc driver package mysql-connector-java-5.1.25-bin.jar needs to be copied to the/home/jira/atlassian-jira-6.3.6-standalone/atlassian-jira/WEB-INF/lib directory and then restarted with the following error message:

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, restart jira, and reconfigure

PS: Chinese after the error, because there is a problem with the Chinese version, the JIRA-Language-STD-CN.jar Chinese package into a new JIRA-6.3.3-language-pack-zh_CN.jar Chinese package:

Http://download.csdn.net/download/mchdba/7943421,Configure the database first, as shown in:

After the database is configured, enter the program title on the new interface and click "back ".

Enter a temporary authorization code for registration:

Enter the Administrator account and password after registration.

Then configure the email server and click "finish", as shown in the following figure,

After JIRA is installed, the JIRA Management page is automatically displayed as follows:

5. Crack authorization

Click the Gear Shape management icon in the upper right corner, select "system", and then select "authorize". The usage date is less than one month, as shown below:

Replace the atlassian-extras-2.2.2.jar in the attachment with the \ atlassian-JIRA \ WEB-INF \ lib jar package of the same name in your jira installation directory. The cracking package is: http://download.csdn.net/detail/mchdba/7950429.

Enter the authorization code. The authorization code parameters are as follows:

Description = JIRA: Commercial,

CreationDate = your installation date, format (yyyy-mm-dd ),

Jira. LicenseEdition = ENTERPRISE,

Evaluation = false,

Jira. LicenseTypeName = policcial,

Jira. active = true,

LicenseVersion = 2,

MaintenanceExpiryDate = the expiration date you want to set, for example, 2099-12-31,

Organisation = joiandjoin,

SEN = Note that the SEN you applied has no prefix LID,

ServerID = The ServerID you applied,

Jira. NumberOfUsers =-1,

LicenseID = LID the SEN you applied for. Note that the LID prefix should not be discarded,

LicenseExpiryDate = the expiration date you want to set, for example, 2099-12-31,

PurchaseDate = your installation date, in the format of yyyy-mm-dd)

This installation authorization code instance is:

Description = JIRA: Commercial,

CreationDate = 2014-09-20,

Jira. LicenseEdition = ENTERPRISE,

Evaluation = false,

Jira. LicenseTypeName = policcial,

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

Zxbpi2a682134dpqr/a0rZJS5VmuC0XOBNnjAH/s5bGFxBxABmkcqzzQu2jRTd3bEZaFZvE + AnYzR

JDYWNeDM64G9d1aPJ4TeXxOlOK7cbZbjrbNgkyGwwtg + rbvJpBkHikAR0Adytt0XzFV7R5Y + qQzV

KWZIoVK5FQsWq03YrvdkN/Ekz3S4SXlcpRswPrDdPD/aT + P1nzDMC0CFQCM9 + 0 LlHVNnZQnSTwuR

O3eK + 2gVgIUCteTs4Q3khIgrnsY64hxYB/d8bM = X02dh,

LicenseExpiryDate = 2099-12-31,

PurchaseDate = 2014-09-20

Enter the above authorization code information in the authorization code input box and click "add", as shown below:

Then, when the authorization information is updated, the attack is successful and the following successful information is displayed, such:

6. Restore data

Enter the authorization code:

AAABBw0ODAoPeNptkFtLxDAQhd/zKwI + R9Kwy66FPKxthGhvtF0p4kuso0a6sUwvuP/edissyj4MD

HPOfHOYqzu0tICWeoJy4a + FzzkNwpIK7q1ICF2Ntu3tl5P3Ot89 + 1SNphnMPCEBwqkJTQ9y9jN + w

Zxbpi2a682134dpqr/a0rZJS5VmuC0XOBNnjAH/s5bGFxBxABmkcqzzQu2jRTd3bEZaFZvE + AnYzR

JDYWNeDM64G9d1aPJ4TeXxOlOK7cbZbjrbNgkyGwwtg + rbvJpBkHikAR0Adytt0XzFV7R5Y + qQzV

KWZIoVK5FQsWq03YrvdkN/Ekz3S4SXlcpRswPrDdPD/aT + P1nzDMC0CFQCM9 + 0 LlHVNnZQnSTwuR

O3eK + 2gVgIUCteTs4Q3khIgrnsY64hxYB/d8bM = X02dh

Click recover to start data recovery, as shown below:

In Linux, the 24 m jira data file is imported very quickly and completed in 4 minutes, as shown below:

If the Import fails:

An error occurred while parsing the file. The imported file is incorrect. It may be because the file contains an older version of CDATA (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.

Solution: select the Disable button instead of the Enable button, as shown below:

Therefore, JIRA's latest Linux version 6.3.6 has been installed for cracking and data migration.

Reference: http://www.linuxidc.com/Linux/2014-08/105586p3.htm