Search results

From Open-Xchange
  • ...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
    5 KB (779 words) - 04:48, 1 August 2018
  • == Communication with the server ==
    21 KB (3,345 words) - 13:52, 29 June 2016
  • ...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
    23 KB (2,471 words) - 10:59, 2 October 2015
  • ...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
    5 KB (792 words) - 04:48, 1 August 2018
  • [[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
  • ...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
  • ...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
    28 KB (3,967 words) - 11:39, 9 January 2017
  • 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
    58 KB (8,939 words) - 14:04, 30 January 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
    26 KB (3,953 words) - 08:05, 11 April 2024
  • ...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
  • ...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
    38 KB (5,758 words) - 18:25, 13 April 2017
  • * Enabled Hazelcast for inter-OX-communication, see [[AppSuite:Running_a_cluster]] for details
    22 KB (3,224 words) - 13:19, 18 December 2023
  • |Communication error with Facebook service: %1$s |A communication error occured while processing the free/busy request ("%1$s").
    213 KB (27,569 words) - 14:38, 15 August 2013
  • ...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
  • communication and collaboration platform. Based on open standards, OX App Suite can be ea
    25 KB (3,877 words) - 07:11, 8 September 2022
  • ...o the individual wforce instances, and we need to have some "intra-cluster communication" between the wforce instances to present a unified view of status.
    31 KB (4,248 words) - 12:18, 9 June 2022
  • | <nowiki>Specifies the protocol to be used for network communication (http or https) ...wiki>Specifies the hosts as <hostname>:<port> pairs to be used for network communication.
    321 KB (44,146 words) - 07:59, 2 December 2015
  • | <nowiki>Specifies the protocol to be used for network communication (http or https) ...wiki>Specifies the hosts as <hostname>:<port> pairs to be used for network communication.
    333 KB (45,761 words) - 15:55, 17 May 2016
  • | <nowiki>Specifies the protocol to be used for network communication (http or https) ...wiki>Specifies the hosts as <hostname>:<port> pairs to be used for network communication.
    347 KB (47,794 words) - 13:34, 31 January 2017
  • | <nowiki>Specifies the protocol to be used for network communication (http or https) ...wiki>Specifies the hosts as <hostname>:<port> pairs to be used for network communication.
    351 KB (48,276 words) - 15:48, 31 January 2017
View ( | ) (20 | 50 | 100 | 250 | 500)