Search results

  • ...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
    26 KB (3,410 words) - 09:34, 27 November 2015
  • ...pen-Xchange is done via some cPanel/WHM hooks and UI plugins using SOAP as communication channel. That means that SOAP must be enabled on Open-Xchange.
    22 KB (3,239 words) - 12:58, 15 January 2019
  • The port for the OX Backend. Default is 8009 (which is direct communication with the backend). Could be 80, etc, if going through load balancers Communication between Guard and the OX backend is set to HTTP by default. All items to be
    12 KB (1,812 words) - 15:50, 8 July 2019
  • == Setup the backend communication ==
    4 KB (620 words) - 10:48, 13 December 2011
  • == Communication with the server ==
    21 KB (3,345 words) - 13:52, 29 June 2016
  • | <nowiki>Enables or disables symmetric encryption. When enabled, the entire communication between the hazelcast members is encrypted at socket level. Ensure that all ...ieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.co
    297 KB (40,685 words) - 10:14, 13 June 2017
  • ...ith a key configured at the open-xchange server. This is only for internal communication and by default no keys are available.
    14 KB (2,193 words) - 13:43, 2 June 2022
  • [[Appsuite:Grizzly#Cluster_setup]] shows that HTTPS communication is terminated by the Apache balancer in front of the Open-Xchange nodes. To
    10 KB (1,419 words) - 04:57, 18 August 2020
  • ...6<br>Open-Xchange Documents frontend v7.8.0-rev6<br>Open-Xchange Documents communication v7.8.0-rev6<br>Open-Xchange Calcengine v7.8.0-rev6<br>Open-Xchange Readeren ...6<br>Open-Xchange Documents frontend v7.8.0-rev6<br>Open-Xchange Documents communication v7.8.0-rev6<br>Open-Xchange Calcengine v7.8.0-rev6<br>Open-Xchange Readeren
    18 KB (2,661 words) - 12:47, 13 January 2016
  • communication and collaboration platform. Based on open standards, OX App Suite can be ea
    25 KB (3,877 words) - 07:11, 8 September 2022
  • ...ervices as dependency. The Apache module ''proxy_ajp'' will handle all the communication with the Open-Xchange Servers. Its configuration also contains the setup of
    4 KB (573 words) - 14:15, 16 June 2011
  • ...n successful, the groupware nodes will establish TCP connections for cache communication.
    4 KB (496 words) - 11:33, 26 August 2015
  • ...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
    28 KB (3,931 words) - 14:07, 14 February 2023
  • [[Category: Communication]]
    1 KB (181 words) - 11:52, 4 June 2020
  • ...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
    27 KB (3,971 words) - 07:21, 22 April 2024
  • An easy-to-use email, communication, and collaboration platform, OX App Suite v7 provides access to a wide rang
    1 KB (137 words) - 16:00, 28 November 2023
  • ...ieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.co ...the java function getHostName will be used. This name is used for internal communication. </nowiki>
    231 KB (31,767 words) - 10:27, 19 April 2013
  • ...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
    21 KB (3,032 words) - 06:05, 18 September 2019
  • [[Category: Communication]]
    3 KB (494 words) - 11:52, 4 June 2020
  • 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
    9 KB (1,287 words) - 16:02, 28 November 2023

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)