Jira Data Center のインストール

These instructions are applicable for installing Jira Software Data Center, or Jira Service Desk Data Center.

Jira Data Center のインストール

This illustration shows the general method of installing a Jira clustered instance:

This install guide assumes that you already have a Jira instance, already have a load balancer, and are able to set up a network file share system.

1. Upgrade or install Jira 7.0 or later

See Jira applications installation guides or the Jira applications upgrade guides.

• If you're installing your instance from scratch, you should generate a non-Data Center evaluation license at the set up stage, and update to your Data Center license when you're adding your cluster properties file at step 3.
• If you're upgrading your instance, update your license at step 3.

2. Set up the Jira file storage location on shared storage

In this step, you need to set up a shared home directory that is writable by the Jira instance and any future nodes.

There are multiple ways to do this, but the simplest is to use an NFS share. The mechanics of setting one is unique from installation to installation, and is outside the scope of this document. We recommend using a UNC file path to your storage location.

この共有ストレージの場所の最終的なマウントポイントは、/data/jira/sharedhome を想定しています。

• ディレクトリは、他の潜在的なノードによる読み取りと書き込みができるようにします。
• 次のディレクトリを /data/jira/sharedhome にコピーします (一部のディレクトリは空の場合もあります)。
  • data
  • plugins
  • logos
  • インポート
  • export

$ cp -R /path/to/jira-local-home/{data,plugins,logos,import,export} /data/jira/sharedhome

3. 既存の Jira インスタンスをクラスター内で動作するように設定する

Set up the following on your existing Jira instance:

1. Stop your instance.

2. Put a cluster.properties file in the local Jira home directory, with contents as follows:

   例を展開

   cluster.properties ファイルの例

   
   

   # This ID must be unique across the cluster jira.node.id = node1 # The location of the shared home directory for all Jira nodes jira.shared.home = /data/jira/sharedhome

   詳細は、Cluster.properties ファイルのパラメーター を参照してください。

   If using the Apache load balancer, set the Apache node name by appending the following setting to the same variable (replacing node1 with the node name used in the load balancer configuration):

   • • -DjvmRoute=node1

3. Start your instance, and install your Data Center license.

4. 最初のノードをロードバランサに追加する

Jira Data Center relies on a load balancer to balance traffic between the nodes. Many larger installations of Jira already have a reverse proxy configured, and many reverse proxies have the ability to perform load balancing as well. We've provided a sample Apache httpd configuration to serve as an example, but please check with your proxy vendor for specific information.

<VirtualHost *:80>
        ProxyRequests off
 
        ServerName MyCompanyServer
 
        <Proxy balancer://jiracluster>
                # JIRA node 1
                BalancerMember http://jira1.internal.atlassian.com:8080 route=node1
                # JIRA node 2  Commented pending node installation
                # BalancerMember http://jira2.internal.atlassian.com:8080 route=node2
 
                # Security "we aren't blocking anyone but this the place to make those changes
                Order Deny,Allow
                Deny from none
                Allow from all
 
                # Load Balancer Settings
                # We are not really balancing anything in this setup, but need to configure this
                ProxySet lbmethod=byrequests
                ProxySet stickysession=JSESSIONID
        </Proxy>
 
        # Here's how to enable the load balancer's management UI if desired
        <Location /balancer-manager>
                SetHandler balancer-manager
 
                # You SHOULD CHANGE THIS to only allow trusted ips to use the manager
                Order deny,allow
                Allow from all
        </Location>
 
        # Don't reverse-proxy requests to the management UI
        ProxyPass /balancer-manager !
        # Reverse proxy all other requests to the JIRA cluster
        ProxyPass / balancer://jiracluster/
        ProxyPreserveHost on
</VirtualHost>

5. Add a new Jira node to the cluster

1. Copy the Jira installation directory to a new host. Atlassian recommends that your configuration deviates from the first installation as little as possible to ease the burden of documentation and deployment (e.g. Installation paths, users, file permissions, etc).
2. Ensure that the new host can access the shared home directory (e.g. ensure that you can read the contents of the shared Jira directory and have write access to it)
3. 最初のノードからこの新しいノードに、ローカルのホーム ディレクトリをコピーします。
4. cluster.properties ファイルが新しいノード ID を参照するように変更します。すべてのノード ID は、ノード間で一意でなければなりません。
5. 新しいノードを起動し、スタートアップの問題がないか監視します。
6. 課題の作成、検索、添付ファイル、およびカスタマイズが期待どおりに動作するか確認します。

6. この新しいノードをロードバランサに接続する

Verify that the new node is in the cluster and receiving requests by checking the logs on each node to ensure both are receiving traffic and also check that updates done on one node are visible on the other.

各ノードで、手順 5 と 6 を繰り返します。

セキュリティ

Ensure that only permitted cluster nodes are allowed to connect to a Jira Data Center instance's ehcache RMI port, which by default is port port 40001, through the use of a firewall and/or network segregation. Not restricting access to the ehcache RMI port could result in the compromise of a Jira Data Center instance.

Cluster.properties ファイルのパラメーター

You can set the following parameters in the cluster.properties file:

If you set ehcache.peer.discovery = automatic then you need to set the following parameters:

• ehcache.multicast.address

• ehcache.multicast.port

• ehcache.multicast.timeToLive

• ehcache.multicast.hostName

これらのパラメーターについての詳細は、Ehcache ドキュメントを参照してください。