Search results

Multiple Open-Xchange servers can form a cluster with inter-OX-communication over a network. OX App Suite offers a second HTTP based connector for the communication between the HTTP server and the backend. This new connector is based on Ora

The whole cluster communication will now be done through Hazelcast. Please note that even in case of an upd

...ng App Store. Availability will be confirmed by Open-Xchange via the usual communication channels.

...t the TCP port 9090 may be changed. It is used for the directors’ internal communication. *director-admin unix socket used for director admin communication. director-admin unix listener service needs to be configured in dovecot.con

...ease 7.0.1 of OX App Suite, we offer a second HTTP based connector for the communication between the HTTP server and the backend. This new connector is based on Ora [[Appsuite:Grizzly#Cluster_setup]] shows that HTTPS communication is terminated by the Apache balancer in front of the OX backends. To let th

...unning.<br/>But the client is not connected to the server directly.<br/>As communication channel between both nodes JMS is used. * 1x JMS Server for communication

...requirement, customers and support agents have to keep the readable ticket communication, in form of email/article body, subject or attachment names, free from any

== Communication with the server ==

...unning.<br/>But the client is not connected to the server directly.<br/>As communication channel between both nodes JMS is used. * 1x JMS Server for communication

...requirement, customers and support agents have to keep the readable ticket communication, in form of email/article body, subject or attachment names, free from any

[[Appsuite:Grizzly#Cluster_setup]] shows that HTTPS communication is terminated by the Apache balancer in front of the Open-Xchange nodes. To

...pdf2svg''' instances, managing the '''caching''' of conversion results, '''communication''' with remote converters and remote converter caches etc. '''Deployments from 7.10.1 on''' Communication between OX backend and OX Documentconverter is no longer stateful. It is no

...v7<br>Open-Xchange Documents Frontend 7.8.1-rev7<br>Open-Xchange Documents Communication 7.8.1-rev7<br>Open-Xchange Calcengine 7.8.1-rev7<br>Open-Xchange Readerengi

For inter-OX-communication over the network, multiple Open-Xchange servers can form a cluster. This br It's required to define the network interface that is used for cluster communication via ''com.openexchange.hazelcast.network.interfaces''. By default, the inte

...al IPs and the private network <tt>10.10.10.0/24</tt> for the LVS internal communication. Via bonding of two physical devices the network devices bond0/1 need to be ...and virtual IPs and the private network 10.10.10.0/24 for the LVS internal communication is used. Via bonding of two physical devices the network devices bond0/1 ha

...ith a key configured at the open-xchange server. This is only for internal communication and by default no keys are available.

...educational institutions and public administrations seeking a customizable communication solution. Focus: System Integrators |Support for AJP based communication between the HTTP server and the OX backend server. Open-Xchange already pro

...ween those two components by using SSL. To enforce Guard to use SSL in the communication between those two components enable the follwing configuration in Guard con

* Enabled Hazelcast for inter-OX-communication, see [[AppSuite:Running_a_cluster]] for details

|Communication error with Facebook service: %1$s |A communication error occured while processing the free/busy request ("%1$s").