Supported operating systems, databases, etc., are the same as for the Server installation, and you can see them here: Supported platforms. You need to use an external database - HSQLDB is not supported.

ノード要件

Those specific to Data Center include requirements for nodes that create the cluster:

Yes. Crowd Data Center relies on a load balancer to balance the traffic between the nodes, and this guide assumes that you already have one set up. You can use a load balancer of your choice, just make sure it meets these requirements:

"クッキー ベースのセッション アフィニティ" ("スティッキー セッション" としても知られる) をサポートする必要があります。

利用可能なノードのいずれかへ HTTP/HTTPS トラフィックをルーティングできる。

ノードが利用可能かどうかを決定し、必要に応じてリクエストを他のノードへルーティングできる。

すべてのアトラシアン アプリケーションやその他の REST クライアントは、ロード バランサ経由でノードにアクセスする必要があります。

または、プロキシをロード バランサに変えてもかまいません。

Many bigger installations of Crowd already have a reverse proxy configured, and many reverse proxies can do load balancing as well. We've provided some examples on how to use your proxy as a load balancer. See Load balancer examples.

Restart the node, and then try opening different pages in Crowd. If the load balancer is working properly, you should have no problems with accessing Crowd.

In Crowd, go to > Clustering. The node should be listed as part of the cluster.

tip/resting
Created with Sketch.

If your load balancer supports health checks, configure it to perform a check on http://<crowd-node>:8095/<context-path>/status, where <crowd-node> is the node's hostname or IP address, and <context-path> is the Crowd's context path (e.g. /crowd). If the node doesn't respond with a 200 OK response within a reasonable time, the load balancer shouldn't direct any traffic to this node.

After you've added the node to the load balancer, configure the Crowd's base URL to also point to the load balancer. Go to > General, and enter the URL of your load balancer as Base URL.

4. 残りのノードをクラスターに追加します。

Copy the Crowd installation directory to the new node.

Create a home directory, like you did for the first node, and mount shared as its sub-directory.

Edit crowd-init.properties, and enter the path to the home directory that you just created.

The crowd-init.properties file is in <installation-directory>\crowd-webapp\WEB-INF\classes\.

Go to <installation-directory>/apache-tomcat/conf/Catalina/localhost, and delete the openidserver.xml file. This is needed because currently the CrowdID component doesn't support clustering, and it must be enabled only on the first node. The component will work as usual.

Start Crowd. It will read the configuration from the shared directory, and start without any extra setup.

Take a look around the new Crowd instance. Verify that user and group management, directory synchronization, and any custom integrations all work as expected.

Again, verify that the node was added to the cluster. In Crowd, go to > Clustering.

If everything looks fine, you can configure your load balancer to start routing traffic to the new node. Once you do this, you can make a couple of changes in one Crowd instance to see if they're visible in other instances as well.

その他

Adding node names

When displaying information about your nodes in the Crowd footer or on the > Clustering page, Crowd Data Center uses random IDs that were generated for your nodes. Instead, you can give them more persistent and readable names by setting the cluster.node.name system property, like in the following example: