Linux under jira-6.3.6 configuration hack translation Migration database

Each version translation package Https://translations.atlassian.com/dashboard/download

Jira Https://www.atlassian.com/zh/software/jira/download

The latest version of jira-6.3.6 is used here.

Experimental environment

Operating system Red Hat Enterprise Linux Server release 5.9 (64)

Database Mysql:ver 14.14 Distrib 5.6.12, for Linux (x86_64) using Editline Wrapper

1. Software preparation
   Jira-6.3.6-language-pack-zh_cn.jar
   Atlassian-jira-6.3.6-x64.bin
   
   
2. Installation
   Default installation Address
   
   [/opt/atlassian/jira]
   Add MySQL driver mysql-connector-java-5.0.6-bin.jar restart in/opt/atlassian/jira/atlassian-jira/web-inf/lib Jira

View under Use date only 22 days

Write the authorization code, the authorization code parameter example is 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= you want to set the expiration date as: 2099-12-31,

Organisation=joiandjoin,

Sen= you apply to the Sen note there is no prefix lid,

Serverid= you applied to the ServerID,

Jira. Numberofusers=-1,

Licenseid=lid you apply to the Sen, note lid prefix do not throw away,

Licenseexpirydate= you want to set the expiration date as: 2099-12-31,

Purchasedate= your installation date, format (YYYY-MM-DD)

-----This Authorization code format

description=jira:commercial,
CreationDate= 2014-09-21,
Jira. Licenseedition=enterprise,
Evaluation=false,
Jira. Licensetypename=commercial,
Jira.active=true,
licenseversion=2,
maintenanceexpirydate=2099-12-31,
Organisation=joiandjoin,
sen=sen-l4613020,
Serverid=bez9-crk4-7axe-k2ew,
Jira. Numberofusers=-1,
LICENSEID=AAABBQ0ODAOPENPTUETPHDAQVVDXKHIUASTQIOKBOQDCHHTAD2O8VBY1ZRESKRD33WULYUAZH0LM5
Nvml7mob+vv0hmce4kffhcyay9ommngpknatwi63nxzez9w0xpoqvhvbj1vsixwbbldg5z5lavuc
Pjpuf9mpgxrql2ao1ovjarwvvorcnkqpq7wh94coij0hmrc5rmq4jtkfly3vrlheeww7iogm00ey
BWXPVHTW1DFNCHDKRFNC6IS37U1BJNKF8DI2L8ALM8PBVKRLJMACARME3MNNGIAVYUF3KZBRVDCB
UitCjkVzfwbfsUEI7+ Bj3qwjueq80nwa7yf2sh/n/0ax/x7hdatahuajzptr2idwxza4x0xrrhz3
R5gcvwcfgfhw4rgcsf8bjllvdofyhekwtcpx02dd,
licenseexpirydate=2099-12-31,
purchasedate=2014-09-21

It's been 2,099 years since the authorization code was added.

Back to the homepage to see the business license has been

Many times we need to migrate the data to the new version

Here's a summary of my experience.

First click on the system on the old version of the database Settings icon-backup data results just a name here: jira_db

Show data output after completion to: /var/atlassian/application-data/jira/export/jira_db.zip

Now all you have to do is download the Jira_db.zip to local and extract two XML files, Entities.xml and Activeobjects.xml, respectively .

Then copy the two XML files to the new version of the server (this is 6.3.6) on the/var/atlassian/application-data/jira/import folder

Then the system--recovers the data

Perform recovery complete

Download the corresponding version of the package to install the plugin on the line The example of translation online seems a lot

jira6.3.6 version installation + hack + Migration database completed

Linux under jira-6.3.6 configuration hack translation Migration database