Documentation for JIRA 4.2. Documentation for other versions of JIRA is available too.
For long-term use, JIRA should be configured to automatically restart when the operating system restarts. For Windows servers, this means configuring JIRA to run as a Windows service.
If you are running JIRA Standalone on Linux and want to start it automatically, please refer to Starting JIRA Standalone automatically on Linux instead.
Running JIRA as a Windows service has other advantages. When started manually a console window opens, and there is a risk of someone accidentally shutting down JIRA by closing this. Also, the JIRA logs are properly managed by the Windows service (found in logs\stdout*.log
in your JIRA Home Directory, and rotated daily).
JIRA をサービスとしてインストールするには、インストーラー経由および手動の二通りの方法があります。
On this page:
The easiest way to get JIRA installed as a Windows service is by clicking the 'Install JIRA as Service' checkbox when running the Windows installer:
このインストレーションプロセスを成功させるには、お使いの Windows オペレーティングシステムにおける完全な管理者権限が必要となります。
If you didn't use the Windows installer, or for some other reason have JIRA Standalone and now want it to run as a service, follow these instructions. They apply only to JIRA running in the Apache Tomcat application server (e.g. the JIRA "Standalone" distribution).
If you are running 64-bit Windows, please note that Apache Tomcat cannot run as a Windows service if you are using a 64 bit JDK (see JRA-12965). Please ensure that you are using a 32 bit JDK (if you used the Windows Installer, a 32 bit JDK has already been installed for you).
On Windows Vista or any other operating system with User Account Control (UAC), you must either disable UAC or right-click on cmd.exe and select "Run as administrator" in order to run the following script. If UAC is enabled, being logged on with an Administrator account is not sufficient.
echo %JAVA_HOME%
.service.bat install JIRA
tomcat6 //US//JIRA --Startup auto
To see what parameters the JIRA service is starting with, Go to Start -> Run, and run "regedt32.exe". There should be an entry at HKEY_LOCAL_MACHINE -> SOFTWARE -> Apache Software Foundation -> Procrun 2.0 -> JIRA.
tomcat6 //US//service_name --JvmMx 512
tomcat6 //US//service_name ++JvmOptions="-Djira.jelly.on=true"
tomcat6 //US//service_name ++JvmOptions="-XX:MaxPermSize=128m"
tomcat6 //US//service_name ++JvmOptions="-Xloggc:path\to\logs\atlassian-gc.log"
tomcat6 //US//service_name ++JvmOptions="-Xloggc:c:\jira\logs\atlassian-gc.log"
See the Tomcat documentation for further service options.
JIRA が Windows インストーラーを通じてインストールされた場合、Windows の'コントロールパネル' から、'プログラムの追加または削除' をクリックして、JIRA を削除します。これによって、サービスも削除されます。
手動でサービスをインストールした場合(上記参照)、以下の手順でアンインストール可能です:
service.bat remove JIRA
上記が動作しない場合、tomcat6 //DS//JIRA
を使用します。
If you are using mapped network drives for JIRA's backup directory, attachments directory, index directoy or the %CATALINA_HOME%* directory, you need to ensure that JIRA can write to these drives. That is, these directories all need to be writeable by the user which the JIRA service is running as. This may mean that you need to change the Windows user that the JIRA server uses.
Also note that you must also specify these network drives by UNC and not letter mappings, e.g. \\backupserver\jira not z:\jira
To change the Windows user that the JIRA service uses, navigate to the service in Windows, i.e. 'Control Panel' -> 'Administrative Tools' -> 'Services'. Locate the 'Atlassian JIRA' service, right-click and view the 'Preferences'.
'ログオン' タブに行き、希望のユーザに変更します。
相互依存的なサービスを有する場合は、それらを正しい順序で起動する事が重要です。以下は、一般的な例です:以下は、一般的な例です:
To set up start up dependency rules, open a command prompt and enter the following command:
C:\Documents and Settings\Developer>sc config [JIRA service] depend=[database service]
Please note the space character after 'depend='
.
If you wish, you can also set up dependency rules by editing the system registry. Please see http://support.microsoft.com/kb/193888 for details on how to do this.
お使いの JIRA サービスあるいはデータベースサービスの正確な名前が分からない場合、以下の手順に従う事でそれらを見つけられます:
%JAVA_HOME%/bin
. There are two options to resolve this problem:
/temp
および /work
ディレクトリを変更して、このユーザーに読み取りおよび書き込み許可を与えます。