Search results

...setup a single Guard instance on an existing Open-Xchange installation, no cluster ...uard server should include the url suffix /guardadmin . In the event of a cluster setup, any Guard server can be referenced here, as it is not session specif

...palived (see below) we can also chose to pick a master node based on their cluster index. This way only cluster nodes which are <code>Synced</code> will be considered available.

...tasked with designing and maintaining the configuration of an OX server or cluster, information contained in this document will acquaint you with options in O

...nstances can be clustered. One DCS cluster is always tied to one Hazelcast cluster of Middleware nodes. ...1 DCS runs ActiveMQ Failover is used to form a symmetric high availability cluster. The Middleware initially connects to a random DCS. Should a DCS disappear

Abuse Shield runs on a cluster of servers, and integrates with authenication systems to detect abuse, brut ...tered architecture – Login reports are shared between all the servers in a cluster so there is a single view of abuse

= Running multiple WHM/cPanel instances with a single Open-Xchange instance (cluster) = ...possible to run multiple WHM/cPanel instances with a single Open-Xchange (cluster) installation. This, however, requires some extra management which is not p

MariaDB cluster can also be used, which is beyond the scope of this guide.</pre style="colo An IMAP cluster can also be used, but it is beyond the scope of this guide.</pre style="col

...ase that the web server is on a dedicated system or maybe even has its own cluster. The default package is installed on the OX application server, and the sec

If OX Documents functionality is used for guest users in a cluster of application servers, this setting needs to be adjusted to false in order

* Disable Hazelcast cluster discovery

# Alternatively select one or more hosts of your cluster to be restricted to handle only eas/usm requests

# Alternatively select one or more hosts of your cluster to be restricted to handle only eas/usm requests

Failed to distribute permanent listeners among cluster nodes

...environments. For upgrades from earlier versions than 7.10.2 the Hazelcast Cluster requires a complete shutdown, since the internal OX Documents data has chan

...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki> ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki>

...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki> ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki>

...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki> ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki>

...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki> ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki>

...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki> ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki>

...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki> ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki>